On second thought.. I'm gonna try to make this move more iterative.. I started working on switching the smx3 trunk to use the new split out modules and realized that updating that is going to entail some serious in and of itself. So to avoid having smx 3 trunk be broken for a while, I've copied my inprogress work to
https://svn.apache.org/repos/asf/servicemix/sandbox/chirino/smx3-trunk-component-splitout Once that's working with the split out components, merge it back to smx3 trunk. Please feel free to jump in on that branch help if you can.. Thx. On Wed, Jun 18, 2008 at 8: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. > > -- > Regards, > Hiram > > Blog: http://hiramchirino.com > > Open Source SOA > http://open.iona.com > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
