Re: JSR250 in the lib

2019-10-18 Thread Robert Scholte
t; > > > > > > > Nested exception is java.lang.NoSuchMethodError: > > > > > > > javax.annotation.Resource.lookup()Ljava/lang/String; > > > > > > > > > > > > > > Seems like maven 3.6.2 comes with jsr-250-a

Re: JSR250 in the lib

2019-10-14 Thread Romain Manni-Bucau
ust expose the @PostConstruct, @PreDestroy, > and > > > > > > @Priority > > > > > > > > annotation types rather than the whole package. > > > > > > > > > > > > > > > > On Mon, 14 Oct 2019 at 06:01, Romain Manni-Bucau < > > > > > >

Re: JSR250 in the lib

2019-10-14 Thread Tibor Digana
t; > > recent API it was not upgraded. > > > > > > > > We can upgrade it or just isolate it IMO - but requires some > > > > careness > > > > > > > since > > > > > > > > custom components can use it so

Re: JSR250 in the lib

2019-10-14 Thread Romain Manni-Bucau
> > > > > > > écrit : > > > > > > > > > > > > > > > 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 >

Re: JSR250 in the lib

2019-10-14 Thread Olivier Lamy
; > > wrote: > > > > > > > > > > > > > > > Hello guys, > > > > > > > > > > > > > > > > I just decided to upgrade my build from 3.5.0 to 3.6.2 last > > night > > > > >

Re: JSR250 in the lib

2019-10-14 Thread Stuart McCulloch
multiple problems, latest one being the > following > > > > > > > exception: > > > > > > > > > > > > > > Nested exception is java.lang.NoSuchMethodError: > > > > > > > javax.annotation.Resource.lookup()Ljava/lang/String; > > > > > > &g

Re: JSR250 in the lib

2019-10-14 Thread Tibor Digana
hMethodError: > > > > > > 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

Re: JSR250 in the lib

2019-10-14 Thread Stuart McCulloch
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 > > > >

Re: JSR250 in the lib

2019-10-14 Thread Petar Tahchiev
lems 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-SNA

Re: JSR250 in the lib

2019-10-14 Thread Tibor Digana
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 > >

Re: JSR250 in the lib

2019-10-14 Thread Stuart McCulloch
SHOT:compile > > > [INFO]\- org.javamoney:moneta:pom:1.3:compile > > > [INFO] \- javax.annotation:javax.annotation-api:jar:1.3.2:compile > > > [INFO] > > > > -------- > > > >

Re: JSR250 in the lib

2019-10-13 Thread Romain Manni-Bucau
- 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/52607

Re: JSR250 in the lib

2019-10-13 Thread Tibor Digana
> 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? Als

JSR250 in the lib

2019-10-13 Thread Petar Tahchiev
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