Re: [ee4j-community] EE4J Project for annotation scanning?

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

Incidentally, I've recently been thinking about the exact same thing.

What about generating an index like Jandex (https://github.com/wildfly/jandex) by the java compiler and store that in module-info.class?

Any Java environment needing annotations could then just ask the java runtime for it, with an option of manually scanning and/or using the JDK scanner algorithm at run time for those modules that don't have the index.

This would need to become a JEP then I guess.

Thoughts?

Kind regards,

Arjan Tijms

On Thu, Nov 30, 2017 at 1:33 PM, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

If your intention is to simply provide some kind of commonly used library, Github is a good place to start. Once your project gains attention and you feel the need for some kind of official organization around it, start a project on Eclipse: https://www.eclipse.org/projects/handbook/#starting. If you found an existing Eclipse top level project that looks like what you want to be part of, ask them for adoption. :-)

-Markus

 

 

 

From: ee4j-community-bounces@eclipse.org [mailto:ee4j-community-bounces@xxxxxxxxxxx] On Behalf Of Greg Wilkins
Sent: Donnerstag, 30. November 2017 13:28
To: EE4J community discussions
Subject: Re: [ee4j-community] EE4J Project for annotation scanning?

 

 

On 30 November 2017 at 13:26, Markus KARG <markus@xxxxxxxxxxxxxxx> wrote:

I do not see that annotation scanning is limited to enterprise use, so I would say no.

 

So where would you suggest such an effort is coordinated?

 

 

--

Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com

_______________________________________________
ee4j-community mailing list
ee4j-community@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-community