You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Kristian Rosenvold <kr...@gmail.com> on 2012/11/28 08:52:28 UTC
maven-3 and core-integration-testing git migration, needs verification
The repos are located at:
https://git-wip-us.apache.org/repos/asf/maven.git
https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
Please "test" them, unless anyone has any objections they will become
r/w 24 hours from now.
The "3.1.0" tag is in the git repo, so I suppose this does not affect
the release unless we have to respin.
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Anders Hammar <an...@hammar.net>.
Ah, thanks for clarifying. I'll leave it as is then.
/Anders (mobile)
Den 30 nov 2012 20:24 skrev "Dennis Lundberg" <de...@apache.org>:
> On 2012-11-30 12:52, Anders Hammar wrote:
> >> * Git doesn't seem to be available on the ubuntu-ARM nodes that the jdk
> >> 1.7 job is running on. Kind of surprised as I thought this was handled
> by
> >> the Jenkins plugin and should then not be a problem. Does anyone know?
> >>
> >
> > Sorry, this should have been "the solaris" nodes. The ARM ones are down
> so
> > I haven't been able to verify.
> >
> >
> >> * All solaris and osx nodes are down, so I haven't been able to delete
> the
> >> workspace to remove old stuff nor able to verify. I'll try to monitor
> this
> >> and complete.
> >>
> >
> > And here it should have been "all ubuntu-ARM and osx nodes are down".
> Sorry
> > for the confusion!
> >
> > I also found a IT job on Windows that had a different naming convention.
> > I've switched that one as well and plan on renaming it to align with the
> > others.
>
> I put in some time to get that job to work properly. I had to shorten
> the name of the job, in order to shorten the file system path on the
> Windows slave. Otherwise Jenkins was not able to delete some files due
> to the path being too long (= ~260 chars). So be aware that the job
> might fail for this reason if you give it a name that's too long.
>
> >
> > /Anders
> >
> >
> >>
> >> While switching the embedded job I realigned the configuration with the
> >> other jobs (still using the embedded profile). I hope that's ok and I
> >> didn't break any special stuff in there. This job still fails on some
> ITs
> >> though. Also, the job activates a non-existing profile '
> >> core-integration-testing-maven-3' which should be corrected/removed.
> >>
> >> /Anders
> >>
> >>
> >> On Fri, Nov 30, 2012 at 9:45 AM, Anders Hammar <an...@hammar.net>
> wrote:
> >>
> >>> I'll work on the core-integration-testing-maven-3-xxx ones.
> >>>
> >>> /Anders
> >>>
> >>>
> >>>
> >>> On Fri, Nov 30, 2012 at 9:02 AM, Olivier Lamy <ol...@apache.org>
> wrote:
> >>>
> >>>> I have switched only 2 jenkins jobs:
> >>>> * https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
> >>>> *
> >>>>
> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3/
> >>>>
> >>>> Lack of time today to switch others.
> >>>> If any volunteer that will be appreciate :-)
> >>>>
> >>>>
> >>>> 2012/11/30 Olivier Lamy <ol...@apache.org>:
> >>>>> they are now rw mode.
> >>>>>
> >>>>>
> >>>>> 2012/11/29 Brett Porter <br...@apache.org>:
> >>>>>> Looks good. Compared the current state of these to SVN and confirmed
> >>>> they match. We have a lot of $Id$ to kill in
> maven-integration-testing.
> >>>>>>
> >>>>>> Some empty directories removed in maven-3 - hopefully they don't
> >>>> affect anything. Particular oddities:
> >>>>>>
> >>>>
> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
> >>>>>>
> >>>>
> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
> >>>>>>
> >>>>>> All builds, so should be fine.
> >>>>>>
> >>>>>> Tags and branches look to line up. Looks like the 3.0.4 tag was
> >>>> corrected. I note some old branches have been brought back: e.g.
> >>>> http://svn.apache.org/viewvc?view=revision&revision=983251. This is
> >>>> probably ok, though.
> >>>>>>
> >>>>>> I guess the 3.1.0 tag should be removed from SVN & Git before this
> is
> >>>> wrapped up?
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Brett
> >>>>>>
> >>>>>> On 28/11/2012, at 6:52 PM, Kristian Rosenvold <
> >>>> kristian.rosenvold@gmail.com> wrote:
> >>>>>>
> >>>>>>> The repos are located at:
> >>>>>>>
> >>>>>>> https://git-wip-us.apache.org/repos/asf/maven.git
> >>>>>>>
> >>>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
> >>>>>>>
> >>>>>>>
> >>>>>>> Please "test" them, unless anyone has any objections they will
> become
> >>>>>>> r/w 24 hours from now.
> >>>>>>>
> >>>>>>>
> >>>>>>> The "3.1.0" tag is in the git repo, so I suppose this does not
> affect
> >>>>>>> the release unless we have to respin.
> >>>>>>>
> >>>>>>>
> >>>>>>> Kristian
> >>>>>>>
> >>>>>>>
> ---------------------------------------------------------------------
> >>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Brett Porter
> >>>>>> brett@apache.org
> >>>>>> http://brettporter.wordpress.com/
> >>>>>> http://au.linkedin.com/in/brettporter
> >>>>>> http://twitter.com/brettporter
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Olivier Lamy
> >>>>> Talend: http://coders.talend.com
> >>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Olivier Lamy
> >>>> Talend: http://coders.talend.com
> >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>>
> >>>>
> >>>
> >>
> >
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Dennis Lundberg <de...@apache.org>.
On 2012-11-30 12:52, Anders Hammar wrote:
>> * Git doesn't seem to be available on the ubuntu-ARM nodes that the jdk
>> 1.7 job is running on. Kind of surprised as I thought this was handled by
>> the Jenkins plugin and should then not be a problem. Does anyone know?
>>
>
> Sorry, this should have been "the solaris" nodes. The ARM ones are down so
> I haven't been able to verify.
>
>
>> * All solaris and osx nodes are down, so I haven't been able to delete the
>> workspace to remove old stuff nor able to verify. I'll try to monitor this
>> and complete.
>>
>
> And here it should have been "all ubuntu-ARM and osx nodes are down". Sorry
> for the confusion!
>
> I also found a IT job on Windows that had a different naming convention.
> I've switched that one as well and plan on renaming it to align with the
> others.
I put in some time to get that job to work properly. I had to shorten
the name of the job, in order to shorten the file system path on the
Windows slave. Otherwise Jenkins was not able to delete some files due
to the path being too long (= ~260 chars). So be aware that the job
might fail for this reason if you give it a name that's too long.
>
> /Anders
>
>
>>
>> While switching the embedded job I realigned the configuration with the
>> other jobs (still using the embedded profile). I hope that's ok and I
>> didn't break any special stuff in there. This job still fails on some ITs
>> though. Also, the job activates a non-existing profile '
>> core-integration-testing-maven-3' which should be corrected/removed.
>>
>> /Anders
>>
>>
>> On Fri, Nov 30, 2012 at 9:45 AM, Anders Hammar <an...@hammar.net> wrote:
>>
>>> I'll work on the core-integration-testing-maven-3-xxx ones.
>>>
>>> /Anders
>>>
>>>
>>>
>>> On Fri, Nov 30, 2012 at 9:02 AM, Olivier Lamy <ol...@apache.org> wrote:
>>>
>>>> I have switched only 2 jenkins jobs:
>>>> * https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
>>>> *
>>>> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3/
>>>>
>>>> Lack of time today to switch others.
>>>> If any volunteer that will be appreciate :-)
>>>>
>>>>
>>>> 2012/11/30 Olivier Lamy <ol...@apache.org>:
>>>>> they are now rw mode.
>>>>>
>>>>>
>>>>> 2012/11/29 Brett Porter <br...@apache.org>:
>>>>>> Looks good. Compared the current state of these to SVN and confirmed
>>>> they match. We have a lot of $Id$ to kill in maven-integration-testing.
>>>>>>
>>>>>> Some empty directories removed in maven-3 - hopefully they don't
>>>> affect anything. Particular oddities:
>>>>>>
>>>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
>>>>>>
>>>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
>>>>>>
>>>>>> All builds, so should be fine.
>>>>>>
>>>>>> Tags and branches look to line up. Looks like the 3.0.4 tag was
>>>> corrected. I note some old branches have been brought back: e.g.
>>>> http://svn.apache.org/viewvc?view=revision&revision=983251. This is
>>>> probably ok, though.
>>>>>>
>>>>>> I guess the 3.1.0 tag should be removed from SVN & Git before this is
>>>> wrapped up?
>>>>>>
>>>>>> Cheers,
>>>>>> Brett
>>>>>>
>>>>>> On 28/11/2012, at 6:52 PM, Kristian Rosenvold <
>>>> kristian.rosenvold@gmail.com> wrote:
>>>>>>
>>>>>>> The repos are located at:
>>>>>>>
>>>>>>> https://git-wip-us.apache.org/repos/asf/maven.git
>>>>>>>
>>>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>>>>>>>
>>>>>>>
>>>>>>> Please "test" them, unless anyone has any objections they will become
>>>>>>> r/w 24 hours from now.
>>>>>>>
>>>>>>>
>>>>>>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>>>>>>> the release unless we have to respin.
>>>>>>>
>>>>>>>
>>>>>>> Kristian
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Brett Porter
>>>>>> brett@apache.org
>>>>>> http://brettporter.wordpress.com/
>>>>>> http://au.linkedin.com/in/brettporter
>>>>>> http://twitter.com/brettporter
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Olivier Lamy
>>>>> Talend: http://coders.talend.com
>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>>
>>>>
>>>> --
>>>> Olivier Lamy
>>>> Talend: http://coders.talend.com
>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>>>
>>>
>>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Anders Hammar <an...@hammar.net>.
> * Git doesn't seem to be available on the ubuntu-ARM nodes that the jdk
> 1.7 job is running on. Kind of surprised as I thought this was handled by
> the Jenkins plugin and should then not be a problem. Does anyone know?
>
Sorry, this should have been "the solaris" nodes. The ARM ones are down so
I haven't been able to verify.
> * All solaris and osx nodes are down, so I haven't been able to delete the
> workspace to remove old stuff nor able to verify. I'll try to monitor this
> and complete.
>
And here it should have been "all ubuntu-ARM and osx nodes are down". Sorry
for the confusion!
I also found a IT job on Windows that had a different naming convention.
I've switched that one as well and plan on renaming it to align with the
others.
/Anders
>
> While switching the embedded job I realigned the configuration with the
> other jobs (still using the embedded profile). I hope that's ok and I
> didn't break any special stuff in there. This job still fails on some ITs
> though. Also, the job activates a non-existing profile '
> core-integration-testing-maven-3' which should be corrected/removed.
>
> /Anders
>
>
> On Fri, Nov 30, 2012 at 9:45 AM, Anders Hammar <an...@hammar.net> wrote:
>
>> I'll work on the core-integration-testing-maven-3-xxx ones.
>>
>> /Anders
>>
>>
>>
>> On Fri, Nov 30, 2012 at 9:02 AM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> I have switched only 2 jenkins jobs:
>>> * https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
>>> *
>>> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3/
>>>
>>> Lack of time today to switch others.
>>> If any volunteer that will be appreciate :-)
>>>
>>>
>>> 2012/11/30 Olivier Lamy <ol...@apache.org>:
>>> > they are now rw mode.
>>> >
>>> >
>>> > 2012/11/29 Brett Porter <br...@apache.org>:
>>> >> Looks good. Compared the current state of these to SVN and confirmed
>>> they match. We have a lot of $Id$ to kill in maven-integration-testing.
>>> >>
>>> >> Some empty directories removed in maven-3 - hopefully they don't
>>> affect anything. Particular oddities:
>>> >>
>>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
>>> >>
>>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
>>> >>
>>> >> All builds, so should be fine.
>>> >>
>>> >> Tags and branches look to line up. Looks like the 3.0.4 tag was
>>> corrected. I note some old branches have been brought back: e.g.
>>> http://svn.apache.org/viewvc?view=revision&revision=983251. This is
>>> probably ok, though.
>>> >>
>>> >> I guess the 3.1.0 tag should be removed from SVN & Git before this is
>>> wrapped up?
>>> >>
>>> >> Cheers,
>>> >> Brett
>>> >>
>>> >> On 28/11/2012, at 6:52 PM, Kristian Rosenvold <
>>> kristian.rosenvold@gmail.com> wrote:
>>> >>
>>> >>> The repos are located at:
>>> >>>
>>> >>> https://git-wip-us.apache.org/repos/asf/maven.git
>>> >>>
>>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>>> >>>
>>> >>>
>>> >>> Please "test" them, unless anyone has any objections they will become
>>> >>> r/w 24 hours from now.
>>> >>>
>>> >>>
>>> >>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>>> >>> the release unless we have to respin.
>>> >>>
>>> >>>
>>> >>> Kristian
>>> >>>
>>> >>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>>> >>>
>>> >>
>>> >> --
>>> >> Brett Porter
>>> >> brett@apache.org
>>> >> http://brettporter.wordpress.com/
>>> >> http://au.linkedin.com/in/brettporter
>>> >> http://twitter.com/brettporter
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> >> For additional commands, e-mail: dev-help@maven.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Olivier Lamy
>>> > Talend: http://coders.talend.com
>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Anders Hammar <an...@hammar.net>.
All of the core-integration-testing-maven-3-xxx jobs are now switched
configuration wise. However, I ran into some problems:
* Git doesn't seem to be available on the ubuntu-ARM nodes that the jdk 1.7
job is running on. Kind of surprised as I thought this was handled by the
Jenkins plugin and should then not be a problem. Does anyone know?
* All solaris and osx nodes are down, so I haven't been able to delete the
workspace to remove old stuff nor able to verify. I'll try to monitor this
and complete.
While switching the embedded job I realigned the configuration with the
other jobs (still using the embedded profile). I hope that's ok and I
didn't break any special stuff in there. This job still fails on some ITs
though. Also, the job activates a non-existing profile '
core-integration-testing-maven-3' which should be corrected/removed.
/Anders
On Fri, Nov 30, 2012 at 9:45 AM, Anders Hammar <an...@hammar.net> wrote:
> I'll work on the core-integration-testing-maven-3-xxx ones.
>
> /Anders
>
>
>
> On Fri, Nov 30, 2012 at 9:02 AM, Olivier Lamy <ol...@apache.org> wrote:
>
>> I have switched only 2 jenkins jobs:
>> * https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
>> *
>> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3/
>>
>> Lack of time today to switch others.
>> If any volunteer that will be appreciate :-)
>>
>>
>> 2012/11/30 Olivier Lamy <ol...@apache.org>:
>> > they are now rw mode.
>> >
>> >
>> > 2012/11/29 Brett Porter <br...@apache.org>:
>> >> Looks good. Compared the current state of these to SVN and confirmed
>> they match. We have a lot of $Id$ to kill in maven-integration-testing.
>> >>
>> >> Some empty directories removed in maven-3 - hopefully they don't
>> affect anything. Particular oddities:
>> >>
>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
>> >>
>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
>> >>
>> >> All builds, so should be fine.
>> >>
>> >> Tags and branches look to line up. Looks like the 3.0.4 tag was
>> corrected. I note some old branches have been brought back: e.g.
>> http://svn.apache.org/viewvc?view=revision&revision=983251. This is
>> probably ok, though.
>> >>
>> >> I guess the 3.1.0 tag should be removed from SVN & Git before this is
>> wrapped up?
>> >>
>> >> Cheers,
>> >> Brett
>> >>
>> >> On 28/11/2012, at 6:52 PM, Kristian Rosenvold <
>> kristian.rosenvold@gmail.com> wrote:
>> >>
>> >>> The repos are located at:
>> >>>
>> >>> https://git-wip-us.apache.org/repos/asf/maven.git
>> >>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>> >>>
>> >>>
>> >>> Please "test" them, unless anyone has any objections they will become
>> >>> r/w 24 hours from now.
>> >>>
>> >>>
>> >>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>> >>> the release unless we have to respin.
>> >>>
>> >>>
>> >>> Kristian
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >>> For additional commands, e-mail: dev-help@maven.apache.org
>> >>>
>> >>
>> >> --
>> >> Brett Porter
>> >> brett@apache.org
>> >> http://brettporter.wordpress.com/
>> >> http://au.linkedin.com/in/brettporter
>> >> http://twitter.com/brettporter
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: dev-help@maven.apache.org
>> >>
>> >
>> >
>> >
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Anders Hammar <an...@hammar.net>.
I'll work on the core-integration-testing-maven-3-xxx ones.
/Anders
On Fri, Nov 30, 2012 at 9:02 AM, Olivier Lamy <ol...@apache.org> wrote:
> I have switched only 2 jenkins jobs:
> * https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
> *
> https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3/
>
> Lack of time today to switch others.
> If any volunteer that will be appreciate :-)
>
>
> 2012/11/30 Olivier Lamy <ol...@apache.org>:
> > they are now rw mode.
> >
> >
> > 2012/11/29 Brett Porter <br...@apache.org>:
> >> Looks good. Compared the current state of these to SVN and confirmed
> they match. We have a lot of $Id$ to kill in maven-integration-testing.
> >>
> >> Some empty directories removed in maven-3 - hopefully they don't affect
> anything. Particular oddities:
> >>
> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
> >>
> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
> >>
> >> All builds, so should be fine.
> >>
> >> Tags and branches look to line up. Looks like the 3.0.4 tag was
> corrected. I note some old branches have been brought back: e.g.
> http://svn.apache.org/viewvc?view=revision&revision=983251. This is
> probably ok, though.
> >>
> >> I guess the 3.1.0 tag should be removed from SVN & Git before this is
> wrapped up?
> >>
> >> Cheers,
> >> Brett
> >>
> >> On 28/11/2012, at 6:52 PM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
> >>
> >>> The repos are located at:
> >>>
> >>> https://git-wip-us.apache.org/repos/asf/maven.git
> >>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
> >>>
> >>>
> >>> Please "test" them, unless anyone has any objections they will become
> >>> r/w 24 hours from now.
> >>>
> >>>
> >>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
> >>> the release unless we have to respin.
> >>>
> >>>
> >>> Kristian
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>
> >> --
> >> Brett Porter
> >> brett@apache.org
> >> http://brettporter.wordpress.com/
> >> http://au.linkedin.com/in/brettporter
> >> http://twitter.com/brettporter
> >>
> >>
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >
> >
> >
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Olivier Lamy <ol...@apache.org>.
I have switched only 2 jenkins jobs:
* https://builds.apache.org/view/M-R/view/Maven/job/maven-3.0.x/
* https://builds.apache.org/view/M-R/view/Maven/job/core-integration-testing-maven-3/
Lack of time today to switch others.
If any volunteer that will be appreciate :-)
2012/11/30 Olivier Lamy <ol...@apache.org>:
> they are now rw mode.
>
>
> 2012/11/29 Brett Porter <br...@apache.org>:
>> Looks good. Compared the current state of these to SVN and confirmed they match. We have a lot of $Id$ to kill in maven-integration-testing.
>>
>> Some empty directories removed in maven-3 - hopefully they don't affect anything. Particular oddities:
>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
>> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
>>
>> All builds, so should be fine.
>>
>> Tags and branches look to line up. Looks like the 3.0.4 tag was corrected. I note some old branches have been brought back: e.g. http://svn.apache.org/viewvc?view=revision&revision=983251. This is probably ok, though.
>>
>> I guess the 3.1.0 tag should be removed from SVN & Git before this is wrapped up?
>>
>> Cheers,
>> Brett
>>
>> On 28/11/2012, at 6:52 PM, Kristian Rosenvold <kr...@gmail.com> wrote:
>>
>>> The repos are located at:
>>>
>>> https://git-wip-us.apache.org/repos/asf/maven.git
>>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>>>
>>>
>>> Please "test" them, unless anyone has any objections they will become
>>> r/w 24 hours from now.
>>>
>>>
>>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>>> the release unless we have to respin.
>>>
>>>
>>> Kristian
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>> http://twitter.com/brettporter
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Olivier Lamy <ol...@apache.org>.
they are now rw mode.
2012/11/29 Brett Porter <br...@apache.org>:
> Looks good. Compared the current state of these to SVN and confirmed they match. We have a lot of $Id$ to kill in maven-integration-testing.
>
> Some empty directories removed in maven-3 - hopefully they don't affect anything. Particular oddities:
> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
> http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
>
> All builds, so should be fine.
>
> Tags and branches look to line up. Looks like the 3.0.4 tag was corrected. I note some old branches have been brought back: e.g. http://svn.apache.org/viewvc?view=revision&revision=983251. This is probably ok, though.
>
> I guess the 3.1.0 tag should be removed from SVN & Git before this is wrapped up?
>
> Cheers,
> Brett
>
> On 28/11/2012, at 6:52 PM, Kristian Rosenvold <kr...@gmail.com> wrote:
>
>> The repos are located at:
>>
>> https://git-wip-us.apache.org/repos/asf/maven.git
>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>>
>>
>> Please "test" them, unless anyone has any objections they will become
>> r/w 24 hours from now.
>>
>>
>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>> the release unless we have to respin.
>>
>>
>> Kristian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Brett Porter <br...@apache.org>.
Looks good. Compared the current state of these to SVN and confirmed they match. We have a lot of $Id$ to kill in maven-integration-testing.
Some empty directories removed in maven-3 - hopefully they don't affect anything. Particular oddities:
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/load-extern-profiles-ioex/profiles.xml/
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-embedder/src/test/error-reporting-projects/project-parse-ioex/pom.xml
All builds, so should be fine.
Tags and branches look to line up. Looks like the 3.0.4 tag was corrected. I note some old branches have been brought back: e.g. http://svn.apache.org/viewvc?view=revision&revision=983251. This is probably ok, though.
I guess the 3.1.0 tag should be removed from SVN & Git before this is wrapped up?
Cheers,
Brett
On 28/11/2012, at 6:52 PM, Kristian Rosenvold <kr...@gmail.com> wrote:
> The repos are located at:
>
> https://git-wip-us.apache.org/repos/asf/maven.git
> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>
>
> Please "test" them, unless anyone has any objections they will become
> r/w 24 hours from now.
>
>
> The "3.1.0" tag is in the git repo, so I suppose this does not affect
> the release unless we have to respin.
>
>
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Kristian Rosenvold <kr...@gmail.com>.
This is where things get a little tricky ;) The first time we did this
I had the foresight to ask olivier to add a notice to the repository
about moving to git. This time I forgot, and we're read only now. Doh.
The svn repos are not deleted. I will ask infra if they can add a
notice to the r/o svn repos, maybe update standard procedure for this
too, since it's a shared problem.
Kristian
2012/11/28 Arnaud Héritier <ah...@gmail.com>:
> But after the migration we remove them from SVN ?
> Perhaps with just a README to let people where it was moved ?
> Otherwise it will be really confusing and source of errors. No ?
>
>
> On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
>> SVN is read only while we test, this is standard procedure for migrations.
>>
>> (So if you *must* work on core in the next 24 hours, github is the
>> place to do it ;)
>>
>> Kristian
>>
>>
>>
>> 2012/11/28 Anders Hammar <an...@hammar.net>:
>> > Will the svn repo go read only once we switch, to prevent mistakes?
>> >
>> > /Anders
>> >
>> >
>> > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
>> > kristian.rosenvold@gmail.com> wrote:
>> >
>> >> The repos are located at:
>> >>
>> >> https://git-wip-us.apache.org/repos/asf/maven.git
>> >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>> >>
>> >>
>> >> Please "test" them, unless anyone has any objections they will become
>> >> r/w 24 hours from now.
>> >>
>> >>
>> >> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>> >> the release unless we have to respin.
>> >>
>> >>
>> >> Kristian
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> >> For additional commands, e-mail: dev-help@maven.apache.org
>> >>
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
AW: maven-3 and core-integration-testing git migration, needs verification
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
in short it builds OK now!
I've changed in my settings.xml .m2 to .m22, then have maven-3.0.5 build this maven-3 release.
The build went OK! Then I compared briefly the new .m22 with the old .m2 repository. I merged the
new repository into my old .m2 repository and changed settings.xml back to refer to old .m2 repository
and did a $ mvn clean install; now all has built OK. I don't know, why and when and circumstances my .m2
repository got bad content. but will certainly do this more frequently when problems arise. Some of the
content may well have made it to my .m2/repository through the AXA Winterthur Sonatype Repo-Server.
Sorry for the inconvenience, but I still do not understand what you Kristian said regarding <scm>
Josef
-----Ursprüngliche Nachricht-----
Von: kristian.rosenvold@zenior.no [mailto:kristian.rosenvold@zenior.no] Im Auftrag von Kristian Rosenvold
Gesendet: Mittwoch, 28. November 2012 12:57
An: Maven Developers List
Betreff: Re: maven-3 and core-integration-testing git migration, needs verification
It builds fine here, with or without pom change
Kristian
2012/11/28 Stadelmann Josef <jo...@axa-winterthur.ch>
> in the maven/pom.xml the following is found
> <scm>
> <connection>scm:svn:http://svn.apache.org/repos/asf/maven/maven-3/trunk</connection>
> <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/maven-3/trunk</developerConnection>
> <url>http://svn.apache.org/viewvc/maven/maven-3/trunk</url>
> </scm>
>
> I changed this to
> <scm>
> <connection>scm:git:https//git-wip-us.apache.org/repos/asf/maven.git</connection>
> <developerConnection>scm:git:https//git-wip-us.apache.org/repos/asf/maven.git</developerConnection>
> <url>http://svn.apache.org/viewvc/maven/maven-3/trunk</url>
> </scm>
> and got the build error below.
>
> so what is the proper update to reference via git this maven.git project to build the project properly?
> OR
> Do I hunting a something which is just suppoed to work but does not yet work?
> Josef
>
>
> [buildnumber:create]
> Storing buildNumber: NON-CANONICAL_2012-11-28_11-11_C770817 at
> timestamp: 1354097462927
> 28.11.2012 11:11:02 org.sonatype.guice.bean.reflect.Logs$JULSink warn
> WARNUNG: Error injecting:
> org.apache.maven.scm.provider.svn.svnjava.SvnJavaScmProvider
> java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/SVNException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getDeclaredConstructors(Class.java:1836)
> at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
> at com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:98)
> at com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:629)
> at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:831)
> at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:758)
> at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:255)
> at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:204)
> at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:954)
> at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:987)
> at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:950)
> at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1000)
> at org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:45)
> at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:84)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:52)
> at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at org.sonatype.guice.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:138)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:108)
> at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
> at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
> at org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:83)
> at org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:49)
> at java.util.AbstractMap.get(AbstractMap.java:165)
> at org.apache.maven.scm.manager.AbstractScmManager.getProviderByType(AbstractScmManager.java:136)
> at org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:190)
> at org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:768)
> at org.codehaus.mojo.build.CreateMojo.getScmBranch(CreateMojo.java:619)
> at org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:464)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:544)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:197)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:3
> 52) Caused by: java.lang.ClassNotFoundException:
> org.tmatesoft.svn.core.SVNException
> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 61 more
> ----------------------------------------------------------------------
> --
> Reactor Summary:
>
> Apache Maven ...................................... SUCCESS [5.709s]
> Maven Model ....................................... SUCCESS [10.265s]
> Maven Artifact .................................... SUCCESS [2.496s]
> Maven Plugin API .................................. SUCCESS [3.167s]
> Maven Model Builder ............................... SUCCESS [5.148s]
> Maven Settings .................................... SUCCESS [1.529s]
> Maven Settings Builder ............................ SUCCESS [1.607s]
> Maven Repository Metadata Model ................... SUCCESS [1.700s]
> Maven Aether Provider ............................. SUCCESS [4.774s]
> Maven Core ........................................ FAILURE [1.513s]
> Maven Compat ...................................... SKIPPED Maven
> Embedder .................................... SKIPPED Maven
> Distribution ................................ SKIPPED
> ----------------------------------------------------------------------
> --
> BUILD FAILURE
> ----------------------------------------------------------------------
> --
> Total time: 38.267s
> Finished at: Wed Nov 28 11:11:02 CET 2012 Final Memory: 23M/918M
> ----------------------------------------------------------------------
> --
>
>
>
> Josef
>
> -----Ursprüngliche Nachricht-----
> Von: Arnaud Héritier [mailto:aheritier@gmail.com]
> Gesendet: Mittwoch, 28. November 2012 10:30
> An: Maven Developers List
> Betreff: Re: maven-3 and core-integration-testing git migration, needs
> verification
>
> scm infos will have to be updated to reference git otherwise the buildnumber plugin will try to extract some svn data from the local copy.
>
>
> On Wed, Nov 28, 2012 at 10:12 AM, Stadelmann Josef < josef.stadelmann@axa-winterthur.ch> wrote:
>
>> after a
>> $ git clone https://git-wip-us.apache.org/repos/asf/maven.git
>> I got some mvn install
>> build error. see attachment
>> what can I do?
>> Josef
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Arnaud Héritier [mailto:aheritier@gmail.com]
>> Gesendet: Mittwoch, 28. November 2012 09:34
>> An: Maven Developers List
>> Betreff: Re: maven-3 and core-integration-testing git migration,
>> needs verification
>>
>> But after the migration we remove them from SVN ?
>> Perhaps with just a README to let people where it was moved ?
>> Otherwise it will be really confusing and source of errors. No ?
>>
>>
>> On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
>> kristian.rosenvold@gmail.com> wrote:
>>
>> > SVN is read only while we test, this is standard procedure for
>> migrations.
>> >
>> > (So if you *must* work on core in the next 24 hours, github is the
>> > place to do it ;)
>> >
>> > Kristian
>> >
>> >
>> >
>> > 2012/11/28 Anders Hammar <an...@hammar.net>:
>> > > Will the svn repo go read only once we switch, to prevent mistakes?
>> > >
>> > > /Anders
>> > >
>> > >
>> > > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
>> > > kristian.rosenvold@gmail.com> wrote:
>> > >
>> > >> The repos are located at:
>> > >>
>> > >> https://git-wip-us.apache.org/repos/asf/maven.git
>> > >> https://git-wip-us.apache.org/repos/asf/maven-integration-testin
>> > >> g
>> > >> .g
>> > >> it
>> > >>
>> > >>
>> > >> Please "test" them, unless anyone has any objections they will
>> > >> become r/w 24 hours from now.
>> > >>
>> > >>
>> > >> The "3.1.0" tag is in the git repo, so I suppose this does not
>> > >> affect the release unless we have to respin.
>> > >>
>> > >>
>> > >> Kristian
>> > >>
>> > >> ----------------------------------------------------------------
>> > >> -
>> > >> --
>> > >> -- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> > >> additional commands, e-mail: dev-help@maven.apache.org
>> > >>
>> > >>
>> >
>> > -------------------------------------------------------------------
>> > -
>> > - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> > additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
>>
>>
>> --
>> -----
>> Arnaud Héritier
>> 06-89-76-64-24
>> http://aheritier.net
>> Mail/GTalk: aheritier@gmail.com
>> Twitter/Skype : aheritier
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Kristian Rosenvold <kr...@gmail.com>.
It builds fine here, with or without pom change
Kristian
2012/11/28 Stadelmann Josef <jo...@axa-winterthur.ch>
> in the maven/pom.xml the following is found
> <scm>
> <connection>scm:svn:http://svn.apache.org/repos/asf/maven/maven-3/trunk</connection>
> <developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/maven-3/trunk</developerConnection>
> <url>http://svn.apache.org/viewvc/maven/maven-3/trunk</url>
> </scm>
>
> I changed this to
> <scm>
> <connection>scm:git:https//git-wip-us.apache.org/repos/asf/maven.git</connection>
> <developerConnection>scm:git:https//git-wip-us.apache.org/repos/asf/maven.git</developerConnection>
> <url>http://svn.apache.org/viewvc/maven/maven-3/trunk</url>
> </scm>
> and got the build error below.
>
> so what is the proper update to reference via git this maven.git project to build the project properly?
> OR
> Do I hunting a something which is just suppoed to work but does not yet work?
> Josef
>
>
> [buildnumber:create]
> Storing buildNumber: NON-CANONICAL_2012-11-28_11-11_C770817 at timestamp: 1354097462927
> 28.11.2012 11:11:02 org.sonatype.guice.bean.reflect.Logs$JULSink warn
> WARNUNG: Error injecting: org.apache.maven.scm.provider.svn.svnjava.SvnJavaScmProvider
> java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/SVNException
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getDeclaredConstructors(Class.java:1836)
> at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
> at com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:98)
> at com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:629)
> at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:831)
> at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:758)
> at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:255)
> at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:204)
> at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:954)
> at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:987)
> at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:950)
> at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1000)
> at org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:45)
> at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:84)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:52)
> at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at org.sonatype.guice.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:138)
> at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:108)
> at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018)
> at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
> at com.google.inject.Scopes$1$1.get(Scopes.java:59)
> at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
> at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
> at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
> at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
> at org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:83)
> at org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:49)
> at java.util.AbstractMap.get(AbstractMap.java:165)
> at org.apache.maven.scm.manager.AbstractScmManager.getProviderByType(AbstractScmManager.java:136)
> at org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:190)
> at org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:768)
> at org.codehaus.mojo.build.CreateMojo.getScmBranch(CreateMojo.java:619)
> at org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:464)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:544)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:197)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: java.lang.ClassNotFoundException: org.tmatesoft.svn.core.SVNException
> at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
> at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
> ... 61 more
> ------------------------------------------------------------------------
> Reactor Summary:
>
> Apache Maven ...................................... SUCCESS [5.709s]
> Maven Model ....................................... SUCCESS [10.265s]
> Maven Artifact .................................... SUCCESS [2.496s]
> Maven Plugin API .................................. SUCCESS [3.167s]
> Maven Model Builder ............................... SUCCESS [5.148s]
> Maven Settings .................................... SUCCESS [1.529s]
> Maven Settings Builder ............................ SUCCESS [1.607s]
> Maven Repository Metadata Model ................... SUCCESS [1.700s]
> Maven Aether Provider ............................. SUCCESS [4.774s]
> Maven Core ........................................ FAILURE [1.513s]
> Maven Compat ...................................... SKIPPED
> Maven Embedder .................................... SKIPPED
> Maven Distribution ................................ SKIPPED
> ------------------------------------------------------------------------
> BUILD FAILURE
> ------------------------------------------------------------------------
> Total time: 38.267s
> Finished at: Wed Nov 28 11:11:02 CET 2012
> Final Memory: 23M/918M
> ------------------------------------------------------------------------
>
>
>
> Josef
>
> -----Ursprüngliche Nachricht-----
> Von: Arnaud Héritier [mailto:aheritier@gmail.com]
> Gesendet: Mittwoch, 28. November 2012 10:30
> An: Maven Developers List
> Betreff: Re: maven-3 and core-integration-testing git migration, needs verification
>
> scm infos will have to be updated to reference git otherwise the buildnumber plugin will try to extract some svn data from the local copy.
>
>
> On Wed, Nov 28, 2012 at 10:12 AM, Stadelmann Josef < josef.stadelmann@axa-winterthur.ch> wrote:
>
>> after a
>> $ git clone https://git-wip-us.apache.org/repos/asf/maven.git
>> I got some mvn install
>> build error. see attachment
>> what can I do?
>> Josef
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Arnaud Héritier [mailto:aheritier@gmail.com]
>> Gesendet: Mittwoch, 28. November 2012 09:34
>> An: Maven Developers List
>> Betreff: Re: maven-3 and core-integration-testing git migration, needs
>> verification
>>
>> But after the migration we remove them from SVN ?
>> Perhaps with just a README to let people where it was moved ?
>> Otherwise it will be really confusing and source of errors. No ?
>>
>>
>> On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
>> kristian.rosenvold@gmail.com> wrote:
>>
>> > SVN is read only while we test, this is standard procedure for
>> migrations.
>> >
>> > (So if you *must* work on core in the next 24 hours, github is the
>> > place to do it ;)
>> >
>> > Kristian
>> >
>> >
>> >
>> > 2012/11/28 Anders Hammar <an...@hammar.net>:
>> > > Will the svn repo go read only once we switch, to prevent mistakes?
>> > >
>> > > /Anders
>> > >
>> > >
>> > > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
>> > > kristian.rosenvold@gmail.com> wrote:
>> > >
>> > >> The repos are located at:
>> > >>
>> > >> https://git-wip-us.apache.org/repos/asf/maven.git
>> > >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing
>> > >> .g
>> > >> it
>> > >>
>> > >>
>> > >> Please "test" them, unless anyone has any objections they will
>> > >> become r/w 24 hours from now.
>> > >>
>> > >>
>> > >> The "3.1.0" tag is in the git repo, so I suppose this does not
>> > >> affect the release unless we have to respin.
>> > >>
>> > >>
>> > >> Kristian
>> > >>
>> > >> -----------------------------------------------------------------
>> > >> --
>> > >> -- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> > >> additional commands, e-mail: dev-help@maven.apache.org
>> > >>
>> > >>
>> >
>> > --------------------------------------------------------------------
>> > - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> > additional commands, e-mail: dev-help@maven.apache.org
>> >
>> >
>>
>>
>> --
>> -----
>> Arnaud Héritier
>> 06-89-76-64-24
>> http://aheritier.net
>> Mail/GTalk: aheritier@gmail.com
>> Twitter/Skype : aheritier
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
>> additional commands, e-mail: dev-help@maven.apache.org
>>
>
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
AW: maven-3 and core-integration-testing git migration, needs verification
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
in the maven/pom.xml the following is found
<scm>
<connection>scm:svn:http://svn.apache.org/repos/asf/maven/maven-3/trunk</connection>
<developerConnection>scm:svn:https://svn.apache.org/repos/asf/maven/maven-3/trunk</developerConnection>
<url>http://svn.apache.org/viewvc/maven/maven-3/trunk</url>
</scm>
I changed this to
<scm>
<connection>scm:git:https//git-wip-us.apache.org/repos/asf/maven.git</connection>
<developerConnection>scm:git:https//git-wip-us.apache.org/repos/asf/maven.git</developerConnection>
<url>http://svn.apache.org/viewvc/maven/maven-3/trunk</url>
</scm>
and got the build error below.
so what is the proper update to reference via git this maven.git project to build the project properly?
OR
Do I hunting a something which is just suppoed to work but does not yet work?
Josef
[buildnumber:create]
Storing buildNumber: NON-CANONICAL_2012-11-28_11-11_C770817 at timestamp: 1354097462927
28.11.2012 11:11:02 org.sonatype.guice.bean.reflect.Logs$JULSink warn
WARNUNG: Error injecting: org.apache.maven.scm.provider.svn.svnjava.SvnJavaScmProvider
java.lang.NoClassDefFoundError: org/tmatesoft/svn/core/SVNException
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
at java.lang.Class.getDeclaredConstructors(Class.java:1836)
at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoint.java:245)
at com.google.inject.internal.ConstructorBindingImpl.create(ConstructorBindingImpl.java:98)
at com.google.inject.internal.InjectorImpl.createUninitializedBinding(InjectorImpl.java:629)
at com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:831)
at com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:758)
at com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:255)
at com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:204)
at com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:954)
at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:987)
at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:950)
at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1000)
at org.sonatype.guice.bean.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:45)
at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:84)
at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:52)
at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
at org.sonatype.guice.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:138)
at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:108)
at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:45)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1018)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:59)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:965)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1011)
at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:961)
at org.sonatype.guice.bean.locators.LazyBeanEntry.getValue(LazyBeanEntry.java:83)
at org.sonatype.guice.plexus.locators.LazyPlexusBean.getValue(LazyPlexusBean.java:49)
at java.util.AbstractMap.get(AbstractMap.java:165)
at org.apache.maven.scm.manager.AbstractScmManager.getProviderByType(AbstractScmManager.java:136)
at org.apache.maven.scm.manager.AbstractScmManager.makeScmRepository(AbstractScmManager.java:190)
at org.codehaus.mojo.build.CreateMojo.getScmRepository(CreateMojo.java:768)
at org.codehaus.mojo.build.CreateMojo.getScmBranch(CreateMojo.java:619)
at org.codehaus.mojo.build.CreateMojo.execute(CreateMojo.java:464)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:544)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:197)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: java.lang.ClassNotFoundException: org.tmatesoft.svn.core.SVNException
at org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 61 more
------------------------------------------------------------------------
Reactor Summary:
Apache Maven ...................................... SUCCESS [5.709s]
Maven Model ....................................... SUCCESS [10.265s]
Maven Artifact .................................... SUCCESS [2.496s]
Maven Plugin API .................................. SUCCESS [3.167s]
Maven Model Builder ............................... SUCCESS [5.148s]
Maven Settings .................................... SUCCESS [1.529s]
Maven Settings Builder ............................ SUCCESS [1.607s]
Maven Repository Metadata Model ................... SUCCESS [1.700s]
Maven Aether Provider ............................. SUCCESS [4.774s]
Maven Core ........................................ FAILURE [1.513s]
Maven Compat ...................................... SKIPPED
Maven Embedder .................................... SKIPPED
Maven Distribution ................................ SKIPPED
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 38.267s
Finished at: Wed Nov 28 11:11:02 CET 2012
Final Memory: 23M/918M
------------------------------------------------------------------------
Josef
-----Ursprüngliche Nachricht-----
Von: Arnaud Héritier [mailto:aheritier@gmail.com]
Gesendet: Mittwoch, 28. November 2012 10:30
An: Maven Developers List
Betreff: Re: maven-3 and core-integration-testing git migration, needs verification
scm infos will have to be updated to reference git otherwise the buildnumber plugin will try to extract some svn data from the local copy.
On Wed, Nov 28, 2012 at 10:12 AM, Stadelmann Josef < josef.stadelmann@axa-winterthur.ch> wrote:
> after a
> $ git clone https://git-wip-us.apache.org/repos/asf/maven.git
> I got some mvn install
> build error. see attachment
> what can I do?
> Josef
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Arnaud Héritier [mailto:aheritier@gmail.com]
> Gesendet: Mittwoch, 28. November 2012 09:34
> An: Maven Developers List
> Betreff: Re: maven-3 and core-integration-testing git migration, needs
> verification
>
> But after the migration we remove them from SVN ?
> Perhaps with just a README to let people where it was moved ?
> Otherwise it will be really confusing and source of errors. No ?
>
>
> On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
> > SVN is read only while we test, this is standard procedure for
> migrations.
> >
> > (So if you *must* work on core in the next 24 hours, github is the
> > place to do it ;)
> >
> > Kristian
> >
> >
> >
> > 2012/11/28 Anders Hammar <an...@hammar.net>:
> > > Will the svn repo go read only once we switch, to prevent mistakes?
> > >
> > > /Anders
> > >
> > >
> > > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> > > kristian.rosenvold@gmail.com> wrote:
> > >
> > >> The repos are located at:
> > >>
> > >> https://git-wip-us.apache.org/repos/asf/maven.git
> > >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing
> > >> .g
> > >> it
> > >>
> > >>
> > >> Please "test" them, unless anyone has any objections they will
> > >> become r/w 24 hours from now.
> > >>
> > >>
> > >> The "3.1.0" tag is in the git repo, so I suppose this does not
> > >> affect the release unless we have to respin.
> > >>
> > >>
> > >> Kristian
> > >>
> > >> -----------------------------------------------------------------
> > >> --
> > >> -- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > >> additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >>
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Arnaud Héritier <ah...@gmail.com>.
scm infos will have to be updated to reference git otherwise the
buildnumber plugin will try to extract some svn data from the local copy.
On Wed, Nov 28, 2012 at 10:12 AM, Stadelmann Josef <
josef.stadelmann@axa-winterthur.ch> wrote:
> after a
> $ git clone https://git-wip-us.apache.org/repos/asf/maven.git
> I got some mvn install
> build error. see attachment
> what can I do?
> Josef
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Arnaud Héritier [mailto:aheritier@gmail.com]
> Gesendet: Mittwoch, 28. November 2012 09:34
> An: Maven Developers List
> Betreff: Re: maven-3 and core-integration-testing git migration, needs
> verification
>
> But after the migration we remove them from SVN ?
> Perhaps with just a README to let people where it was moved ?
> Otherwise it will be really confusing and source of errors. No ?
>
>
> On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
> > SVN is read only while we test, this is standard procedure for
> migrations.
> >
> > (So if you *must* work on core in the next 24 hours, github is the
> > place to do it ;)
> >
> > Kristian
> >
> >
> >
> > 2012/11/28 Anders Hammar <an...@hammar.net>:
> > > Will the svn repo go read only once we switch, to prevent mistakes?
> > >
> > > /Anders
> > >
> > >
> > > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> > > kristian.rosenvold@gmail.com> wrote:
> > >
> > >> The repos are located at:
> > >>
> > >> https://git-wip-us.apache.org/repos/asf/maven.git
> > >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.g
> > >> it
> > >>
> > >>
> > >> Please "test" them, unless anyone has any objections they will
> > >> become r/w 24 hours from now.
> > >>
> > >>
> > >> The "3.1.0" tag is in the git repo, so I suppose this does not
> > >> affect the release unless we have to respin.
> > >>
> > >>
> > >> Kristian
> > >>
> > >> -------------------------------------------------------------------
> > >> -- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > >> additional commands, e-mail: dev-help@maven.apache.org
> > >>
> > >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
>
> --
> -----
> Arnaud Héritier
> 06-89-76-64-24
> http://aheritier.net
> Mail/GTalk: aheritier@gmail.com
> Twitter/Skype : aheritier
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
AW: maven-3 and core-integration-testing git migration, needs verification
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
after a
$ git clone https://git-wip-us.apache.org/repos/asf/maven.git
I got some mvn install
build error. see attachment
what can I do?
Josef
-----Ursprüngliche Nachricht-----
Von: Arnaud Héritier [mailto:aheritier@gmail.com]
Gesendet: Mittwoch, 28. November 2012 09:34
An: Maven Developers List
Betreff: Re: maven-3 and core-integration-testing git migration, needs verification
But after the migration we remove them from SVN ?
Perhaps with just a README to let people where it was moved ?
Otherwise it will be really confusing and source of errors. No ?
On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold < kristian.rosenvold@gmail.com> wrote:
> SVN is read only while we test, this is standard procedure for migrations.
>
> (So if you *must* work on core in the next 24 hours, github is the
> place to do it ;)
>
> Kristian
>
>
>
> 2012/11/28 Anders Hammar <an...@hammar.net>:
> > Will the svn repo go read only once we switch, to prevent mistakes?
> >
> > /Anders
> >
> >
> > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> > kristian.rosenvold@gmail.com> wrote:
> >
> >> The repos are located at:
> >>
> >> https://git-wip-us.apache.org/repos/asf/maven.git
> >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.g
> >> it
> >>
> >>
> >> Please "test" them, unless anyone has any objections they will
> >> become r/w 24 hours from now.
> >>
> >>
> >> The "3.1.0" tag is in the git repo, so I suppose this does not
> >> affect the release unless we have to respin.
> >>
> >>
> >> Kristian
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> >> additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Arnaud Héritier <ah...@gmail.com>.
But after the migration we remove them from SVN ?
Perhaps with just a README to let people where it was moved ?
Otherwise it will be really confusing and source of errors. No ?
On Wed, Nov 28, 2012 at 9:02 AM, Kristian Rosenvold <
kristian.rosenvold@gmail.com> wrote:
> SVN is read only while we test, this is standard procedure for migrations.
>
> (So if you *must* work on core in the next 24 hours, github is the
> place to do it ;)
>
> Kristian
>
>
>
> 2012/11/28 Anders Hammar <an...@hammar.net>:
> > Will the svn repo go read only once we switch, to prevent mistakes?
> >
> > /Anders
> >
> >
> > On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> > kristian.rosenvold@gmail.com> wrote:
> >
> >> The repos are located at:
> >>
> >> https://git-wip-us.apache.org/repos/asf/maven.git
> >> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
> >>
> >>
> >> Please "test" them, unless anyone has any objections they will become
> >> r/w 24 hours from now.
> >>
> >>
> >> The "3.1.0" tag is in the git repo, so I suppose this does not affect
> >> the release unless we have to respin.
> >>
> >>
> >> Kristian
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
-----
Arnaud Héritier
06-89-76-64-24
http://aheritier.net
Mail/GTalk: aheritier@gmail.com
Twitter/Skype : aheritier
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Kristian Rosenvold <kr...@gmail.com>.
SVN is read only while we test, this is standard procedure for migrations.
(So if you *must* work on core in the next 24 hours, github is the
place to do it ;)
Kristian
2012/11/28 Anders Hammar <an...@hammar.net>:
> Will the svn repo go read only once we switch, to prevent mistakes?
>
> /Anders
>
>
> On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
> kristian.rosenvold@gmail.com> wrote:
>
>> The repos are located at:
>>
>> https://git-wip-us.apache.org/repos/asf/maven.git
>> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>>
>>
>> Please "test" them, unless anyone has any objections they will become
>> r/w 24 hours from now.
>>
>>
>> The "3.1.0" tag is in the git repo, so I suppose this does not affect
>> the release unless we have to respin.
>>
>>
>> Kristian
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Olivier Lamy <ol...@apache.org>.
Yup and already read only now.
--
Olivier
Le 28 nov. 2012 09:00, "Anders Hammar" <an...@hammar.net> a écrit :
Re: maven-3 and core-integration-testing git migration, needs verification
Posted by Anders Hammar <an...@hammar.net>.
Will the svn repo go read only once we switch, to prevent mistakes?
/Anders
On Wed, Nov 28, 2012 at 8:52 AM, Kristian Rosenvold <
kristian.rosenvold@gmail.com> wrote:
> The repos are located at:
>
> https://git-wip-us.apache.org/repos/asf/maven.git
> https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
>
>
> Please "test" them, unless anyone has any objections they will become
> r/w 24 hours from now.
>
>
> The "3.1.0" tag is in the git repo, so I suppose this does not affect
> the release unless we have to respin.
>
>
> Kristian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>