+1 for the components release.
If you need some help, don't hesitate to ping me.
Thanks Gert
Regards JB
On 12/17/2010 11:46 AM, Gert Vanthienen wrote:
L.S.,
It has taken a few more days to some extra javadocs included in the
endpoints and sort out the correct version of Camel to use, but
components trunk now looks ready for release. I'll start the release
build right after lunch...
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Fri, Dec 10, 2010 at 5:24 PM, Gert Vanthienen
<[email protected]> wrote:
Jean-Baptiste,
Sounds good - I'll ping you on Monday to coordinate about the best
time to start the release.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Fri, Dec 10, 2010 at 5:13 PM, Jean-Baptiste Onofré<[email protected]> wrote:
Gert,
I would like to fix some issues on components before releasing. I do my best
this week end to fix the max.
Regards
JB
-----Original Message-----
From: Gert Vanthienen<[email protected]>
Date: Fri, 10 Dec 2010 17:02:34
To:<[email protected]>
Reply-To: [email protected]
Subject: Re: Getting ready for components 2010.02 release
L.S.,
Previous release tags have been copied into the
http://svn.apache.org/repos/asf/servicemix/components/tags/ directory,
the new location has been documented in
https://cwiki.apache.org/confluence/display/SM/Building+JBI+Components
and the Hudson CI build has been updated to use the new trunk
location. I'll await a first run of the CI build and once everything
looks OK, I'll remove the old locations from the svn repo and prepare
for a components' release on Monday.
Regards,
Gert Vanthienen
------------------------
FuseSource
Web: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On Fri, Dec 10, 2010 at 7:56 AM, Jean-Baptiste Onofré<[email protected]> wrote:
Checkout and build in progress on my side.
Regards
JB
On 12/09/2010 11:32 PM, Gert Vanthienen wrote:
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/
