Alan, good to know that there is at least interest and intent to help out with this complex task.
Not so sure we have a lot of cycles, but the eclipse jetty project is already burning cycles now to implement, so in the long run it may be better to put in a few more cycles to make this logic generally accepted. I'm wondering if perhaps I should suggest as a new project within the eclipse EE4J effort, as that will capture interest, expertise and cycles from several frameworks that could benefit. If successful, it might then live there long term, but I think contribution to a future java platform would be a better home for it as it would benefit from being part of future considerations. Unless anybody has a better suggestion of where such an effort could be coordinated, I'll take this suggestion to eclipse EE4J. cheers On 29 November 2017 at 11:01, Alan Bateman <alan.bate...@oracle.com> wrote: > On 29/11/2017 09:33, Greg Wilkins wrote: > >> : >> >> So perhaps it would be a good idea for the library to provide some >> semantics to assist frameworks to get this right? Ideally there would be >> an API to allow frameworks to query the JVM about what classes (which may >> not be loaded and may even be for a different target platform) it can see >> that are annotated in a particular way. >> >> This was listed in the JSR 376 requirements document [1] but it didn't > happen in Java SE 9. There were suggestions at the time to generate an > index at packaging time. There were also suggestions (and some initial > prototyping with a jlink plugin) to index at link time. I don't think the > efforts got as far as thinking about an API. > > So yes, it is an area where there is interest but I'm not aware of anyone > working on it just now. If you or others have cycles to create a library > and explore the area then it could be useful. > > -Alan > > [1] http://openjdk.java.net/projects/jigsaw/spec/reqs/#efficient > -annotation-detection > -- Greg Wilkins <gr...@webtide.com> CTO http://webtide.com
