For people looking for an example solution, this is what we ended up doing in Hibernate projects after we had shared these pain points in February: add an explicit dependency to the Maven artifact `javax.annotation:jsr250-api:1.0`.
We use an explicit phase for running annotation processors via the maven-processor-plugin, so that it doesn't pollute published dependency definitions. https://github.com/hibernate/hibernate-search/blob/master/pom.xml#L996-L1001 HTH Thanks, Sanne On Wed, Sep 20, 2017 at 4:50 PM, Michael Rasmussen < michael.rasmus...@zeroturnaround.com> wrote: > This one? > http://download.java.net/java/jdk9/docs/api/javax/annotation/processing/ > Generated.html > > /Michael > > On Sep 20, 2017 18:44, "Stephen Colebourne" <scolebou...@joda.org> wrote: > > > As per this email: > > http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017- > > February/011365.html > > the idea was to add a new annotation `java.lang.annotation.Generated` > > to replace the old problematic one. > > > > Is it my imagination, or did this get forgotten?: > > http://download.java.net/java/jdk9/docs/api/java/lang/ > > annotation/package-summary.html > > > > Stephen > > >
