You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Nicolas Lalevée <ni...@hibnet.org> on 2014/11/09 17:56:43 UTC
[VOTE] Release Ivy 2.4.0
I have built a release candidate for Ivy 2.4.0
The git tag of this release is: https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
The artifacts has been published to: https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
Do you vote for the release of these binaries?
[ ] Yes
[ ] No
Regards,
Nicolas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [VOTE] Release Ivy 2.4.0
Posted by Jean-Louis Boudart <je...@gmail.com>.
I asked INFRA to create a git readonly mirror to this directory (
https://issues.apache.org/jira/browse/INFRA-8627).
Stay tuned!
2014-11-12 20:13 GMT+01:00 Maarten Coene <ma...@yahoo.com.invalid>:
> The style folder was included using svn:externals and is part of the ivy
> site:
> https://svn.apache.org/repos/asf/ant/site/ivy/sources/style/
>
> We should rebuild the release with this folder included imho.
>
> Maarten
>
>
>
> ________________________________
> Van: Jean-Louis Boudart <je...@gmail.com>
> Aan: Ant Developers List <de...@ant.apache.org>; Maarten Coene <
> maarten_coene@yahoo.com>
> Verzonden: woensdag 12 november 10:05 2014
> Onderwerp: Re: [VOTE] Release Ivy 2.4.0
>
>
> +1 for expect the style folder
>
> Where does this style folder is ? Is it somewhere in SVN / GIT ?
>
>
> 2014-11-10 0:24 GMT+01:00 Maarten Coene <ma...@yahoo.com.invalid>:
>
> > Thank you for creating the release Nicolas :-)
> >
> > I've noticed that the "style" directory is missing in the documentation
> in
> > apache-ivy-2.4.0-bin.zip (and probably the others too).
> > This makes the documentation inside these binaries look a bit 'basic'.
> >
> > Maarten
> >
> >
> >
> > ________________________________
> > Van: Nicolas Lalevée <ni...@hibnet.org>
> > Aan: Ant Developers List <de...@ant.apache.org>
> > Verzonden: zondag 9 november 17:56 2014
> > Onderwerp: [VOTE] Release Ivy 2.4.0
> >
> >
> > I have built a release candidate for Ivy 2.4.0
> >
> > The git tag of this release is:
> >
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
> >
> > The artifacts has been published to:
> > https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
> >
> > Do you vote for the release of these binaries?
> >
> > [ ] Yes
> > [ ] No
> >
> > Regards,
> > Nicolas
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
>
>
>
> --
> Jean Louis Boudart
> Independent consultant
> Apache EasyAnt commiter http://ant.apache.org/easyant/
>
--
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/
Re: [VOTE] Release Ivy 2.4.0
Posted by Maarten Coene <ma...@yahoo.com.INVALID>.
The style folder was included using svn:externals and is part of the ivy site:
https://svn.apache.org/repos/asf/ant/site/ivy/sources/style/
We should rebuild the release with this folder included imho.
Maarten
________________________________
Van: Jean-Louis Boudart <je...@gmail.com>
Aan: Ant Developers List <de...@ant.apache.org>; Maarten Coene <ma...@yahoo.com>
Verzonden: woensdag 12 november 10:05 2014
Onderwerp: Re: [VOTE] Release Ivy 2.4.0
+1 for expect the style folder
Where does this style folder is ? Is it somewhere in SVN / GIT ?
2014-11-10 0:24 GMT+01:00 Maarten Coene <ma...@yahoo.com.invalid>:
> Thank you for creating the release Nicolas :-)
>
> I've noticed that the "style" directory is missing in the documentation in
> apache-ivy-2.4.0-bin.zip (and probably the others too).
> This makes the documentation inside these binaries look a bit 'basic'.
>
> Maarten
>
>
>
> ________________________________
> Van: Nicolas Lalevée <ni...@hibnet.org>
> Aan: Ant Developers List <de...@ant.apache.org>
> Verzonden: zondag 9 november 17:56 2014
> Onderwerp: [VOTE] Release Ivy 2.4.0
>
>
> I have built a release candidate for Ivy 2.4.0
>
> The git tag of this release is:
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
>
> The artifacts has been published to:
> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
>
> Do you vote for the release of these binaries?
>
> [ ] Yes
> [ ] No
>
> Regards,
> Nicolas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
--
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/
Re: [VOTE] Release Ivy 2.4.0
Posted by Jean-Louis Boudart <je...@gmail.com>.
+1 for expect the style folder
Where does this style folder is ? Is it somewhere in SVN / GIT ?
2014-11-10 0:24 GMT+01:00 Maarten Coene <ma...@yahoo.com.invalid>:
> Thank you for creating the release Nicolas :-)
>
> I've noticed that the "style" directory is missing in the documentation in
> apache-ivy-2.4.0-bin.zip (and probably the others too).
> This makes the documentation inside these binaries look a bit 'basic'.
>
> Maarten
>
>
>
> ________________________________
> Van: Nicolas Lalevée <ni...@hibnet.org>
> Aan: Ant Developers List <de...@ant.apache.org>
> Verzonden: zondag 9 november 17:56 2014
> Onderwerp: [VOTE] Release Ivy 2.4.0
>
>
> I have built a release candidate for Ivy 2.4.0
>
> The git tag of this release is:
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
>
> The artifacts has been published to:
> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
>
> Do you vote for the release of these binaries?
>
> [ ] Yes
> [ ] No
>
> Regards,
> Nicolas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
--
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/
Re: [VOTE] Release Ivy 2.4.0
Posted by Maarten Coene <ma...@yahoo.com.INVALID>.
Thank you for creating the release Nicolas :-)
I've noticed that the "style" directory is missing in the documentation in apache-ivy-2.4.0-bin.zip (and probably the others too).
This makes the documentation inside these binaries look a bit 'basic'.
Maarten
________________________________
Van: Nicolas Lalevée <ni...@hibnet.org>
Aan: Ant Developers List <de...@ant.apache.org>
Verzonden: zondag 9 november 17:56 2014
Onderwerp: [VOTE] Release Ivy 2.4.0
I have built a release candidate for Ivy 2.4.0
The git tag of this release is: https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
The artifacts has been published to: https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
Do you vote for the release of these binaries?
[ ] Yes
[ ] No
Regards,
Nicolas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Nicolas Lalevée <ni...@hibnet.org>.
I pushed the current style folder into git so we can go forward with the release. If we have a better process later, we will just change it.
Nicolas
> Le 10 déc. 2014 à 10:57, Nicolas Lalevée <ni...@hibnet.org> a écrit :
>
> Note that the style files are also useful to edit the doc within Ivy’s code source. So this needs to be easily fetchable for contributors.
>
> Having to maintain the styles folders between the source and the site one doesn’t seem that a burden. I prefer to have the burden on committers than on contributors.
>
> Nicolas
>
>> Le 10 déc. 2014 à 09:28, Jan Matèrne (jhm) <ap...@materne.de> a écrit :
>>
>> Security hint: 'pushing' is not as secure as 'polling' here ... Maybe
>> passwords have to be configured...
>>
>> Jan
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Jan Matèrne (jhm) [mailto:apache@materne.de]
>>> Gesendet: Mittwoch, 10. Dezember 2014 07:57
>>> An: 'Ant Developers List'
>>> Betreff: AW: [CANCELED][VOTE] Release Ivy 2.4.0
>>>
>>>> The ideal solutions to all this headaches would probably to have
>>>> everything
>>> in >git (including ivy's website), unfortunatly as far as i know we
>>> can't publish >website via git @ASF for the moment. Infra offers a
>>> gitpubsub feature but i >read somewhere that we can't use it to publish
>>> websites.
>>>
>>> Would a Jenkins job help here?
>>> It could build the website from git and 'push' (not git push ;) it
>>> somewhere.
>>>
>>>
>>> Jan
>>>
>>>
>>>
>>>> -----Ursprüngliche Nachricht-----
>>>> Von: Antoine Levy Lambert [mailto:antoine@gmx.de]
>>>> Gesendet: Mittwoch, 10. Dezember 2014 01:18
>>>> An: Ant Developers List
>>>> Betreff: Re: [CANCELED][VOTE] Release Ivy 2.4.0
>>>>
>>>> Yes !!!
>>>>
>>>> Antoine
>>>> On Dec 9, 2014, at 9:36 AM, Stefan Bodewig <bo...@apache.org>
>>> wrote:
>>>>
>>>>> On 2014-12-09, Jean-Louis Boudart wrote:
>>>>>
>>>>>> This directory containing styles (css,etc...) is used by both
>>>> website
>>>>>> (which is still in svn and published via svnpubsub) and project
>>>>>> documentation (which is in ivy's git repository). As infra was
>>>>>> proposing git-svn mirror it was a good compromise. Website could
>>>> live
>>>>>> using svn:externals to fetch appropriate files, and project
>>>>>> documentation could use git submodules.
>>>>>
>>>>>> Considering we're talking about a few files that doesn't move too
>>>>>> often i was suggesting duplicating them by hand and/or automating
>>>>>> it via a script during the release process.
>>>>>
>>>>> OK, I think I understand. If this is really only needed for a
>>>> release
>>>>> build, having the build process fetch them from svn (which I think
>>>> you
>>>>> are suggesting) seems to be a good choice.
>>>>>
>>>>> Stefan
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
>>>> commands, e-mail: dev-help@ant.apache.org
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
>>> commands, e-mail: dev-help@ant.apache.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Nicolas Lalevée <ni...@hibnet.org>.
Note that the style files are also useful to edit the doc within Ivy’s code source. So this needs to be easily fetchable for contributors.
Having to maintain the styles folders between the source and the site one doesn’t seem that a burden. I prefer to have the burden on committers than on contributors.
Nicolas
> Le 10 déc. 2014 à 09:28, Jan Matèrne (jhm) <ap...@materne.de> a écrit :
>
> Security hint: 'pushing' is not as secure as 'polling' here ... Maybe
> passwords have to be configured...
>
> Jan
>
>> -----Ursprüngliche Nachricht-----
>> Von: Jan Matèrne (jhm) [mailto:apache@materne.de]
>> Gesendet: Mittwoch, 10. Dezember 2014 07:57
>> An: 'Ant Developers List'
>> Betreff: AW: [CANCELED][VOTE] Release Ivy 2.4.0
>>
>>> The ideal solutions to all this headaches would probably to have
>>> everything
>> in >git (including ivy's website), unfortunatly as far as i know we
>> can't publish >website via git @ASF for the moment. Infra offers a
>> gitpubsub feature but i >read somewhere that we can't use it to publish
>> websites.
>>
>> Would a Jenkins job help here?
>> It could build the website from git and 'push' (not git push ;) it
>> somewhere.
>>
>>
>> Jan
>>
>>
>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: Antoine Levy Lambert [mailto:antoine@gmx.de]
>>> Gesendet: Mittwoch, 10. Dezember 2014 01:18
>>> An: Ant Developers List
>>> Betreff: Re: [CANCELED][VOTE] Release Ivy 2.4.0
>>>
>>> Yes !!!
>>>
>>> Antoine
>>> On Dec 9, 2014, at 9:36 AM, Stefan Bodewig <bo...@apache.org>
>> wrote:
>>>
>>>> On 2014-12-09, Jean-Louis Boudart wrote:
>>>>
>>>>> This directory containing styles (css,etc...) is used by both
>>> website
>>>>> (which is still in svn and published via svnpubsub) and project
>>>>> documentation (which is in ivy's git repository). As infra was
>>>>> proposing git-svn mirror it was a good compromise. Website could
>>> live
>>>>> using svn:externals to fetch appropriate files, and project
>>>>> documentation could use git submodules.
>>>>
>>>>> Considering we're talking about a few files that doesn't move too
>>>>> often i was suggesting duplicating them by hand and/or automating
>>>>> it via a script during the release process.
>>>>
>>>> OK, I think I understand. If this is really only needed for a
>>> release
>>>> build, having the build process fetch them from svn (which I think
>>> you
>>>> are suggesting) seems to be a good choice.
>>>>
>>>> Stefan
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
>>> commands, e-mail: dev-help@ant.apache.org
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
>> commands, e-mail: dev-help@ant.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
AW: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
Security hint: 'pushing' is not as secure as 'polling' here ... Maybe
passwords have to be configured...
Jan
> -----Ursprüngliche Nachricht-----
> Von: Jan Matèrne (jhm) [mailto:apache@materne.de]
> Gesendet: Mittwoch, 10. Dezember 2014 07:57
> An: 'Ant Developers List'
> Betreff: AW: [CANCELED][VOTE] Release Ivy 2.4.0
>
> >The ideal solutions to all this headaches would probably to have
> >everything
> in >git (including ivy's website), unfortunatly as far as i know we
> can't publish >website via git @ASF for the moment. Infra offers a
> gitpubsub feature but i >read somewhere that we can't use it to publish
> websites.
>
> Would a Jenkins job help here?
> It could build the website from git and 'push' (not git push ;) it
> somewhere.
>
>
> Jan
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Antoine Levy Lambert [mailto:antoine@gmx.de]
> > Gesendet: Mittwoch, 10. Dezember 2014 01:18
> > An: Ant Developers List
> > Betreff: Re: [CANCELED][VOTE] Release Ivy 2.4.0
> >
> > Yes !!!
> >
> > Antoine
> > On Dec 9, 2014, at 9:36 AM, Stefan Bodewig <bo...@apache.org>
> wrote:
> >
> > > On 2014-12-09, Jean-Louis Boudart wrote:
> > >
> > >> This directory containing styles (css,etc...) is used by both
> > website
> > >> (which is still in svn and published via svnpubsub) and project
> > >> documentation (which is in ivy's git repository). As infra was
> > >> proposing git-svn mirror it was a good compromise. Website could
> > live
> > >> using svn:externals to fetch appropriate files, and project
> > >> documentation could use git submodules.
> > >
> > >> Considering we're talking about a few files that doesn't move too
> > >> often i was suggesting duplicating them by hand and/or automating
> > >> it via a script during the release process.
> > >
> > > OK, I think I understand. If this is really only needed for a
> > release
> > > build, having the build process fetch them from svn (which I think
> > you
> > > are suggesting) seems to be a good choice.
> > >
> > > Stefan
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> > commands, e-mail: dev-help@ant.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> commands, e-mail: dev-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
AW: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by "Jan Matèrne (jhm)" <ap...@materne.de>.
>The ideal solutions to all this headaches would probably to have everything
in >git (including ivy's website), unfortunatly as far as i know we can't
publish >website via git @ASF for the moment. Infra offers a gitpubsub
feature but i >read somewhere that we can't use it to publish websites.
Would a Jenkins job help here?
It could build the website from git and 'push' (not git push ;) it
somewhere.
Jan
> -----Ursprüngliche Nachricht-----
> Von: Antoine Levy Lambert [mailto:antoine@gmx.de]
> Gesendet: Mittwoch, 10. Dezember 2014 01:18
> An: Ant Developers List
> Betreff: Re: [CANCELED][VOTE] Release Ivy 2.4.0
>
> Yes !!!
>
> Antoine
> On Dec 9, 2014, at 9:36 AM, Stefan Bodewig <bo...@apache.org> wrote:
>
> > On 2014-12-09, Jean-Louis Boudart wrote:
> >
> >> This directory containing styles (css,etc...) is used by both
> website
> >> (which is still in svn and published via svnpubsub) and project
> >> documentation (which is in ivy's git repository). As infra was
> >> proposing git-svn mirror it was a good compromise. Website could
> live
> >> using svn:externals to fetch appropriate files, and project
> >> documentation could use git submodules.
> >
> >> Considering we're talking about a few files that doesn't move too
> >> often i was suggesting duplicating them by hand and/or automating it
> >> via a script during the release process.
> >
> > OK, I think I understand. If this is really only needed for a
> release
> > build, having the build process fetch them from svn (which I think
> you
> > are suggesting) seems to be a good choice.
> >
> > Stefan
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional
> commands, e-mail: dev-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Antoine Levy Lambert <an...@gmx.de>.
Yes !!!
Antoine
On Dec 9, 2014, at 9:36 AM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2014-12-09, Jean-Louis Boudart wrote:
>
>> This directory containing styles (css,etc...) is used by both website
>> (which is still in svn and published via svnpubsub) and project
>> documentation (which is in ivy's git repository). As infra was proposing
>> git-svn mirror it was a good compromise. Website could live using
>> svn:externals to fetch appropriate files, and project documentation could
>> use git submodules.
>
>> Considering we're talking about a few files that doesn't move too often i
>> was suggesting duplicating them by hand and/or automating it via a script
>> during the release process.
>
> OK, I think I understand. If this is really only needed for a release
> build, having the build process fetch them from svn (which I think you
> are suggesting) seems to be a good choice.
>
> Stefan
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Stefan Bodewig <bo...@apache.org>.
On 2014-12-09, Jean-Louis Boudart wrote:
> This directory containing styles (css,etc...) is used by both website
> (which is still in svn and published via svnpubsub) and project
> documentation (which is in ivy's git repository). As infra was proposing
> git-svn mirror it was a good compromise. Website could live using
> svn:externals to fetch appropriate files, and project documentation could
> use git submodules.
> Considering we're talking about a few files that doesn't move too often i
> was suggesting duplicating them by hand and/or automating it via a script
> during the release process.
OK, I think I understand. If this is really only needed for a release
build, having the build process fetch them from svn (which I think you
are suggesting) seems to be a good choice.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Jean-Louis Boudart <je...@gmail.com>.
Thanks for pointers stefan, i never used svn2git but i'll have a closer
look.
We need to choose what will be our reference.
Let me give you some context :
This directory containing styles (css,etc...) is used by both website
(which is still in svn and published via svnpubsub) and project
documentation (which is in ivy's git repository). As infra was proposing
git-svn mirror it was a good compromise. Website could live using
svn:externals to fetch appropriate files, and project documentation could
use git submodules.
If we can't have this svn mirror i don't think we could move thoses file in
a new git repository as website will not be able to access it.
The ideal solutions to all this headaches would probably to have everything
in git (including ivy's website), unfortunatly as far as i know we can't
publish website via git @ASF for the moment. Infra offers a gitpubsub
feature but i read somewhere that we can't use it to publish websites.
Considering we're talking about a few files that doesn't move too often i
was suggesting duplicating them by hand and/or automating it via a script
during the release process.
2014-12-09 9:59 GMT+01:00 Stefan Bodewig <bo...@apache.org>:
> On 2014-12-09, Jean-Louis Boudart wrote:
>
> > If we need to find another solution then we should probably duplicate
> > styles on git as they do not move too often. We can then improve this by
> > adding some automation to replicate changes from our new reference (GIT)
> in
> > svn website like Nicolas has done when handling documentation of released
> > versions.
>
> I've migrated xmlunit from svn to git[1] using svn2git[2] quite easily,
> so starting with a fresh git repo and the pushing such a migrated code
> base would preserve all history.
>
> If you really need to keep two copies around, then "svn2git --rebase"
> might help with it - it would certainly be a manual step.
>
> Stefan
>
> [1] https://github.com/xmlunit/xmlunit
> [2] https://github.com/nirvdrum/svn2git
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Stefan Bodewig <bo...@apache.org>.
On 2014-12-09, Jean-Louis Boudart wrote:
> If we need to find another solution then we should probably duplicate
> styles on git as they do not move too often. We can then improve this by
> adding some automation to replicate changes from our new reference (GIT) in
> svn website like Nicolas has done when handling documentation of released
> versions.
I've migrated xmlunit from svn to git[1] using svn2git[2] quite easily,
so starting with a fresh git repo and the pushing such a migrated code
base would preserve all history.
If you really need to keep two copies around, then "svn2git --rebase"
might help with it - it would certainly be a manual step.
Stefan
[1] https://github.com/xmlunit/xmlunit
[2] https://github.com/nirvdrum/svn2git
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Jean-Louis Boudart <je...@gmail.com>.
I thought it was possible as it was done for xooki (which doesn't seems to
have trunk/tags/branches structure see
https://issues.apache.org/jira/browse/INFRA-7816).
If we need to find another solution then we should probably duplicate
styles on git as they do not move too often. We can then improve this by
adding some automation to replicate changes from our new reference (GIT) in
svn website like Nicolas has done when handling documentation of released
versions.
2014-12-09 5:33 GMT+01:00 Antoine Levy Lambert <an...@gmx.de>:
> On the infrastructure list Gavin wrote that infra is not able to create
> the mirror of the styles folder of the ivy doc that has been requested by
> Jean-Louis.
>
> The reason being that infra can only create a mirror from a structure
> having tags and trunk.
>
> @Jean-Louis, would creating a new git repository that we would populate
> manually work ?
>
> Regards,
>
> Antoine
>
>
> On Dec 3, 2014, at 5:05 PM, JBaruch <jb...@jfrog.com> wrote:
>
> > documentation added.
> >
> > Baruch.
> >
> > --
> > JFrog Developer Advocate
> > www.jfrog.com
> > +972544954353
> > @jbaruch <https://twitter.com/jbaruch/>
> > http://linkd.in/jbaruch
> >
> > On Wed, Dec 3, 2014 at 1:37 PM, JBaruch <jb...@jfrog.com> wrote:
> >
> >> Perfect, we are on it.
> >> On 3 Dec 2014 12:29, "Nicolas Lalevée" <ni...@hibnet.org>
> wrote:
> >>
> >>> I would still would like some doc.
> >>>
> >>> The doc in the code source is still broken and it make it difficult to
> >>> know how it is rendered.
> >>> In the mean time time, you could write a page. I will then ensure
> myself
> >>> that is proper included in the doc and rendered when the build will be
> >>> fixed. You can take this file as an exemple:
> >>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
> >>> <
> >>>
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
> >>>>
> >>>
> >>> Nicolas
> >>>
> >>>> Le 2 déc. 2014 à 22:56, JBaruch <jb...@jfrog.com> a écrit :
> >>>>
> >>>> Can we use this opportunity to sneak IVY-1474 in?
> >>>>
> >>>> Baruch.
> >>>>
> >>>> --
> >>>> JFrog Developer Advocate
> >>>> www.jfrog.com
> >>>> +972544954353
> >>>> @jbaruch <https://twitter.com/jbaruch/>
> >>>> http://linkd.in/jbaruch
> >>>>
> >>>> On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée <
> >>> nicolas.lalevee@hibnet.org>
> >>>> wrote:
> >>>>
> >>>>> It was so obvious that this release candidate should be canceled
> that I
> >>>>> forgot to officially set it. Here it is.
> >>>>>
> >>>>> I see that the infra ticket is resolved. Jean-Louis spotted some
> issues
> >>>>> with it though. But I guess we will retry very soon.
> >>>>>
> >>>>> Nicolas
> >>>>>
> >>>>>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée <nicolas.lalevee@hibnet.org
> >
> >>> a
> >>>>> écrit :
> >>>>>>
> >>>>>> I have built a release candidate for Ivy 2.4.0
> >>>>>>
> >>>>>> The git tag of this release is:
> >>>>>
> >>>
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
> >>>>>>
> >>>>>> The artifacts has been published to:
> >>>>> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
> >>>>>>
> >>>>>> Do you vote for the release of these binaries?
> >>>>>>
> >>>>>> [ ] Yes
> >>>>>> [ ] No
> >>>>>>
> >>>>>> Regards,
> >>>>>> Nicolas
> >>>>>>
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>>>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>>>
> >>>>>
> >>>
> >>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
--
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Antoine Levy Lambert <an...@gmx.de>.
On the infrastructure list Gavin wrote that infra is not able to create the mirror of the styles folder of the ivy doc that has been requested by Jean-Louis.
The reason being that infra can only create a mirror from a structure having tags and trunk.
@Jean-Louis, would creating a new git repository that we would populate manually work ?
Regards,
Antoine
On Dec 3, 2014, at 5:05 PM, JBaruch <jb...@jfrog.com> wrote:
> documentation added.
>
> Baruch.
>
> --
> JFrog Developer Advocate
> www.jfrog.com
> +972544954353
> @jbaruch <https://twitter.com/jbaruch/>
> http://linkd.in/jbaruch
>
> On Wed, Dec 3, 2014 at 1:37 PM, JBaruch <jb...@jfrog.com> wrote:
>
>> Perfect, we are on it.
>> On 3 Dec 2014 12:29, "Nicolas Lalevée" <ni...@hibnet.org> wrote:
>>
>>> I would still would like some doc.
>>>
>>> The doc in the code source is still broken and it make it difficult to
>>> know how it is rendered.
>>> In the mean time time, you could write a page. I will then ensure myself
>>> that is proper included in the doc and rendered when the build will be
>>> fixed. You can take this file as an exemple:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
>>> <
>>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
>>>>
>>>
>>> Nicolas
>>>
>>>> Le 2 déc. 2014 à 22:56, JBaruch <jb...@jfrog.com> a écrit :
>>>>
>>>> Can we use this opportunity to sneak IVY-1474 in?
>>>>
>>>> Baruch.
>>>>
>>>> --
>>>> JFrog Developer Advocate
>>>> www.jfrog.com
>>>> +972544954353
>>>> @jbaruch <https://twitter.com/jbaruch/>
>>>> http://linkd.in/jbaruch
>>>>
>>>> On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée <
>>> nicolas.lalevee@hibnet.org>
>>>> wrote:
>>>>
>>>>> It was so obvious that this release candidate should be canceled that I
>>>>> forgot to officially set it. Here it is.
>>>>>
>>>>> I see that the infra ticket is resolved. Jean-Louis spotted some issues
>>>>> with it though. But I guess we will retry very soon.
>>>>>
>>>>> Nicolas
>>>>>
>>>>>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée <ni...@hibnet.org>
>>> a
>>>>> écrit :
>>>>>>
>>>>>> I have built a release candidate for Ivy 2.4.0
>>>>>>
>>>>>> The git tag of this release is:
>>>>>
>>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
>>>>>>
>>>>>> The artifacts has been published to:
>>>>> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
>>>>>>
>>>>>> Do you vote for the release of these binaries?
>>>>>>
>>>>>> [ ] Yes
>>>>>> [ ] No
>>>>>>
>>>>>> Regards,
>>>>>> Nicolas
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>>
>>>>>
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by JBaruch <jb...@jfrog.com>.
documentation added.
Baruch.
--
JFrog Developer Advocate
www.jfrog.com
+972544954353
@jbaruch <https://twitter.com/jbaruch/>
http://linkd.in/jbaruch
On Wed, Dec 3, 2014 at 1:37 PM, JBaruch <jb...@jfrog.com> wrote:
> Perfect, we are on it.
> On 3 Dec 2014 12:29, "Nicolas Lalevée" <ni...@hibnet.org> wrote:
>
>> I would still would like some doc.
>>
>> The doc in the code source is still broken and it make it difficult to
>> know how it is rendered.
>> In the mean time time, you could write a page. I will then ensure myself
>> that is proper included in the doc and rendered when the build will be
>> fixed. You can take this file as an exemple:
>>
>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
>> <
>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
>> >
>>
>> Nicolas
>>
>> > Le 2 déc. 2014 à 22:56, JBaruch <jb...@jfrog.com> a écrit :
>> >
>> > Can we use this opportunity to sneak IVY-1474 in?
>> >
>> > Baruch.
>> >
>> > --
>> > JFrog Developer Advocate
>> > www.jfrog.com
>> > +972544954353
>> > @jbaruch <https://twitter.com/jbaruch/>
>> > http://linkd.in/jbaruch
>> >
>> > On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée <
>> nicolas.lalevee@hibnet.org>
>> > wrote:
>> >
>> >> It was so obvious that this release candidate should be canceled that I
>> >> forgot to officially set it. Here it is.
>> >>
>> >> I see that the infra ticket is resolved. Jean-Louis spotted some issues
>> >> with it though. But I guess we will retry very soon.
>> >>
>> >> Nicolas
>> >>
>> >>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée <ni...@hibnet.org>
>> a
>> >> écrit :
>> >>>
>> >>> I have built a release candidate for Ivy 2.4.0
>> >>>
>> >>> The git tag of this release is:
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
>> >>>
>> >>> The artifacts has been published to:
>> >> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
>> >>>
>> >>> Do you vote for the release of these binaries?
>> >>>
>> >>> [ ] Yes
>> >>> [ ] No
>> >>>
>> >>> Regards,
>> >>> Nicolas
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> >>> For additional commands, e-mail: dev-help@ant.apache.org
>> >>>
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> >> For additional commands, e-mail: dev-help@ant.apache.org
>> >>
>> >>
>>
>>
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by JBaruch <jb...@jfrog.com>.
Perfect, we are on it.
On 3 Dec 2014 12:29, "Nicolas Lalevée" <ni...@hibnet.org> wrote:
> I would still would like some doc.
>
> The doc in the code source is still broken and it make it difficult to
> know how it is rendered.
> In the mean time time, you could write a page. I will then ensure myself
> that is proper included in the doc and rendered when the build will be
> fixed. You can take this file as an exemple:
>
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
> <
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD
> >
>
> Nicolas
>
> > Le 2 déc. 2014 à 22:56, JBaruch <jb...@jfrog.com> a écrit :
> >
> > Can we use this opportunity to sneak IVY-1474 in?
> >
> > Baruch.
> >
> > --
> > JFrog Developer Advocate
> > www.jfrog.com
> > +972544954353
> > @jbaruch <https://twitter.com/jbaruch/>
> > http://linkd.in/jbaruch
> >
> > On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée <
> nicolas.lalevee@hibnet.org>
> > wrote:
> >
> >> It was so obvious that this release candidate should be canceled that I
> >> forgot to officially set it. Here it is.
> >>
> >> I see that the infra ticket is resolved. Jean-Louis spotted some issues
> >> with it though. But I guess we will retry very soon.
> >>
> >> Nicolas
> >>
> >>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée <ni...@hibnet.org> a
> >> écrit :
> >>>
> >>> I have built a release candidate for Ivy 2.4.0
> >>>
> >>> The git tag of this release is:
> >>
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
> >>>
> >>> The artifacts has been published to:
> >> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
> >>>
> >>> Do you vote for the release of these binaries?
> >>>
> >>> [ ] Yes
> >>> [ ] No
> >>>
> >>> Regards,
> >>> Nicolas
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >>> For additional commands, e-mail: dev-help@ant.apache.org
> >>>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> >> For additional commands, e-mail: dev-help@ant.apache.org
> >>
> >>
>
>
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by Nicolas Lalevée <ni...@hibnet.org>.
I would still would like some doc.
The doc in the code source is still broken and it make it difficult to know how it is rendered.
In the mean time time, you could write a page. I will then ensure myself that is proper included in the doc and rendered when the build will be fixed. You can take this file as an exemple:
https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD <https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=blob;f=doc/resolver/ibiblio.html;h=80057c4816a3cabc79bee70c961c57adcee29d11;hb=HEAD>
Nicolas
> Le 2 déc. 2014 à 22:56, JBaruch <jb...@jfrog.com> a écrit :
>
> Can we use this opportunity to sneak IVY-1474 in?
>
> Baruch.
>
> --
> JFrog Developer Advocate
> www.jfrog.com
> +972544954353
> @jbaruch <https://twitter.com/jbaruch/>
> http://linkd.in/jbaruch
>
> On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée <ni...@hibnet.org>
> wrote:
>
>> It was so obvious that this release candidate should be canceled that I
>> forgot to officially set it. Here it is.
>>
>> I see that the infra ticket is resolved. Jean-Louis spotted some issues
>> with it though. But I guess we will retry very soon.
>>
>> Nicolas
>>
>>> Le 9 nov. 2014 à 17:56, Nicolas Lalevée <ni...@hibnet.org> a
>> écrit :
>>>
>>> I have built a release candidate for Ivy 2.4.0
>>>
>>> The git tag of this release is:
>> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
>>>
>>> The artifacts has been published to:
>> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
>>>
>>> Do you vote for the release of these binaries?
>>>
>>> [ ] Yes
>>> [ ] No
>>>
>>> Regards,
>>> Nicolas
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>> For additional commands, e-mail: dev-help@ant.apache.org
>>
>>
Re: [CANCELED][VOTE] Release Ivy 2.4.0
Posted by JBaruch <jb...@jfrog.com>.
Can we use this opportunity to sneak IVY-1474 in?
Baruch.
--
JFrog Developer Advocate
www.jfrog.com
+972544954353
@jbaruch <https://twitter.com/jbaruch/>
http://linkd.in/jbaruch
On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée <ni...@hibnet.org>
wrote:
> It was so obvious that this release candidate should be canceled that I
> forgot to officially set it. Here it is.
>
> I see that the infra ticket is resolved. Jean-Louis spotted some issues
> with it though. But I guess we will retry very soon.
>
> Nicolas
>
> > Le 9 nov. 2014 à 17:56, Nicolas Lalevée <ni...@hibnet.org> a
> écrit :
> >
> > I have built a release candidate for Ivy 2.4.0
> >
> > The git tag of this release is:
> https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
> >
> > The artifacts has been published to:
> https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
> >
> > Do you vote for the release of these binaries?
> >
> > [ ] Yes
> > [ ] No
> >
> > Regards,
> > Nicolas
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> > For additional commands, e-mail: dev-help@ant.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
[CANCELED][VOTE] Release Ivy 2.4.0
Posted by Nicolas Lalevée <ni...@hibnet.org>.
It was so obvious that this release candidate should be canceled that I forgot to officially set it. Here it is.
I see that the infra ticket is resolved. Jean-Louis spotted some issues with it though. But I guess we will retry very soon.
Nicolas
> Le 9 nov. 2014 à 17:56, Nicolas Lalevée <ni...@hibnet.org> a écrit :
>
> I have built a release candidate for Ivy 2.4.0
>
> The git tag of this release is: https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2
>
> The artifacts has been published to: https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093
>
> Do you vote for the release of these binaries?
>
> [ ] Yes
> [ ] No
>
> Regards,
> Nicolas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org