It is a similar issue to the problem with "javax.inject" API. What about relocating these two APIs to a package "org.apache.maven"? Any thoughts?
On Mon, Oct 14, 2019 at 12:11 AM Petar Tahchiev <[email protected]> wrote: > Hello guys, > > I just decided to upgrade my build from 3.5.0 to 3.6.2 last night and I > stumbled across multiple problems, latest one being the following > exception: > > Nested exception is java.lang.NoSuchMethodError: > javax.annotation.Resource.lookup()Ljava/lang/String; > > Seems like maven 3.6.2 comes with jsr-250-api-1.0.jar in the lib/ folder > and that seems to cause problems for me because I have moneta in my > classpath which brings newer version of jsr250: > > [INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ drmartens --- > [INFO] com.demo:drmartens:war:1.0-SNAPSHOT > [INFO] \- > > com.nemesis.platform:nemesis-platform-core:jar:2.1.67.BUILD-SNAPSHOT:compile > [INFO] \- org.javamoney:moneta:pom:1.3:compile > [INFO] \- javax.annotation:javax.annotation-api:jar:1.3.2:compile > [INFO] > ------------------------------------------------------------------------ > > So I was able to fix this following this recommendation: > > https://stackoverflow.com/questions/52607814/how-to-remove-a-maven-lib-jsr250-api-1-0-jar-from-the-plugin-classpath-jetty > using extensions, but I was wondering: why do we need the JSR250 in the lib > folder? Also why do we need such an old version? > -- > Regards, Petar! > Karlovo, Bulgaria. > --- > Public PGP Key at: > http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x19658550C3110611 > Key Fingerprint: A369 A7EE 61BC 93A3 CDFF 55A5 1965 8550 C311 0611 >
