Re: [VOTE] Release Apache Maven JMod Plugin version 3.0.0-alpha-1 (First Public Release) Take 3

2017-09-20 Thread Hervé BOUTEMY
sorry, the failure was with an old jdk 1.9+134 with latest jdk 1.9+181, everything is ok then here is my +1 notice one WARNING: [INFO] Building: non-default-config-headerfiles/pom.xml [INFO] run post-build script verify.groovy WARNING: An illegal reflective access operation has occurred WARNING:

Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)

2017-09-20 Thread Stephen Connolly
On Wed 20 Sep 2017 at 01:29, Igor Fedorenko wrote: > In that case, can I suggest couple of changes to the test project > > * I thinks it makes more sense to configure extjar1 and extjar2 as > extensions elements in probleN pom.xml files. First, there is > no meaningful

Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)

2017-09-20 Thread Robert Scholte
On Wed, 20 Sep 2017 09:12:47 +0200, Stephen Connolly wrote: On Wed 20 Sep 2017 at 01:29, Igor Fedorenko wrote: In that case, can I suggest couple of changes to the test project * I thinks it makes more sense to configure extjar1 and

[ANN] Apache Maven JMod Plugin Version 3.0.0-alpha-1 Released

2017-09-20 Thread Karl Heinz Marbaise
The Apache Maven team is pleased to announce the release of the Apache Maven JMod Plugin Version 3.0.0-alpha-1 release https://maven.apache.org/plugins/maven-jmod-plugin/ The JMod Plugin is used to create JMod Files http://openjdk.java.net/jeps/261 The plugin has got the major version 3 to

Re: [VOTE] Release Apache Maven JMod Plugin version 3.0.0-alpha-1 (First Public Release) Take 3

2017-09-20 Thread Karl Heinz Marbaise
Hi Hervé, On 20/09/17 08:07, Hervé BOUTEMY wrote: sorry, the failure was with an old jdk 1.9+134 with latest jdk 1.9+181, everything is ok then here is my +1 notice one WARNING: [INFO] Building: non-default-config-headerfiles/pom.xml [INFO] run post-build script verify.groovy WARNING: An

dependency:go-offline broken?

2017-09-20 Thread Benedikt Ritter
Hi, as far as I understand it should be possible to call mvn dependency:go-offline and from there on work in offline mode (mvn -o). I’ve put a minimal example together [1] that demonstrates that this currently does not work. Am I missing anything? Thank you! Benedikt [1]

Re: dependency:go-offline broken?

2017-09-20 Thread Brian Fox
It's been a really long time, but I recall that there were issues getting the dependencies of plugins bound to the lifecycle. This looks to be the same problem. I think the documentation talked about a way to do this effectively. On Wed, Sep 20, 2017 at 4:48 PM, Benedikt Ritter

[RESULT] [VOTE] Release Apache Maven JMod Plugin version 3.0.0-alpha-1 (First Public Release) Take 3

2017-09-20 Thread Karl Heinz Marbaise
Hi, The vote has passed with the following result: +1 : Robert Scholte, Hervé Boutemy, Karl Heinz Marbaise PMC quorum: reached. I will promote the artifacts to the central repo. Kind regards Karl Heinz Marbaise - To

Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)

2017-09-20 Thread Igor Fedorenko
Just to be clear, while I agree the documentation is lacking, neither special-casing "simple" nor META-INF/maven/extension.xml is new behaviour in 3.5.1, both existed since 3.0 alphas iirc. Also, Hervé did add some extension.xml documentation couple of years ago.

Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)

2017-09-20 Thread Igor Fedorenko
Real-world scm or wagon won't trigger maven2-compat code path [1]. To avoid that obscure code path we can either make the test more elaborate (i.e. add dependencies to extjar1/extjar2) or we can use extensions . Either way I don't think we should spend time on the code path unlikely to be used in