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 2012/03/02 14:00:36 UTC

Re: Mandatory svnpubsub migration by Jan 2013

issue created:
https://issues.apache.org/jira/browse/INFRA-4509

Nicolas

Le 23 févr. 2012 à 17:29, Nicolas Lalevée a écrit :

> 
> Le 21 févr. 2012 à 16:52, Stefan Bodewig a écrit :
> 
>> On 2012-02-20, Nicolas Lalevée wrote:
>> 
>>> We then just need to create an INFRA ticket asking for the
>>> transition. I guess we want the svn notifications sent to
>>> notifications@ant.apache.org. Once the infra has created our space, we
>>> would just need to check in the current content of our dist.
>> 
>> Currently KEYS is a (sym)link to a checked out copy from somewhere else.
>> Once we have svnpubsub in place I'd suggest we make the dist repository
>> the canonical place for storing PGP keys.
> 
> +1
> 
>> 
>>> A side effect will probably that ivy/updatesite/trunk/dist will
>>> disappeared from our svn. Maybe it would help in the management of the
>>> new Eclipse update site [3] [4].
>> 
>> Is this something that has to be resolved before the transition?
> 
> No it doesn't. It is quite independant. And finally I don't think having it in svn will help much technically. But for this new Eclipse update site, I'll need to write some doc about it; I prefer write it once with already reference to the dist-svn. Just me being a little lazy :)
> 
> 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: Mandatory svnpubsub migration by Jan 2013

Posted by Stefan Bodewig <bo...@apache.org>.
On 2012-03-13, Nicolas Lalevée wrote:

> Our ant dist has been migrated.

Thank you

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Mandatory svnpubsub migration by Jan 2013

Posted by Nicolas Lalevée <ni...@hibnet.org>.
Our ant dist has been migrated.

Nicolas

Le 2 mars 2012 à 14:14, Nicolas Lalevée a écrit :

> By the way, I have noticed that some symlinks still exist:
> antlibs/antunit/apache-ant-antunit-current-* -> binaries/* et  -> source/*
> antlibs/dotnet/apache-ant-dotnet-current-* -> binaries/* et  -> source/*
> antlibs/antunit/binaries/README.html -> ../README.html
> antlibs/antunit/source/README.html -> ../README.html
> 
> When I'll push our artifacts to the new svn, by default I won't create copies of symlinked files. But if somebody thinks copies are deserved, he could do svn cp after the migration.
> 
> Nicolas
> 
> Le 2 mars 2012 à 14:00, Nicolas Lalevée a écrit :
> 
>> issue created:
>> https://issues.apache.org/jira/browse/INFRA-4509
>> 
>> Nicolas
>> 
>> Le 23 févr. 2012 à 17:29, Nicolas Lalevée a écrit :
>> 
>>> 
>>> Le 21 févr. 2012 à 16:52, Stefan Bodewig a écrit :
>>> 
>>>> On 2012-02-20, Nicolas Lalevée wrote:
>>>> 
>>>>> We then just need to create an INFRA ticket asking for the
>>>>> transition. I guess we want the svn notifications sent to
>>>>> notifications@ant.apache.org. Once the infra has created our space, we
>>>>> would just need to check in the current content of our dist.
>>>> 
>>>> Currently KEYS is a (sym)link to a checked out copy from somewhere else.
>>>> Once we have svnpubsub in place I'd suggest we make the dist repository
>>>> the canonical place for storing PGP keys.
>>> 
>>> +1
>>> 
>>>> 
>>>>> A side effect will probably that ivy/updatesite/trunk/dist will
>>>>> disappeared from our svn. Maybe it would help in the management of the
>>>>> new Eclipse update site [3] [4].
>>>> 
>>>> Is this something that has to be resolved before the transition?
>>> 
>>> No it doesn't. It is quite independant. And finally I don't think having it in svn will help much technically. But for this new Eclipse update site, I'll need to write some doc about it; I prefer write it once with already reference to the dist-svn. Just me being a little lazy :)
>>> 
>>> 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
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Mandatory svnpubsub migration by Jan 2013

Posted by Nicolas Lalevée <ni...@hibnet.org>.
By the way, I have noticed that some symlinks still exist:
antlibs/antunit/apache-ant-antunit-current-* -> binaries/* et  -> source/*
antlibs/dotnet/apache-ant-dotnet-current-* -> binaries/* et  -> source/*
antlibs/antunit/binaries/README.html -> ../README.html
antlibs/antunit/source/README.html -> ../README.html

When I'll push our artifacts to the new svn, by default I won't create copies of symlinked files. But if somebody thinks copies are deserved, he could do svn cp after the migration.

Nicolas

Le 2 mars 2012 à 14:00, Nicolas Lalevée a écrit :

> issue created:
> https://issues.apache.org/jira/browse/INFRA-4509
> 
> Nicolas
> 
> Le 23 févr. 2012 à 17:29, Nicolas Lalevée a écrit :
> 
>> 
>> Le 21 févr. 2012 à 16:52, Stefan Bodewig a écrit :
>> 
>>> On 2012-02-20, Nicolas Lalevée wrote:
>>> 
>>>> We then just need to create an INFRA ticket asking for the
>>>> transition. I guess we want the svn notifications sent to
>>>> notifications@ant.apache.org. Once the infra has created our space, we
>>>> would just need to check in the current content of our dist.
>>> 
>>> Currently KEYS is a (sym)link to a checked out copy from somewhere else.
>>> Once we have svnpubsub in place I'd suggest we make the dist repository
>>> the canonical place for storing PGP keys.
>> 
>> +1
>> 
>>> 
>>>> A side effect will probably that ivy/updatesite/trunk/dist will
>>>> disappeared from our svn. Maybe it would help in the management of the
>>>> new Eclipse update site [3] [4].
>>> 
>>> Is this something that has to be resolved before the transition?
>> 
>> No it doesn't. It is quite independant. And finally I don't think having it in svn will help much technically. But for this new Eclipse update site, I'll need to write some doc about it; I prefer write it once with already reference to the dist-svn. Just me being a little lazy :)
>> 
>> 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