camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: [DISCUSS] - Apache Camel 2.10 release
Date Tue, 22 May 2012 13:18:32 GMT
Hi

Just a heads up. I have fixed the hdfs and zookeeper on windows java 7.
I could not reproduce the failure on camel-sql.

And currently testing the osgi ones, they take a long time as usual.

Hope Willem get those tests upgraded to Pax-Exam 2.x soon.

On Tue, May 22, 2012 at 11:34 AM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
> Hi
>
> I am currently working on polishing and fixing the tests so they work
> on Java 7 on my Windows box.
> Its looking really good, so far there is a few errors in the
> - camel-hdfs
> - camel-sql
> - camel-zookeeper
> - camel-itest-osgi
>
> I will work my way to see if these tests can be fixed along the way.
>
>
> On Wed, May 9, 2012 at 1:10 PM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>> Just a heads-up that Camel 2.10 now requires Maven 3.0.2 or better to
>> build from source.
>> We put out note in the 2.9 release notes that we would drop Maven 2.x support.
>>
>> Also I upgrade the maven bundle plugin to 2.3.7, so keep an eye out if
>> that plugin makes some mistakes.
>> It has done that in the past.
>>
>>
>>
>> On Wed, May 9, 2012 at 11:08 AM, Christian Müller
>> <christian.mueller@gmail.com> wrote:
>>> Thanks Dan, thanks Claus,
>>>
>>> great work. I got a compile failure in camel-quickfix. Will have a look on
>>> it later...
>>>
>>> Best,
>>> Christian
>>>
>>> On Wed, May 9, 2012 at 10:53 AM, Claus Ibsen <claus.ibsen@gmail.com> wrote:
>>>
>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dkulp@apache.org> wrote:
>>>> >
>>>> > The latest Jenkins build definitely looks a TON better:
>>>> >
>>>> >
>>>> > https://builds.apache.org/job/Camel.trunk.fulltest.java7/82/
>>>> >
>>>>
>>>> Great work. Nice to see it down to a manageable size.
>>>>
>>>> At first glance many of those test failures is due to port number in use.
>>>> A bit odd as some of these components ought to use the free port finder.
>>>>
>>>>
>>>> > :-)
>>>> >
>>>> > Most of the test failures are with SSL related tests.  They pass on
my
>>>> > machine fine so it's a bit concerning to me.  However, I always have
the
>>>> > unlimited strength crypto things installed due to my work on the
>>>> ws-security
>>>> > things and wss4j and such.  I'm not sure it that may be part of it
or not
>>>> > yet.   I'd have to setup a separate JDK setup to test that.  Can someone
>>>> > with a non-JCE JDK7 setup check some of those tests and see if that
may
>>>> be
>>>> > the issue?
>>>> >
>>>>
>>>> If I find some cycles I will try installing a vanilla JDK7 on my xp
>>>> box (this wont have the unlimted strengh crypto)
>>>> And give it a test run.
>>>>
>>>>
>>>>
>>>> >
>>>> >
>>>> > Dan
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > On Tuesday, May 08, 2012 01:04:28 PM Daniel Kulp wrote:
>>>> >> On Tuesday, May 08, 2012 05:00:50 PM Christian Müller wrote:
>>>> >> > For private reasons I cannot work on Camel 2.10.0 as I want.
I will do
>>>> >> > my
>>>> >> > best to resolve my two outstanding issues in the next week.
If this is
>>>> >> > not possible, it's no problem to postpone it to Camel 2.10.1.
>>>> >> >
>>>> >> > The only one issue which is not resolved at the moment and
I worked on
>>>> >> > (it's not assigned to anybody at present) and which should
be resolved
>>>> >> > in
>>>> >> > Camel 2.10.0 in my opinion is:
>>>> >> > CAMEL-4955: Camel should run in a Java 7 environment
>>>> >> > May be we have a voluntary which could support me? The Jenkins
build
>>>> >> > results are here [1].
>>>> >>
>>>> >> I've pretty much picked this up for you.   I'm at a point now where
all
>>>> of
>>>> >> Camel *BUILDS* other that quickfix.   All of the component/* unit
tests
>>>> >> now pass as well (although some randomly fail, but that's no different
>>>> >> than with J6).   I'm getting a bunch of failures in the itests.
  That's
>>>> >> next to look at.
>>>> >>
>>>> >> Dan
>>>> >>
>>>> >> > If I have a few hours left, I will also have a look on some
>>>> >> > other/smaller
>>>> >> > enhancements which could go into Camel 2.10.0.
>>>> >> >
>>>> >> > [1]
>>>> >> >
>>>> https://builds.apache.org/view/A-F/view/Camel/job/Camel.trunk.fulltest.j
>>>> >> > av a7/
>>>> >> >
>>>> >> > Best,
>>>> >> > Christian
>>>> >> >
>>>> >> > On Mon, May 7, 2012 at 4:27 PM, Claus Ibsen <claus.ibsen@gmail.com>
>>>> > wrote:
>>>> >> > > Hi
>>>> >> > >
>>>> >> > > I think its time we start close down on a Camel 2.10 release.
The
>>>> >> > > 2.9.0 release was on January 1sy 2012, so its been 4.5
months since
>>>> >> > > that release. Yes in between there has been 2 patch releases,
eg
>>>> >> > > 2.9.1, and 2.9.2 etc.
>>>> >> > >
>>>> >> > > There is some new components added in Camel 2.10, and
most of them
>>>> now
>>>> >> > > have adequate documentation.
>>>> >> > > But I think a few is missing. The camel-leveldb is essentially
a
>>>> copy
>>>> >> > > of the camel-hawtdb component, so the documentation is
fairly easy
>>>> as
>>>> >> > > it would be a copy, and then some adjustments. The camel-leveldb
is
>>>> >> > > not yet OSGi compliant. We may need to push that for Camel
2.11 or a
>>>> >> > > patch release of 2.10.
>>>> >> > >
>>>> >> > > When the AMQ 5.6.0 release is out, we can bump that in
the camel-jms
>>>> >> > > testing, to ensure we test against that release.
>>>> >> > >
>>>> >> > > In the JIRA tracker there is 70+ unresolved tickets scheduled
for
>>>> 2.10
>>>> >> > >
>>>> >> > >
>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&j
>>>> >> > > ql
>>>> >> > >
>>>> Query=project+%3D+CAMEL+AND+fixVersion+%3D+%222.10.0%22+AND+resolution
>>>> >> > > +%
>>>> >> > > 3D+Unresolved
>>>> >> > >
>>>> >> > > We may be able to push some for 2.10.1, or 2.11.
>>>> >> > > I will create a 2.10.1 version so people can move tickets
to this
>>>> >> > > version.
>>>> >> > >
>>>> >> > >
>>>> >> > > --
>>>> >> > > Claus Ibsen
>>>> >> > > -----------------
>>>> >> > > CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>>>> >> > > FuseSource
>>>> >> > > Email: cibsen@fusesource.com
>>>> >> > > Web: http://fusesource.com
>>>> >> > > Twitter: davsclaus, fusenews
>>>> >> > > Blog: http://davsclaus.blogspot.com/
>>>> >> > > Author of Camel in Action: http://www.manning.com/ibsen/
>>>> > --
>>>> > Daniel Kulp
>>>> > dkulp@apache.org - http://dankulp.com/blog
>>>> > Talend Community Coder - http://coders.talend.com
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>
>
>
> --
> Claus Ibsen
> -----------------
> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/



-- 
Claus Ibsen
-----------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message