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

2017-09-19 Thread Hervé BOUTEMY
tested "mvn verify" and got failure for every IT: Caused by: org.apache.maven.plugin.PluginExecutionException: Execution default-create of goal org.apache.maven.plugins:maven-jmod-plugin:3.0.0- alpha-1:create failed: 9 at

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

2017-09-19 Thread Karl Heinz Marbaise
Hi, one more PMC vote is needed... Kind regards Karl Heinz Marbaise On 17/09/17 13:40, Karl Heinz Marbaise wrote: Hi, this is the VOTE for the first public release for Maven JMod Plugin... We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321433=12341363

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

2017-09-19 Thread Igor Fedorenko
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 order between and elements. More importantly, though, simple are treated in special

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

2017-09-19 Thread Stephen Connolly
Yes, the expectations are key. Depending on what they are we may either drop 3.5.1 or go ahead as it depends on whether this is more correct than 3.5.0 or swapping one fix for a bug On Tue 19 Sep 2017 at 21:39, Igor Fedorenko wrote: > Just to confirm I understand what we

RE: Version Information needed.

2017-09-19 Thread Robert Patrick
[Removing Maven dev list from the email thread via BCC] This plugin is not part of the Maven core so you can likely use any modern version of the plugin with Maven 3.2.5. As for how to use it, probably best to start with http://www.mojohaus.org/cobertura-maven-plugin/ and then ask more

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

2017-09-19 Thread Igor Fedorenko
Just to confirm I understand what we are trying to establish here. We want to decide the expected/desired component injection behaviour and classpath visibility in the absence of package and artifact export configuration (i.e. META-INF/maven/extension.xml file). Did I get this right? -- Regards,

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

2017-09-19 Thread Robert Scholte
Let's do it like this: https://cwiki.apache.org/confluence/download/attachments/2329841/classrealms.pdf?api=v2 Robert On Tue, 19 Sep 2017 21:08:39 +0200, Stephen Connolly wrote: I think you will need a link to the PDF as attachments are stripped from the

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

2017-09-19 Thread Stephen Connolly
I think you will need a link to the PDF as attachments are stripped from the ML On Tue 19 Sep 2017 at 19:57, Robert Scholte wrote: > Attached a single page overview. > > Per block you'll see in the upper left corner the executed plugin > The left column contains the

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

2017-09-19 Thread Robert Scholte
Attached a single page overview. Per block you'll see in the upper left corner the executed plugin The left column contains the extensions and plugin in orderas specified in the pom.xml In every classloadercolumn you'll see numbers which represent the order. I hope I didn't make any

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

2017-09-19 Thread Karl Heinz Marbaise
Hi, here my +1... Kind regards Karl Heinz Marbaise On 17/09/17 13:40, Karl Heinz Marbaise wrote: Hi, this is the VOTE for the first public release for Maven JMod Plugin... We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321433=12341363 There are