On Thu, Apr 8, 2010 at 12:13 PM, Antonio Petrelli
<[email protected]> wrote:
> 2010/4/8 Nathan Bubna <[email protected]>:
>>> I'd vote for a "src/sandbox" directory without any dedicated task, each
>>> tool in its own subdirectory with a small README file. Interested users
>>> can copy the source files towards the main source tree and issue "ant
>>> jar[.generic|.view|.struts]". The only thing to be done in the build
>>> file is to include src/sandbox in the released sources. But not in the
>>> released binary.
>>>
>>> If you use a different package name, early adopters will have to upgrade
>>> their parameters once the tools go into production.
>>
>> That is still more work in total for both me and any would be adopters
>> and will reduce their accesibility and thus may inhibit development of
>> them by anyone else.  But whatever, these are not all that important
>> of tools, and my main desire is to just put them out there.
>
> Sorry to jump in as an intruder, but if Maven was used, isolating non
> stable or experimental code is very easy.
> Long time ago I volunteered to make a Maven reorganization in a
> sandbox directory, if it was available. This offer, obviously, is
> still valid :-)

and still sounds awesome, though we don't split svn access up by
directory, so i'm not sure how to provide you access to a sandbox
directory without just making you a committer.  do you know how/if
that can be done?  i suppose we could just ask infra@ about it, but
they're rather busy right now with some...er..problems.

> Antonio
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to