On Mon, Sep 13, 2010 at 7:00 PM, Jean-Sebastien Delfino
<[email protected]> wrote:
> ant elder wrote:
>>
>> On Wed, Sep 8, 2010 at 12:52 AM,  <[email protected]> wrote:
>>>
>>> Author: jsdelfino
>>> Date: Tue Sep  7 23:52:54 2010
>>> New Revision: 993560
>>>
>>> URL: http://svn.apache.org/viewvc?rev=993560&view=rev
>>> Log:
>>> Sandbox to experiment with deployment and management commands.
>>>
>>> Added:
>>>   tuscany/sandbox/sebastien/java/shell/   (props changed)
>>>     - copied from r993559, tuscany/sca-java-2.x/trunk/
>>>
>>
>> What are the reasons this couldn't be done in trunk?
>>
>>   ...ant
>
> This sandbox is just to experiment. This experiment may lead to changes
> applicable to trunk (like some other small changes I've made in trunk
> recently) or lead to nothing at all. I don't know yet, as I'm experimenting
> :)
>
> So far I've made one small change to the shell sample in this sandbox [1], I
> have been using it with that change for a few days, and I'm getting
> comfortable with it so I may decide to make the same change in trunk, but
> I'm not sure yet.
>
> Using a sandbox also allows me to work and make small changes off a fixed
> revision instead of having to catch up and rebase on the moving trunk all
> the time, which I must admit is overwhelming when you only work on it part
> time a few hours a week.
>
> [1]
> http://mail-archives.apache.org/mod_mbox/tuscany-commits/201009.mbox/%[email protected]%3e
> --
> Jean-Sebastien
>

You don't really need a private sandbox fork of the entire trunk to
experiment with whether or not the shells contribution uri could be
optional or not do you? Just make the change in trunk and if it
doesn't work out it can be reverted. We've already been discussing
what the shell commands could be on the ML and whats currently been
said does have the contribution uri as optional.

   ...ant

Reply via email to