Re: [IMPORTANT] Re: Git migration next steps

2018-01-02 Thread Hervé BOUTEMY
Le mardi 2 janvier 2018, 14:32:00 CET Plamen Totev a écrit : > Hi, > > > On Thu, Dec 28, 2017 at 10:43 AM, Hervé BOUTEMY > > wrote: thank you Plamen: this script is really awesome! > > You're welcome. I'm glad it helped. > > > And I just pushed the result on maven-acr-plugin: you can see the r

Re: [IMPORTANT] Re: Git migration next steps

2018-01-02 Thread Hervé BOUTEMY
Great I pushed tags where the situation was clear. I chose not to push maven-compiler-plugin-2.0.1, since it causes more trouble than this minor version (from 2006, between 2.0 and 2.0.2) is worth Same for maven-shade-plugin-1.0 I still need to work on maven-assembly-plugin, maven-dependency-pl

Re: [IMPORTANT] Re: Git migration next steps

2018-01-02 Thread Stephen Connolly
https://issues.apache.org/jira/browse/MJAVADOC-510 On 2 January 2018 at 13:42, Robert Scholte wrote: > On Tue, 02 Jan 2018 13:16:37 +0100, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > Now here's a strange one The maven-javadoc-plugin is getting a lot of >> open tasks repo

Re: [IMPORTANT] Re: Git migration next steps

2018-01-02 Thread Robert Scholte
On Tue, 02 Jan 2018 13:16:37 +0100, Stephen Connolly wrote: Now here's a strange one The maven-javadoc-plugin is getting a lot of open tasks reported... because there are UNIT tests forking Maven... what is JavadocUtil.invokeMaven doing? Should it even be doing that... or should it be

Re: [IMPORTANT] Re: Git migration next steps

2018-01-02 Thread Plamen Totev
Hi, > On Thu, Dec 28, 2017 at 10:43 AM, Hervé BOUTEMY > wrote: > thank you Plamen: this script is really awesome! You're welcome. I'm glad it helped. > And I just pushed the result on maven-acr-plugin: you can see the result live. > As you can see, the tags on GitBox [2] are updated but not t

Re: [IMPORTANT] Re: Git migration next steps

2018-01-02 Thread Stephen Connolly
Now here's a strange one The maven-javadoc-plugin is getting a lot of open tasks reported... because there are UNIT tests forking Maven... what is JavadocUtil.invokeMaven doing? Should it even be doing that... or should it be using a more correct helper from e.g. maven-invoker? In any case we