migration to git : next steps - Jenkins

2014-05-28 Thread jhm
Here is an intermediate result and my opinion on that: All jobs are successful running or waiting for a blocking INFRA-issue. What about the IvyDE-updatesite? Open problems = I dont know wheter IvyDE-updatesite is migrated to git, too. -- Question to the IvyDE experts here ;)

migration to git : next steps - Jenkins

2014-05-28 Thread jhm
Here is an intermediate result and my opinion on that: All jobs are successful running or waiting for a blocking INFRA-issue. What about the IvyDE-updatesite? Also I updated the view (add missing ivy-tests) https://builds.apache.org/view/A-D/view/Ant/ I deactivated the windows builds until

Re: migration to git : next steps - Jenkins

2014-05-28 Thread Nicolas Lalevée
About IvyDE's updatesite project, it is really just a build script. We never release it. It is a just a helper to produce the binaries associated with an Ivy or IvyDE release so they can be downloaded directly into Eclipse. And it relies on some svn:externals of Apache's dist, so it should be

AW: migration to git : next steps - Jenkins

2014-05-27 Thread jhm
- Von: Antoine Levy Lambert [mailto:anto...@gmx.de] Gesendet: Dienstag, 27. Mai 2014 04:49 An: Ant Developers List Betreff: Re: migration to git : next steps I found an article mentioning something similar to what we would need : http://www.leewillis.co.uk/including-git-repo-svn-external

AW: migration to git : next steps - Jenkins

2014-05-27 Thread jhm
: migration to git : next steps - Jenkins I changed the repo urls from svn to git for - Ant-Build-Matrix - Ant_BuildFromPOMs - Ant_Nightly - EasyAnt - Ivy - Ivy-check - IvyDE all with additional behaviour: clean before checkout and I started the builds. I'll have to wait for running

migration to git : next steps - updating Jenkins jobs

2014-05-27 Thread jhm
Current status: - Ant-Build-Matrix repo: git https://builds.apache.org/job/Ant_BuildFromPOMs/ status: errors on the slaves - Ant_BuildFromPOMs repo: git https://builds.apache.org/job/Ant_BuildFromPOMs/ status: run fine (using locks-and-latches, no archiving) -

AW: migration to git : next steps - updating Jenkins jobs

2014-05-27 Thread jhm
Subject migration to git : next steps - updating Jenkins jobs Text Here is an intermediate result and my opinion on that: Ant-Build-Matrix has problems on Ubuntu and on Windows. On Windows it seems (to me) that there is no git installed or not on the PATH. -- open an INFRA-Ticket? On Ubuntu

migration to git : next steps - updating Jenkins jobs

2014-05-27 Thread jhm
Here is an intermediate result and my opinion on that: Ant-Build-Matrix has problems on Ubuntu and on Windows. On Windows it seems (to me) that there is no git installed or not on the PATH. -- open an INFRA-Ticket? On Ubuntu publishing the build results failed. -- I'll have a look at the

migration to git : next steps - Jenkins

2014-05-27 Thread jhm
Here is an intermediate result and my opinion on that: Open problems = Ant-Build-Matrix has problems on Ubuntu and on Windows. On Windows it seems (to me) that there is no git installed or not on the PATH. -- open an INFRA-Ticket? On Ubuntu publishing the build results

Re: migration to git : next steps

2014-05-27 Thread Jean-Louis Boudart
I just filled an jira ticket for this : https://issues.apache.org/jira/browse/INFRA-7816 2014-05-27 4:42 GMT+02:00 Antoine Levy Lambert anto...@gmx.de: Hello Jean Louis, if you have some cycles for that, you can join infra on IRC ( #asfinfra ) and ask to see whether someone has an idea.

Re: migration to git : next steps - Jenkins

2014-05-27 Thread Antoine Levy Lambert
On May 27, 2014, at 8:53 AM, Jan Matèrne (jhm) apa...@materne.de wrote: Here is an intermediate result and my opinion on that: Open problems = Ant-Build-Matrix has problems on Ubuntu and on Windows. On Windows it seems (to me) that there is no git installed or not

Re: migration to git : next steps

2014-05-26 Thread Maarten Coene
I did some commit tests on Ivy and it seems ok. Could someone also change the configuration on Jenkins? Maarten Van: Stefan Bodewig bode...@apache.org Aan: dev@ant.apache.org Verzonden: zondag 25 mei 20:55 2014 Onderwerp: Re: migration to git : next steps

Re: migration to git : next steps

2014-05-26 Thread Jean-Louis Boudart
The only broken stuff is easyant / ivy documentations as we were using lot of svn:externals (to retrieve latest xooki version for example). svn:externals are not migrated so we need to find a solution for this. 2014-05-25 20:55 GMT+02:00 Stefan Bodewig bode...@apache.org: On 2014-05-23,

Re: migration to git : next steps

2014-05-26 Thread Antoine Levy Lambert
Hello Jean Louis, if you have some cycles for that, you can join infra on IRC ( #asfinfra ) and ask to see whether someone has an idea. Antoine On May 26, 2014, at 9:51 PM, Jean-Louis Boudart jeanlouis.boud...@gmail.com wrote: The only broken stuff is easyant / ivy documentations as we

Re: migration to git : next steps

2014-05-26 Thread Antoine Levy Lambert
I found an article mentioning something similar to what we would need : http://www.leewillis.co.uk/including-git-repo-svn-external/ Antoine On May 26, 2014, at 9:51 PM, Jean-Louis Boudart jeanlouis.boud...@gmail.com wrote: The only broken stuff is easyant / ivy documentations as we were

Re: migration to git : next steps

2014-05-25 Thread Stefan Bodewig
On 2014-05-23, anto...@gmx.de wrote: Jake Farrell has finished the migration, we are asked to verify. Right now I am at work so cannot verify but will look during the weekend. I had a quick look at Ant core, seems to work reasonably. One thing though, the github mirror is now trying to track

Re: migration to git : next steps

2014-05-24 Thread Jean-Louis Boudart
: migration to git : next steps Date: Thu, May 22, 2014 10:17 PM Hi, moving to actual action. jfarrell from infra is setting our svn repo http://svn.apache.org/repos/asf/ant read-only to prepare for the import. The ant site will remain in svn and stay RW during the process. Antoine On May 20

Re: migration to git : next steps

2014-05-23 Thread anto...@gmx.de
...@gmx.de To: Ant Developers List dev@ant.apache.org Subject: migration to git : next steps Date: Thu, May 22, 2014 10:17 PM Hi, moving to actual action. jfarrell from infra is setting our svn repo http://svn.apache.org/repos/asf/ant read-only to prepare for the import. The ant site

Re: migration to git : next steps

2014-05-22 Thread Antoine Levy Lambert
Hi, moving to actual action. jfarrell from infra is setting our svn repo http://svn.apache.org/repos/asf/ant read-only to prepare for the import. The ant site will remain in svn and stay RW during the process. Antoine On May 20, 2014, at 10:25 PM, Matt Sicker boa...@gmail.com wrote: I'm

Re: migration to git : next steps

2014-05-20 Thread Charles Duffy
I'd suggest looking into git-subtree as well, if we wanted to maintain a single-development-tree experience. Submodules have a reputation (well-deserved, IMHO) of being somewhat unwieldy to work with; using git-subtree to manage linked trees can be a bit more automation/setup work, but can also

Re: migration to git : next steps

2014-05-20 Thread Matt Sicker
I'm going to have to look into subtree as I've been using submodule at work lately and it's becoming a huge mess. On 20 May 2014 13:39, Charles Duffy char...@dyfis.net wrote: I'd suggest looking into git-subtree as well, if we wanted to maintain a single-development-tree experience.

Re: migration to git : next steps

2014-05-19 Thread Antoine Levy Lambert
Hi, if someone has some spare cycles, you can contact infra to see whether people have questions about the jira and whether they need help. Apache infra has a chat channel on freenode.net called #asfinfra where committers can join. Antoine On May 19, 2014, at 12:34 AM, Antoine Levy Lambert

Re: migration to git : next steps

2014-05-18 Thread Antoine Levy Lambert
I just created an issue in JIRA : https://issues.apache.org/jira/browse/INFRA-7759 Antoine On May 14, 2014, at 10:54 PM, Antoine Levy Lambert anto...@gmx.de wrote: Migration of the Ant project and subprojects to Git vote :

Re: migration to git : next steps

2014-05-15 Thread Antoine Levy Lambert
I was about to enter an INFRA JIRA for the migration. see below the suggested text. Let me know your thoughts. ——— Migration of the Ant project and subprojects to Git vote : http://ant.1045680.n5.nabble.com/VOTE-migration-to-git-tt5715081.html#none

migration to git : next steps

2014-05-15 Thread Antoine Levy Lambert
To actually migrate to git, we could either make one INFRA JIRA for all the ant family of projects, or do this one step at a time. Concerning the antlibs, I suppose we want one git module for each antlib - we have 6 of them (antunit, compress, dotnet, props, svn, vss) plus a common folder

Re: migration to git : next steps

2014-05-13 Thread Antoine Levy Lambert
Hello Matt, this is interesting - thanks for pointing this out since I am a newbie in git land. does one need to do some advance planning to make a module become a submodule of another repository aggregating the submodules ? there would be a use case for an aggregation of the complete ant

Re: migration to git : next steps

2014-05-13 Thread Matt Sicker
On Tuesday, 13 May 2014, Antoine Levy Lambert anto...@gmx.de wrote: Hello Matt, this is interesting - thanks for pointing this out since I am a newbie in git land. does one need to do some advance planning to make a module become a submodule of another repository aggregating the

migration to git : next steps

2014-05-12 Thread Antoine Levy Lambert
Hi, resending a message which I sent on May 7th but might have been lost completely due to our infrastructure problems last week : To actually migrate to git, we could either make one INFRA JIRA for all the ant family of projects, or do this one step at a time. Concerning the

Re: migration to git : next steps

2014-05-12 Thread Matt Sicker
Something I've been experimenting with is using git submodules. You basically have a repository for each submodule, then you can have another repository that groups them all together for convenience. It's handy for making a sort of stable master that points to the latest tag or something similar.