Re: migrating some code to Git

2017-10-06 Thread Hervé BOUTEMY 
re-reading our migration process documentation [1], I see "check especially 
behaviour on checking out tag"

I suppose that we could compare content between git checkout and svn checkout 
for HEAD and every past release

did somebody prepare a shell script for that?

Regards,

Hervé

[1] https://cwiki.apache.org/confluence/display/MAVEN/Git
+Migration#GitMigration-Migrationprocessdescription

Le vendredi 6 octobre 2017, 00:34:11 CEST Hervé BOUTEMY a écrit :
> great, thank you for your help
> 
> in fact, AFAIK, Apache has already automatic svn2git exports [1] that are
> then mirrored to github.
> Then we already have:
> - https://github.com/apache/maven-doxia/
> - https://github.com/apache/maven-doxia-sitetools/
> - https://github.com/apache/maven-enforcer/
> - https://github.com/apache/maven-jxr/
> - https://github.com/apache/maven-plugin-tools/
> - https://github.com/apache/maven-release/
> 
> I suppose these could be the natural targets.
> But I don't really see what checks to do on these.
> 
> I suppose that once we are convinced this content is ok, we can ask infra to
> switch these to the canonical source (and disable the svn2git exports)
> 
> Do you see any issue in these repos?
> 
> Regards,
> 
> Hervé
> 
> [1] http://git.apache.org/
> 
> Le jeudi 5 octobre 2017, 11:45:23 CEST Dejan Stojadinovic a écrit :
> > Count me in (for both actual migration and related tasks).
> > 
> > My weapon of choice for SVN -->>GIT would be:
> > https://github.com/nirvdrum/svn2git (I managed to move dozen of repos few
> > years ago).
> > 
> > Regards,
> > Dejan
> > 
> > On 2017-10-04 01:48, Hervé BOUTEMY  wrote:
> > > I'd like to work on Plugin Tools with git
> > > 
> > > While at it, looking at our plan [1], I see we have a few other
> > > components
> > > that are ready to migrate:
> > > - Doxia core
> > > - Doxia Sitetools
> > > - Enforcer
> > > - Jxr
> > > - Plugin Tools
> > > - Release
> > > 
> > > What checks are required before switching these 6 components?
> > > Any volunteer?
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
> > > 
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Jenkins and Maven 3.0.5 or JDK 7

2017-10-06 Thread Hervé BOUTEMY 
There are 6 svn locations without any special complexity that are waiting for 
a volunteer for git migration for a few years but nobody does anything about: 
I started 3 days ago to ask for help about it and got pretty no feedback [1]

then there are the 4 complex svn locations (plugins, shared, resources, doxia-
tools) that require much more work: I suppose we can't tell git migration is 
abandoned, but it will require someone to work on it seriously
Remember that the key question [2] is: do we transform these 4 svn locations 
into 41 +26 + 6 + 5 = 78 independent git repos?
Yes, I told that Jenkins configuration is one key aspect we need a strategy 
about, in parallel with git strategy.

then there will be the remaining cases where we need to decide: lower impact, 
lower priority.


Summary: nothing is abandoned, but:
- simple cases: no volunteer to do the job
- hard cases: is there a volunteer either to define a strategy or do some work 
on it?


Regards,

Hervé

[1] https://lists.apache.org/thread.html/
edf3642a7bdd515f0cad421c25589741819446463614bf0515e56dbe@
%3Cdev.maven.apache.org%3E

[2] https://cwiki.apache.org/confluence/display/MAVEN/Git
+Migration#GitMigration-Migratinganaggregatortreeintoacollectionofgitrepos

Le vendredi 6 octobre 2017, 20:35:45 CEST Arnaud Héritier a écrit :
> But did we completely abandoned the idea of moving everything to git ?
> The CI setup was the main stop for it ?
> 
> On Fri, Oct 6, 2017 at 8:05 PM, Hervé BOUTEMY  wrote:
> > I was expecting the usual litany
> > 
> > what I'm not confident currently with pipeline on Maven core is that we
> > have
> > for example the "maven-3.x-jenkinsfile/MNG-6242 - build #1 - null"
> > message,
> > with this "null" part that makes me wonder if we are using it as expected.
> > 
> > And for large multi-module svn trunks (the ones we don't migrate to git:
> > mainly plugins and shared), is there a solution to rebuild just changed
> > modules?
> > 
> > ideally, the rebuild when a SNAPSHOT dependency is published would have
> > been a
> > plus, but this is sufficiently a rare use that I won't be extremist
> > 
> > 
> > Then IIUC, this migration job is one additional TODO for me...
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le vendredi 6 octobre 2017, 17:46:53 CEST Arnaud Héritier a écrit :
> > > I agree that we should use pipeline nowdays
> > > perhaps a shared lib if we want to standardize some stuffs and a set of
> > > multi-branches jobs (or org folder but it requires GitHub :( )
> > > 
> > > On Fri, Oct 6, 2017 at 9:16 AM, Stephen Connolly <
> > > 
> > > stephen.alan.conno...@gmail.com> wrote:
> > > > On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY 
> > 
> > wrote:
> > > > > I just fixed a few failing jobs [1] to have again a usable Jenkins.
> > > > > 
> > > > > Now I'm facing some issues, I suppose caused by newer Jenkins
> > 
> > versions:
> > > > > - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.
> > > > 
> > > > MXParser
> > > > 
> > > > > [2]
> > > > > - I had to switch to JDK 8 for maven-plugin-tools job, since JDK
> > 
> > causes
> > 
> > > > > failures (looks like Jenkins uses a hack to inject JDK 7 as a tool
> > 
> > while
> > 
> > > > > the
> > > > > build JVM is Java 8)
> > > > > 
> > > > > Should we drop Maven 3.0.5 builds and JDK 7?
> > > > > Notice I didn't check which is the minimum Maven version required...
> > > > > 
> > > > > Or perhaps simply don't use the Jenkins Maven plugin with this Maven
> > > > 
> > > > 3.0.5
> > > > 
> > > > > or
> > > > > JDK 7 configuration: default build as Jenkins Maven plugin with JDK
> > 
> > 8 +
> > 
> > > > > latest
> > > > > Maven, and other configurations as scripted jobs?
> > > > 
> > > > http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-> >
> > 
> > type-considered-evil.html
> > 
> > > >  >
> > 
> > maven-job-type-considered-evil.html?m=1>
> > 
> > > > We should stop using the evil job type as it’s minimum Java version is
> > > > dictated by Jenkins’ Java minimum.
> > > > 
> > > > > We need to define our common strategy and have a consistent
> > > > > configuration
> > > > > for
> > > > > every job understood by everybody
> > > > 
> > > > I recommend Jenkinsfile and the `withMaven` wrapper
> > > > 
> > > > > Regards,
> > > > > 
> > > > > Hervé
> > > > > 
> > > > > [1] https://builds.apache.org/view/M-R/view/Maven/
> > > > > 
> > > > > [2]
> > > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-> >
> > > > 
> > > > plugin-tools-jdk-1.7/162/console
> > > > 
> > > > > 
> > 
> > -
> > 
> > > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > > > 
> > > > > --
> > > > 
> > > > Sent from my phone
> > 
> > -
> > To unsubscribe, e-mail:

Re: Jenkins and Maven 3.0.5 or JDK 7

2017-10-06 Thread Stephen Connolly 
On Fri 6 Oct 2017 at 16:47, Arnaud Héritier  wrote:

> I agree that we should use pipeline nowdays
> perhaps a shared lib if we want to standardize some stuffs and a set of
> multi-branches jobs (or org folder but it requires GitHub :( )


Nah I can give us org folder on top of ASF pubsub relatively easily


>
> On Fri, Oct 6, 2017 at 9:16 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY  wrote:
> >
> > > I just fixed a few failing jobs [1] to have again a usable Jenkins.
> > >
> > > Now I'm facing some issues, I suppose caused by newer Jenkins versions:
> > > - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.
> > MXParser
> > > [2]
> > > - I had to switch to JDK 8 for maven-plugin-tools job, since JDK causes
> > > failures (looks like Jenkins uses a hack to inject JDK 7 as a tool
> while
> > > the
> > > build JVM is Java 8)
> > >
> > > Should we drop Maven 3.0.5 builds and JDK 7?
> > > Notice I didn't check which is the minimum Maven version required...
> > >
> > > Or perhaps simply don't use the Jenkins Maven plugin with this Maven
> > 3.0.5
> > > or
> > > JDK 7 configuration: default build as Jenkins Maven plugin with JDK 8 +
> > > latest
> > > Maven, and other configurations as scripted jobs?
> >
> >
> > http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-
> > type-considered-evil.html
> >  > maven-job-type-considered-evil.html?m=1>
> >
> > We should stop using the evil job type as it’s minimum Java version is
> > dictated by Jenkins’ Java minimum.
> >
> >
> > >
> > > We need to define our common strategy and have a consistent
> configuration
> > > for
> > > every job understood by everybody
> >
> >
> > I recommend Jenkinsfile and the `withMaven` wrapper
> >
> > >
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > [1] https://builds.apache.org/view/M-R/view/Maven/
> > >
> > > [2]
> > > https://builds.apache.org/view/M-R/view/Maven/job/maven-
> > plugin-tools-jdk-1.7/162/console
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > > --
> > Sent from my phone
> >
>
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
-- 
Sent from my phone

Re: Jenkins and Maven 3.0.5 or JDK 7

2017-10-06 Thread Arnaud Héritier 
But did we completely abandoned the idea of moving everything to git ?
The CI setup was the main stop for it ?

On Fri, Oct 6, 2017 at 8:05 PM, Hervé BOUTEMY  wrote:

> I was expecting the usual litany
>
> what I'm not confident currently with pipeline on Maven core is that we
> have
> for example the "maven-3.x-jenkinsfile/MNG-6242 - build #1 - null"
> message,
> with this "null" part that makes me wonder if we are using it as expected.
>
> And for large multi-module svn trunks (the ones we don't migrate to git:
> mainly plugins and shared), is there a solution to rebuild just changed
> modules?
>
> ideally, the rebuild when a SNAPSHOT dependency is published would have
> been a
> plus, but this is sufficiently a rare use that I won't be extremist
>
>
> Then IIUC, this migration job is one additional TODO for me...
>
> Regards,
>
> Hervé
>
> Le vendredi 6 octobre 2017, 17:46:53 CEST Arnaud Héritier a écrit :
> > I agree that we should use pipeline nowdays
> > perhaps a shared lib if we want to standardize some stuffs and a set of
> > multi-branches jobs (or org folder but it requires GitHub :( )
> >
> > On Fri, Oct 6, 2017 at 9:16 AM, Stephen Connolly <
> >
> > stephen.alan.conno...@gmail.com> wrote:
> > > On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY 
> wrote:
> > > > I just fixed a few failing jobs [1] to have again a usable Jenkins.
> > > >
> > > > Now I'm facing some issues, I suppose caused by newer Jenkins
> versions:
> > > > - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.
> > >
> > > MXParser
> > >
> > > > [2]
> > > > - I had to switch to JDK 8 for maven-plugin-tools job, since JDK
> causes
> > > > failures (looks like Jenkins uses a hack to inject JDK 7 as a tool
> while
> > > > the
> > > > build JVM is Java 8)
> > > >
> > > > Should we drop Maven 3.0.5 builds and JDK 7?
> > > > Notice I didn't check which is the minimum Maven version required...
> > > >
> > > > Or perhaps simply don't use the Jenkins Maven plugin with this Maven
> > >
> > > 3.0.5
> > >
> > > > or
> > > > JDK 7 configuration: default build as Jenkins Maven plugin with JDK
> 8 +
> > > > latest
> > > > Maven, and other configurations as scripted jobs?
> > >
> > > http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-> >
> type-considered-evil.html
> > >  >
> maven-job-type-considered-evil.html?m=1>
> > >
> > > We should stop using the evil job type as it’s minimum Java version is
> > > dictated by Jenkins’ Java minimum.
> > >
> > > > We need to define our common strategy and have a consistent
> > > > configuration
> > > > for
> > > > every job understood by everybody
> > >
> > > I recommend Jenkinsfile and the `withMaven` wrapper
> > >
> > > > Regards,
> > > >
> > > > Hervé
> > > >
> > > > [1] https://builds.apache.org/view/M-R/view/Maven/
> > > >
> > > > [2]
> > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-> >
> > > plugin-tools-jdk-1.7/162/console
> > >
> > > > 
> -
> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > >
> > > > --
> > >
> > > Sent from my phone
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

Re: Jenkins and Maven 3.0.5 or JDK 7

2017-10-06 Thread Hervé BOUTEMY 
I was expecting the usual litany

what I'm not confident currently with pipeline on Maven core is that we have 
for example the "maven-3.x-jenkinsfile/MNG-6242 - build #1 - null" message, 
with this "null" part that makes me wonder if we are using it as expected.

And for large multi-module svn trunks (the ones we don't migrate to git: 
mainly plugins and shared), is there a solution to rebuild just changed 
modules?

ideally, the rebuild when a SNAPSHOT dependency is published would have been a 
plus, but this is sufficiently a rare use that I won't be extremist


Then IIUC, this migration job is one additional TODO for me...

Regards,

Hervé

Le vendredi 6 octobre 2017, 17:46:53 CEST Arnaud Héritier a écrit :
> I agree that we should use pipeline nowdays
> perhaps a shared lib if we want to standardize some stuffs and a set of
> multi-branches jobs (or org folder but it requires GitHub :( )
> 
> On Fri, Oct 6, 2017 at 9:16 AM, Stephen Connolly <
> 
> stephen.alan.conno...@gmail.com> wrote:
> > On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY  wrote:
> > > I just fixed a few failing jobs [1] to have again a usable Jenkins.
> > > 
> > > Now I'm facing some issues, I suppose caused by newer Jenkins versions:
> > > - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.
> > 
> > MXParser
> > 
> > > [2]
> > > - I had to switch to JDK 8 for maven-plugin-tools job, since JDK causes
> > > failures (looks like Jenkins uses a hack to inject JDK 7 as a tool while
> > > the
> > > build JVM is Java 8)
> > > 
> > > Should we drop Maven 3.0.5 builds and JDK 7?
> > > Notice I didn't check which is the minimum Maven version required...
> > > 
> > > Or perhaps simply don't use the Jenkins Maven plugin with this Maven
> > 
> > 3.0.5
> > 
> > > or
> > > JDK 7 configuration: default build as Jenkins Maven plugin with JDK 8 +
> > > latest
> > > Maven, and other configurations as scripted jobs?
> > 
> > http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-> > 
> > type-considered-evil.html
> >  > 
> > maven-job-type-considered-evil.html?m=1>
> > 
> > We should stop using the evil job type as it’s minimum Java version is
> > dictated by Jenkins’ Java minimum.
> > 
> > > We need to define our common strategy and have a consistent
> > > configuration
> > > for
> > > every job understood by everybody
> > 
> > I recommend Jenkinsfile and the `withMaven` wrapper
> > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > [1] https://builds.apache.org/view/M-R/view/Maven/
> > > 
> > > [2]
> > > https://builds.apache.org/view/M-R/view/Maven/job/maven-> > 
> > plugin-tools-jdk-1.7/162/console
> > 
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > > 
> > > --
> > 
> > Sent from my phone



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Jenkins and Maven 3.0.5 or JDK 7

2017-10-06 Thread Arnaud Héritier 
I agree that we should use pipeline nowdays
perhaps a shared lib if we want to standardize some stuffs and a set of
multi-branches jobs (or org folder but it requires GitHub :( )

On Fri, Oct 6, 2017 at 9:16 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY  wrote:
>
> > I just fixed a few failing jobs [1] to have again a usable Jenkins.
> >
> > Now I'm facing some issues, I suppose caused by newer Jenkins versions:
> > - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.
> MXParser
> > [2]
> > - I had to switch to JDK 8 for maven-plugin-tools job, since JDK causes
> > failures (looks like Jenkins uses a hack to inject JDK 7 as a tool while
> > the
> > build JVM is Java 8)
> >
> > Should we drop Maven 3.0.5 builds and JDK 7?
> > Notice I didn't check which is the minimum Maven version required...
> >
> > Or perhaps simply don't use the Jenkins Maven plugin with this Maven
> 3.0.5
> > or
> > JDK 7 configuration: default build as Jenkins Maven plugin with JDK 8 +
> > latest
> > Maven, and other configurations as scripted jobs?
>
>
> http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-
> type-considered-evil.html
>  maven-job-type-considered-evil.html?m=1>
>
> We should stop using the evil job type as it’s minimum Java version is
> dictated by Jenkins’ Java minimum.
>
>
> >
> > We need to define our common strategy and have a consistent configuration
> > for
> > every job understood by everybody
>
>
> I recommend Jenkinsfile and the `withMaven` wrapper
>
> >
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://builds.apache.org/view/M-R/view/Maven/
> >
> > [2]
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-
> plugin-tools-jdk-1.7/162/console
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> > --
> Sent from my phone
>



-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

[GitHub] maven-plugins pull request #132: MPDF-48: Update site documentation & non su...

2017-10-06 Thread sgarelle 
GitHub user sgarelle opened a pull request:

https://github.com/apache/maven-plugins/pull/132

MPDF-48: Update site documentation &  non supported report plugins.

Ready for 1.4 release.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sgarelle/maven-plugins MPDF-48

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/132.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #132


commit 0d471a2e2793e0dadca140439aeb3dad8e8b9ad9
Author: Sebastien Garelle 
Date:   2017-10-06T14:50:19Z

MPDF-48: Update site documentation &  non supported report plugins.




---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Jenkins and Maven 3.0.5 or JDK 7

2017-10-06 Thread Stephen Connolly 
On Fri 6 Oct 2017 at 06:32, Hervé BOUTEMY  wrote:

> I just fixed a few failing jobs [1] to have again a usable Jenkins.
>
> Now I'm facing some issues, I suppose caused by newer Jenkins versions:
> - Maven 3.0.5 causes NoSuchMethodError: o.c.plexus.util.xml.pull.MXParser
> [2]
> - I had to switch to JDK 8 for maven-plugin-tools job, since JDK causes
> failures (looks like Jenkins uses a hack to inject JDK 7 as a tool while
> the
> build JVM is Java 8)
>
> Should we drop Maven 3.0.5 builds and JDK 7?
> Notice I didn't check which is the minimum Maven version required...
>
> Or perhaps simply don't use the Jenkins Maven plugin with this Maven 3.0.5
> or
> JDK 7 configuration: default build as Jenkins Maven plugin with JDK 8 +
> latest
> Maven, and other configurations as scripted jobs?


http://javaadventure.blogspot.ie/2013/11/jenkins-maven-job-type-considered-evil.html


We should stop using the evil job type as it’s minimum Java version is
dictated by Jenkins’ Java minimum.


>
> We need to define our common strategy and have a consistent configuration
> for
> every job understood by everybody


I recommend Jenkinsfile and the `withMaven` wrapper

>
>
> Regards,
>
> Hervé
>
> [1] https://builds.apache.org/view/M-R/view/Maven/
>
> [2]
> https://builds.apache.org/view/M-R/view/Maven/job/maven-plugin-tools-jdk-1.7/162/console
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone