I tried building with camel 1.6 and it builds fine. That is required only 
because of camel-web's dependency on jersey.
I didn't try if the built artifacts will work with java 5. I'll try that today.

Hadrian


On Sep 7, 2010, at 5:02 AM, Claus Ibsen wrote:

> Hi
> 
> Okay 2.5 looks really good now. The main features have been
> implemented and the important bugs fixed as well.
> The jasypt stuff is also in place now, so we are almost ready to go.
> 
> James Strachan promised to take a peek at the trimmed camel-web
> component to ensure that he got the pieces he want and that it works
> as expected.
> I did some tests yesterday and it works fine as far as I can see. We
> also removed some not needed JS libraries.
> 
> We may be able to remove dojo JS as well (it has a lot of JS files)
> and replace it with something lighter. All we need is some small
> pieces to syntax highlight the XML when viewing and editing routes.
> 
> Also the builds in TC looks great and are all green. So we should
> almost be ready to cut a release.
> 
> Hadrian it requires Maven 2.2.1 or better to build (please use 2.2.1
> as its what used by build servers).
> To build and include the camel-web you need to build with JDK 1.6. Did
> you try this out?
> There is a profile you need to set on the mvn cmd line to enable it.
> 
> See the pom.xml in components for details.
> 
> 
> 
> 
> On Fri, Aug 27, 2010 at 5:10 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote:
>> Absolutely.
>> 
>> It also looks to me that we have more contributors than in the past (many 
>> thanks to our community!) and I wonder if it wouldn't be a good thing to 
>> release more often.
>> We did some work on speeding up the builds (and we won't stop here :) ), and 
>> I am looking into even faster parallel builds, so the release time is 
>> becoming less of an issue.
>> 
>> In the past year and a half or so we had predictable once a quarter 
>> releases. The exception will be this quarter it seems where we'll have two 
>> releases.
>> Camel 2.x doesn't have minor releases (the 3rd digit in the version) and I 
>> would think having 2 releases per quarter (every 6 weeks), one major one 
>> minor, would probably be a good thing.
>> I will start a DISCUSS thread next week, so probably best is to just think 
>> about this (for now) and not hijack this thread.
>> 
>> The 2.5.0 release would also be just in time for the next board report due 
>> in Sep.
>> 
>> Cheers,
>> Hadrian
>> 
>> 
>> On Aug 27, 2010, at 8:24 AM, Claus Ibsen wrote:
>> 
>>> Hi
>>> 
>>> Its just 6-7 weeks ago we released Camel 2.4, and we already got
>>> approx 150 tickets resolved on the road for Camel 2.5.
>>> 
>>> Camel 2.5 doesn't have a lot of new features, but it does have many
>>> great improvements and bug fixes. So it becomes a great and stable
>>> Camel release.
>>> I have therefore started moving tickets with bigger new features to
>>> Camel 2.6 or even 3.0.
>>> 
>>> I suggest that we release Camel 2.5 next month. For example in about 2
>>> weeks time if that suites our release manager, Hadrian :)
>>> 
>>> We are currently having a couple of dependencies to OSGi bundles being
>>> released at SMX.
>>> The vote is currently in progress, and they should be out in central
>>> maven repo next week.
>>> 
>>> What remains to be done is to trim the size of camel-web to remove the
>>> unneeded stuff which has crept into it. See another mail on dev about
>>> this.
>>> 
>>> If you got any must have features, bug fixes, improvements, then its
>>> time to raise your voice.
>>> 
>>> 
>>> You can see the current in progress release notes
>>> http://camel.apache.org/camel-250-release.html
>>> 
>>> --
>>> Claus Ibsen
>>> Apache Camel Committer
>>> 
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>> Open Source Integration: http://fusesource.com
>>> Blog: http://davsclaus.blogspot.com/
>>> Twitter: http://twitter.com/davsclaus
>> 
>> 
> 
> 
> 
> -- 
> Claus Ibsen
> Apache Camel Committer
> 
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus

Reply via email to