commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <Joerg.Schai...@Elsag-Solutions.com>
Subject RE: [sandbox] Using commons-skin for all components
Date Tue, 09 Jan 2007 15:47:11 GMT
Rahul Akolkar wrote on Tuesday, January 09, 2007 4:23 PM:

> On 1/9/07, Jörg Schaible <Joerg.Schaible@elsag-solutions.com> wrote:
>> Hi Rahul,
>> 
>> Rahul Akolkar wrote on Monday, January 08, 2007 8:47 PM:
>> 
> <snip/>
>>> 
>>> In trunks-sandbox, more specifically:
>>> 
>>> https://svn.apache.org/repos/asf/jakarta/commons/trunks-sandbo
>>> x/pom.xml
>> 
>> IMHO it makes more sense to have an own
> commons-sandbox-parent trunk (like any other sandbox
> component). That way you don't have to checkout the complete
> sandbox and additionally you get the possibility to create a
> release for the POM ... or is that not supposed to happen for
> the sandbox parent POM ?
>> 
> <snap/>
> 
> Its possible to just check out the top level svn folder, if you want
> (svn -N co). I don't mind if its moved around. I favor no releases
> (might help ensure sandbox deploys don't accidentally end up in a
> sync'ed/non-snap repo). 

I know, but you cannot release it from there ...

- Jörg

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


Mime
View raw message