Hi,
I have a question related to the defining of a plugin parameter within a
Mojo. Say for brevity something simple:
@Parameter
private String theValue;
During the build of my plugin maven-plugin-plugin will create a plugin
descriptor (plugin.xml) which contains the parameter definition
Hi,
here is my +1
Kind regards
Karl Heinz Marbaise
On 07/05/17 15:46, Karl Heinz Marbaise wrote:
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12340502
There are still a couple of issues left in JIRA:
Hi folks,
I am currently working on an IT for MNG-5935 and see currently no option
for optional flag output from the maven-it-plugin-dependency-resolution.
Artifact#isOptional() is never printed.
Here is the commit:
+1 to the general analysis
perhaps using previous release is not so easy since this plugin is used on
CLI, not in a pom.xml (in general), then you don't really choose which version
will be used when you launch "mvn archetype:generate": Maven magic does a
choice for you
The longer command line
As one of the reporters of the breaking change tickets I also rather not
see this reverted as I think that our plugins should follow The Maven Way
and help people do the right thing.
I've seen some voices raises in some of the tickets (after the fact). But
how many is it really that has a
+1
Regards,
Hervé
Le dimanche 7 mai 2017, 20:29:27 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12333851
>
> There are still a couple of issues left in JIRA:
>
Hi,
here is my +1
Kind regards
Karl Heinz Marbaise
On 07/05/17 20:29, Karl Heinz Marbaise wrote:
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12333851
There are still a couple of issues left in JIRA:
+1
Regards,
Hervé
Le dimanche 7 mai 2017, 15:46:18 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12340502
>
> There are still a couple of issues left in JIRA:
>
Who seconds MNG-5935 for 3.5.1?
IT has been added too. Jenkins job is running...
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Who seconds MNG-6228 for 3.5.1?
This is merely debug log statement improvement as a help for MNG-5935.
Michael
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
+1
nice IT addition
I relaunched the Jenkins file branch run and just got a failure because the
commit in core had not been rebased for MNG-6223 while the IT has been
committed after integration of MNG-6223: just little discrepency that will
disappear when merged to master
Regards,
Hervé
Le
+1
looks to be a good clarification in debug output
Regards,
Hervé
Le mercredi 10 mai 2017, 00:01:14 CEST Michael Osipov a écrit :
> Who seconds MNG-6228 for 3.5.1?
>
> This is merely debug log statement improvement as a help for MNG-5935.
>
> Michael
>
>
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
>Is that true that at least some runners still have some children since the
beginning when parallel computer (PC) has recognized them?
In general case I can not garantee that.
+1
--
Regards,
Igor
On Tue, May 9, 2017, at 05:46 PM, Michael Osipov wrote:
> Who seconds MNG-5935 for 3.5.1?
>
> IT has been added too. Jenkins job is running...
>
> Michael
>
> -
> To unsubscribe, e-mail:
14 matches
Mail list logo
