Re: [VOTE] Release Apache Maven Parent POMs version 32

+1 (non binding) Sylwester W dniu śr., 18.07.2018 o 07:03 Hervé BOUTEMY napisał(a): > here is my +1 > > Regards, > > Hervé > > Le dimanche 15 juillet 2018, 20:32:04 CEST Hervé BOUTEMY a écrit : > > Hi, > > > > We solved 7 issues: > > >

Re: Maven Plugin Development and the @Produces

Inject a component, set the current mojo and just "get" it when you need from the component you can inject? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Re: [VOTE] Release Apache Maven Parent POMs version 32

here is my +1 Regards, Hervé Le dimanche 15 juillet 2018, 20:32:04 CEST Hervé BOUTEMY a écrit : > Hi, > > We solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250 > rsion=12342723=Text > > Changes since the last release: >

Re: Maven Plugin Development and the @Produces

Unfortunately, my module is not being called, so I don't think it's supported. Is there *ANY* way to inject Configuration parameters into sub-modules? ANY possible way? On 2018/07/16 19:53:33, Romain Manni-Bucau wrote: > Maven tries to limit that to jsr330 usage hoping it stays portable ( >

Re: [VOTE] Release Apache Maven Parent POMs version 32

Le mardi 17 juillet 2018, 10:42:43 CEST Sylwester Lachiewicz a écrit : > Hi, > > With update to the parent-pom (maven-apache-parent) MPOM-186 [1] - maybe > we should also update javaVersion property to 7? this is exactly the discussion that should have happened when I asked if something was to

Re: [VOTE] Release Apache Maven Parent POMs version 32

+1 On Sun, 15 Jul 2018 20:32:04 +0200, Hervé BOUTEMY wrote: Hi, We solved 7 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311250=12342723=Text Changes since the last release:

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

Hi Rory, that's fine by me. We should think of a dynamic part on our pages if Maven, maven plugins or libraries are Java-n compatible, but that sounds easier than it is... Robert On Tue, 17 Jul 2018 21:16:24 +0200, Rory O'Donnell wrote: Hi Robert, If you are ok for me to link to this

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

Hi Robert, If you are ok for me to link to this email, that's fine. Thanks,Rory On 17/07/2018 17:34, Robert Scholte wrote: Hi Rory, I see there's a list of tools frameworks that support the latest Java version. From our point of view there has never been an issue to run Maven on the

Re: JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

Hi Rory, I see there's a list of tools frameworks that support the latest Java version. From our point of view there has never been an issue to run Maven on the latest versions. I'm pretty sure that even Maven 3.0 (or likely 2.x as well) will run on those Java versions as well. Do you

JDK 11 Early Access build 22 & JDK 12 Early Access b02 are available.

Hi Robert , *JDK 11 is in Rampdown Phase one* * *The overall feature set is frozen. No further JEPs will be targeted to this release.* * *Rampdown Phase two is scheduled to start * *26th of July* **JDK 11 EA build 22 , *under both the GPL and Oracle EA licenses, is now available

Re: [VOTE] Release Apache Maven Parent POMs version 32

Hi, With update to the parent-pom (maven-apache-parent) MPOM-186 [1] - maybe we should also update javaVersion property to 7? Or maybe this configuration was intentional for other Maven's projecs? pom.xml 867