L.S., All the JBI components have been moved back into a a single svn tree location in http://svn.apache.org/repos/asf/servicemix/components/trunk/. Please give it a go and let me know if there's any issues with this new components build. I'll start moving the tags together into a single tags directory tomorrow morning and after that we can remove the old (per component) svn repository structure to end up with a default trunk/branches/tags layout again for the JBI components.
Regards, Gert Vanthienen ------------------------ FuseSource Web: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ On Wed, Dec 8, 2010 at 4:22 PM, Jean-Baptiste Onofré <[email protected]> wrote: > Awesome, thanks a lot Gert. > > Regards > JB > > On 12/08/2010 03:08 PM, Gert Vanthienen wrote: >> >> L.S., >> >> I'm going to start the migration process. It's probably best to >> refrain from committing to the components codebase until the initial >> svn move operation has been done to avoid losing commits in the >> process. >> >> Regards, >> >> Gert Vanthienen >> ------------------------ >> FuseSource >> Web: http://fusesource.com >> Blog: http://gertvanthienen.blogspot.com/ >> >> >> >> On Tue, Dec 7, 2010 at 11:10 AM, Jean-Baptiste Onofré<[email protected]> >> wrote: >>> >>> +1 to gather components in a single svn. >>> >>> On 12/07/2010 10:56 AM, Freeman Fang wrote: >>>> >>>> On 2010-12-6, at 下午9:01, Gert Vanthienen wrote: >>>> >>>>> L.S., >>>>> >>>>> Now that the jbi-maven-plugin 4.4 has been released, I'd like to >>>>> prepare for a components 2010.02 release later this week (e.g. on >>>>> Thursday or Friday). We'll have to upgrade the builds to use the >>>>> latest release versions of specs/utils/jbi-maven-plugin and I'm also >>>>> working on adding more javadocs to the endpoint setters to get more >>>>> content in the auto-generated xsd/wiki documentation (any help welcome >>>>> btw ;)). >>>>> >>>>> We now have separate trunk/branches/tags folders for every component, >>>>> but we never really leveraged this structure (i.e. we never did many >>>>> single component releases) in the past. Now that the future of >>>>> ServiceMix will focus less on JBI, I think the overhead of the >>>>> separate trunk/branches probably outweighs the benefits. >>>>> >>>>> I was originally planning to propose to move the JBI components back >>>>> into a single svn tree location after this release, but we might as >>>>> well bite the bullet and get that done for this release as well (it >>>>> also simplifies the release process if it's just a single build to >>>>> run). Jean-Baptiste has already done a lot of work in cleaning up the >>>>> component POMs and aligning dependencies through a common dependency >>>>> management section in components-pom, so I should be able to get the >>>>> actual svn moves done over the next few days just in time for the >>>>> release. Any objections/thoughts? >>>> >>>> +1 for moving the JBI components back into a single svn tree before this >>>> release. >>>> >>>> Thanks >>>> Freeman >>>>> >>>>> And finally, there's a few more new bundles waiting to get released as >>>>> well (see current list in >>>>> http://svn.apache.org/repos/asf/servicemix/smx4/bundles/trunk/pom.xml). >>>>> While I'm in 'release mode' anyway, I figured I could do those as >>>>> well. Could you make sure that the bundles you want to get released >>>>> are listed in the pom.xml file? >>>>> >>>>> Regards, >>>>> >>>>> Gert Vanthienen >>>>> ------------------------ >>>>> FuseSource >>>>> Web: http://fusesource.com >>>>> Blog: http://gertvanthienen.blogspot.com/ >>>> >>>> >>> >
