Well it's not really duplication.. It's using svn externals.  Please
feel free to doco it up.  I guess some folks might be thrown for a
loop if they have not worked with svn externals before.

On Wed, Jun 18, 2008 at 9:37 AM, Bruce Snyder <[EMAIL PROTECTED]> wrote:
> On Wed, Jun 18, 2008 at 6:25 AM, Hiram Chirino <[EMAIL PROTECTED]> wrote:
>> Hi folks,
>>
>> At some point we just need to bite the bullet and branch the
>> components to their own release structures.  To avoid folk's commits
>> getting lost in the shuffle, I think we should just 'svn mv' the
>> components from the smx3 trunk to the new component's trunk directory.
>>  For all of you who have not been following the discussions, that
>> would be located under:
>>
>> https://svn.apache.org/repos/asf/servicemix/components/
>>
>> I plan to start doing this soon.  So if a commit fails, chances are
>> because the directory has moved.  Save a diff and reapply to the
>> component's new location.  Sorry for this transitory pain, I'll try to
>> make it as quick as possible.
>
> I agree that we need to get the move completed, but we also need to
> provide some clear documentation for folks about the move and how to
> work on the components in the new location. For example, I think that
> the seeming duplication caused by use of svn:externals is going to be
> confusing to people. We need to explain why there appears to be
> duplication and how to work with it.
>
> Would you agree?
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)[EMAIL 
> PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
>
> Blog: http://bruceblog.org/
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

Reply via email to