You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2012/05/07 16:27:47 UTC
[DISCUSS] - Apache Camel 2.10 release
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&jqlQuery=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/
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I'll be doing release dry runs today.
Hadrian
On 05/07/2012 10:27 AM, Claus Ibsen 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&jqlQuery=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.
>
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Schneider <ch...@die-schneider.net>.
Already done.
https://issues.apache.org/jira/browse/CAMEL-5254
It is just the package import. I will also backport to 2.9.x.
Dan came up with another issue that we will have with karaf 3. As Aries
will be upgraded to 1.0 we will also have to check these imports. Not
sure if this will make it to 2.10.0 though.
Christian
Am 08.05.2012 18:58, schrieb Jean-Baptiste Onofré:
> Hi Christian,
>
> I don't think it's blocker for Camel 2.10.
>
> On my side, I will work on the RMI component improvements (not blocker
> for 2.10 either).
>
> Regards
> JB
>
> On 05/08/2012 06:23 PM, Christian Schneider wrote:
>> Hi Claus,
>>
>> I am currently working on making the camel commands compatible with
>> karaf 3. Would be great if we could get this into 2.10
>> https://issues.apache.org/jira/browse/KARAF-1451
>>
>> In karaf it is the issue above. I will also create an issue in camel for
>> it. The change should be fairly small.
>>
>> Christian
>>
>> Am 07.05.2012 16:27, schrieb Claus Ibsen:
>>> 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&jqlQuery=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.
>>>
>>>
>>
>>
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Christian,
I don't think it's blocker for Camel 2.10.
On my side, I will work on the RMI component improvements (not blocker
for 2.10 either).
Regards
JB
On 05/08/2012 06:23 PM, Christian Schneider wrote:
> Hi Claus,
>
> I am currently working on making the camel commands compatible with
> karaf 3. Would be great if we could get this into 2.10
> https://issues.apache.org/jira/browse/KARAF-1451
>
> In karaf it is the issue above. I will also create an issue in camel for
> it. The change should be fairly small.
>
> Christian
>
> Am 07.05.2012 16:27, schrieb Claus Ibsen:
>> 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&jqlQuery=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.
>>
>>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Claus,
I am currently working on making the camel commands compatible with
karaf 3. Would be great if we could get this into 2.10
https://issues.apache.org/jira/browse/KARAF-1451
In karaf it is the issue above. I will also create an issue in camel for
it. The change should be fairly small.
Christian
Am 07.05.2012 16:27, schrieb Claus Ibsen:
> 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&jqlQuery=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.
>
>
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Daniel Kulp <dk...@apache.org>.
On Wednesday, June 06, 2012 05:14:01 PM Babak Vahdat wrote:
> Hi Christian
>
> according to what I've read many times by this thread I assumed we do
> always skip running the OSGi tests on CI-Servers so why I did already
> check-in the update for QuickFIX/J but apparently I did misunderstand
> something here.
>
> I'm also puzzled about the last JDK7 build:
>
> https://builds.apache.org/job/Camel.trunk.fulltest.java7/127/
>
> Although I did enable the camel-quickfix module inside POM:
>
> http://svn.apache.org/viewvc/camel/trunk/components/pom.xml?view=log&pathr
> ev=1346880
You removed the java6 profile which enabled it on j6. However, you didn't
add it back into the main modules list at the top. Thus, it's not not
enabled at all on any platform.
> It was still skipped through Jenkins! I also don't own the required rights
> on Jenkins, for example for hitting a manual build, etc. Do you know who
> I can ask for that right?
I just added you. If you re-login to Jenkins, it should pick it up.
Dan
> Babak
>
>
> Christian Mueller wrote
>
> > We have to wait for a few SMX bundle releases (at present, we have
> > SNAPSHOT
> > dependencies in our features definitions)...
> >
> > Best,
> > Christian
> >
> > On Wed, Jun 6, 2012 at 3:39 PM, Babak Vahdat <babak.vahdat@>wrote:
> >> Hi
> >>
> >> Upgrade to QuickFIX/J 1.5.2 is already done (CAMEL-5334). As well the
> >> camel-quickfix module is now enabled again on the Jenkins
> >> (Camel.trunk.fulltest.java7).
> >>
> >> I did test both on OS X as well as WIN (JDK 6 & JDK 7). So let's see
> >> how
> >> it
> >> will go through the next build...
> >>
> >> Babak
> >>
> >>
> >> Claus Ibsen-2 wrote
> >>
> >> > On Sat, Jun 2, 2012 at 10:17 PM, Babak Vahdat
> >> >
> >> > <babak.vahdat@> wrote:
> >> >> The Java 7 support is not completely done yet as camel-quickfix is
> >>
> >> still
> >>
> >> >> the
> >> >> last missing piece of the task (currently disabled on the
> >> >> CI-Server).
> >>
> >> I
> >>
> >> >> did
> >> >> play around with upgrading to quickfixj 1.5.2 which first had some
> >> >> compilation error as well as unit-test failures (NPE) which I easily
> >> >> could
> >> >> fix locally. I'm just waiting for the bundle of it:
> >> >>
> >> >> https://issues.apache.org/jira/browse/SMX4-1153
> >> >
> >> > So does quickfix 1.5.2 work with Java 7?
> >> >
> >> > Regardless of what its not a showstopper for the Camel 2.10 release.
> >> > We can add to known issues that camel-quickfix is known to not work
> >> > with Java7 due QuickFix itself.
> >> >
> >> > The release will be built using java 6, and thus the camel-quickfix
> >> > component will be included.
> >> >
> >> >> Babak
> >> >>
> >> >>
> >> >> Claus Ibsen-2 wrote
> >> >>
> >> >>> Hi
> >> >>>
> >> >>> So the Java 7 support is now done.
> >> >>> And when CXF 2.6.1 is out, we should be in a shape for a release.
> >> >>>
> >> >>> I have created a JIRA version 2.11, and moved some tickets from
> >> >>> 2.10
> >>
> >> to
> >>
> >> >>> that.
> >> >>> As we should focus on closing the last bugs, minor improvements
> >> >>> etc.
> >> >>> And keep eye on the CI servers to have a good build.
> >> >>> And test the examples. I think the twitter example is broken.
> >> >>>
> >> >>> Anything in particular you would like in 2.10, that are not yet
> >> >>> done?
> >> >>>
> >> >>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <dan@> wrote:
> >> >>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
> >> >>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I
> >>
> >> will
> >>
> >> >>>>> have
> >> >>>>> more often an eye on Jenkis to see whether we have issues we have
> >>
> >> to
> >>
> >> >>>>> fix.
> >> >>>>> I will support Claus for the outstanding Java 7 issue.
> >> >>>>> If everything run's fine, we should start the release procedure
> >> >>>>> in
> >> >>>>> this
> >> >>>>> or
> >> >>>>> next week. Do we already have release manager for this release?
> >> >>>>
> >> >>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later
> >> >>>> tonight
> >> >>>> or
> >> >>>> tomorrow.
> >> >>>>
> >> >>>>> Afterwards we should roll out Camel 2.8.7., our last official
> >> >>>>> 2.8.
> >> >>>>> release. I could do this, if no one else want do it.
> >> >>>>
> >> >>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm
> >>
> >> also
> >>
> >> >>>> a
> >> >>>> bit uncomfortable saying "last official". 2.8.0 was released
> >> >>>> last
> >> >>>> July
> >> >>>> so
> >> >>>> I would expect about one more before a full year of patches is up.
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Daniel Kulp
> >> >>>> dan@
> >> >>>> http://dankulp.com/blog
> >> >>>
> >> >>> --
> >> >>> Claus Ibsen
> >> >>> -----------------
> >> >>> FuseSource
> >> >>> Email: cibsen@
> >> >>> Web: http://fusesource.com
> >> >>> Twitter: davsclaus, fusenews
> >> >>> Blog: http://davsclaus.com
> >> >>> Author of Camel in Action: http://www.manning.com/ibsen
> >> >>
> >> >> --
> >>
> >> >> View this message in context:
> >> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5
> >> 691194p5713866.html>>
> >> >> Sent from the Camel Development mailing list archive at Nabble.com.
> >> >
> >> > --
> >> > Claus Ibsen
> >> > -----------------
> >> > FuseSource
> >> > Email: cibsen@
> >> > Web: http://fusesource.com
> >> > Twitter: davsclaus, fusenews
> >> > Blog: http://davsclaus.com
> >> > Author of Camel in Action: http://www.manning.com/ibsen
> >>
> >> --
> >> View this message in context:
> >> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5
> >> 691194p5714066.html Sent from the Camel Development mailing list
> >> archive at Nabble.com.
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp569
> 1194p5714097.html Sent from the Camel Development mailing list archive at
> Nabble.com.
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
I don't see anything strange on this as there was no Hokuspokus I did by the
following revision :-)
http://svn.apache.org/viewvc?view=revision&revision=1300914
Through introducing a dedicated <repository> by camel-msv POM we instruct
Maven to pick from here:
[1]
http://svn.apache.org/repos/asf/servicemix/m2-repo/org/iso_relax/verifier/jaxp/validation/isorelax-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom
Instead of here:
[2]
http://repo.maven.apache.org/maven2/org/iso_relax/verifier/jaxp/validation/isorelax-jaxp-bridge/1.0/isorelax-jaxp-bridge-1.0.pom
Now for this to work one should remove any POM which was once already
downloaded through [2] IF ANY. From there on Maven will do always download
through [1] as we have instructed it to do so. Note that removal of the
crappy POM downloaded through [2] should be done ONLY ONCE.
Now back to problem with build 124 you've mentioned: I suspect there are
other Jenkins Builds for some other Apache projects using the SAME m2-cache
on the filesystem causing Maven to poll from [2] as for sure it's not Camel
anymore asking for that old POM. I also had the suspection that maybe
transitively, we could have the same dependency to isorelax-jaxp-bridge
somewhere else through some other Camel modules which makes Maven to poll
from [2] which I did already check. This is however not the case.
See also the yellow notice here:
http://camel.apache.org/building.html
Babak
Claus Ibsen-2 wrote
>
> On Tue, Jun 5, 2012 at 5:36 PM, Claus Ibsen <claus.ibsen@> wrote:
>> Hi
>>
>> The Apache CI server on Camel trunk with java7, had an issue at the end.
>> I think its related to that Maven 3.0.4 issue with that camel-msv
>> component (I think it was that one).
>> So I configured it to use Maven 3.0.3 instead, just to see if it
>> completes then.
>>
>
> Yes the build was now a success
> https://builds.apache.org/job/Camel.trunk.fulltest.java7/125/
>
> The next build failed due some internal Hudson issue
> (I guess it would be nice if Hudson was improved to better detects its
> own failures and display this differently)
> https://builds.apache.org/job/Camel.trunk.fulltest.java7/126/
>
> I wonder if anyone on the Infra team could remove the below directories?
> .m2/repository/org/iso_relax/
> /m2/repository/msv
>
> As strangely having Maven to re-download the artifact fixes that on Maven
> 3.0.4.
> Babak provided this workaround in a post on this mailing listing
>
>
>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714058.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, Jun 5, 2012 at 5:36 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> The Apache CI server on Camel trunk with java7, had an issue at the end.
> I think its related to that Maven 3.0.4 issue with that camel-msv
> component (I think it was that one).
> So I configured it to use Maven 3.0.3 instead, just to see if it completes then.
>
Yes the build was now a success
https://builds.apache.org/job/Camel.trunk.fulltest.java7/125/
The next build failed due some internal Hudson issue
(I guess it would be nice if Hudson was improved to better detects its
own failures and display this differently)
https://builds.apache.org/job/Camel.trunk.fulltest.java7/126/
I wonder if anyone on the Infra team could remove the below directories?
.m2/repository/org/iso_relax/
/m2/repository/msv
As strangely having Maven to re-download the artifact fixes that on Maven 3.0.4.
Babak provided this workaround in a post on this mailing listing
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
The Apache CI server on Camel trunk with java7, had an issue at the end.
I think its related to that Maven 3.0.4 issue with that camel-msv
component (I think it was that one).
So I configured it to use Maven 3.0.3 instead, just to see if it completes then.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi Charles,
Currently the Twitter-Websocket example is broken:
http://camel.apache.org/twitter-websocket-example.html
This has to do with your current work mentioned below (CAMEL-5280), as on my
workspace if I revert camel-websocket component to the Revision 1307636 then
the example would work out-of-the-box again.
There're also bunch of the unit-tests being commented out by
org.apache.camel.component.websocket.WebsocketComponentTest
which through their absence we wouldn't have any clue about the regression.
Would you maybe have sometime to look into this before the 2.10 Release is
already cut?
Babak
Charles Moulliard wrote
>
> Hi Claus,
>
> I have finished the modifications (refactor in fact) for camel-websocket
> to support ws:// and wss:// protocols. So the timing sounds good to me
> to promote soon release 2.10
>
> Nevertheless, I would like to dissuccs the following poitn concerning
> Jetty version. We currently use Jetty 7.5.4. According to some
> discussions that I have had with Jean François Arcand and its blog,
> websocket support in Jetty 7.6.3 and 8.1.3 are stable now which is not
> the case with previous versions
> (http://jfarcand.wordpress.com/category/websocket-2/). So the point is,
> are we ok to migrate to 7.6.3 for apache camel project globally or only
> for websocket component ?
>
> Regards,
>
> Charles
>
> On 24/05/12 11:08, Claus Ibsen wrote:
>> Hi
>>
>> The blueprint issue have been fixed, and backported to 2.9 as well.
>>
>> The Java 7 upgrades seems really good now.
>> I can test all components, examples etc on my windows xp box.
>>
>> Only the osgi have a little issue with pax-exam locking the files, and
>> cannot rename downloaded bundles etc.
>> Thats a problem with pax-exam and not Camel.
>>
>> On the ASF CI servers the java7 tests is also good, they only fail due
>> concurrent testing with the -T option,
>> which triggers a race condition to find a free port number, and
>> causing a "Address already in use" failures.
>>
>> I will look into that later, to improve the camel-test
>> AvailablePortFinder, to use files to lock a given port number,
>> so concurrent JVMs can't compete for the same number.
>>
>>
>> On Tue, May 22, 2012 at 8:19 PM, Raul Kripalani<raul@> wrote:
>>> Hi
>>>
>>> Found what looks like a bug in camel-blueprint:
>>> https://issues.apache.org/jira/browse/CAMEL-5299. It would seem
>>> reasonable
>>> to fix it before 2.10.
>>>
>>> It basically renders EventNotifiers unusable in Blueprint. Not very
>>> familiar with Blueprint internals, and this is pretty critical init
>>> stuff,
>>> so I might take some time to submit a patch. Is someone willing to take
>>> a
>>> stab? (Let me know so we don't duplicate work).
>>>
>>> Thanks,
>>>
>>> *Raúl Kripalani*
>>> Principal Consultant | FuseSource Corp.
>>> raul@ | fusesource.com<http://www.fusesource.com/>
>>> skype: raul.fuse | twitter: @raulvk<http://twitter.com/raulvk>,
>>> @fusenews<http://twitter.com/fusenews>
>>>
>>> <http://twitter.com/fusenews>
>>>
>>> On 22 May 2012 14:18, Claus Ibsen<claus.ibsen@> wrote:
>>>
>>>> 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@>
>>>> 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@>
>>>> 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@> 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@>
>>>> wrote:
>>>>>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp<dkulp@> 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@>
>>>>>>>>> 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@
>>>>>>>>>>>> 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@ - 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@
>>>>>>>> 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@
>>>>>> 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@
>>>>> 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@
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>
>>
>>
>
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714022.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi Christian
according to what I've read many times by this thread I assumed we do always
skip running the OSGi tests on CI-Servers so why I did already check-in the
update for QuickFIX/J but apparently I did misunderstand something here.
I'm also puzzled about the last JDK7 build:
https://builds.apache.org/job/Camel.trunk.fulltest.java7/127/
Although I did enable the camel-quickfix module inside POM:
http://svn.apache.org/viewvc/camel/trunk/components/pom.xml?view=log&pathrev=1346880
It was still skipped through Jenkins! I also don't own the required rights
on Jenkins, for example for hitting a manual build, etc. Do you know who I
can ask for that right?
Babak
Christian Mueller wrote
>
> We have to wait for a few SMX bundle releases (at present, we have
> SNAPSHOT
> dependencies in our features definitions)...
>
> Best,
> Christian
>
> On Wed, Jun 6, 2012 at 3:39 PM, Babak Vahdat <babak.vahdat@>wrote:
>
>> Hi
>>
>> Upgrade to QuickFIX/J 1.5.2 is already done (CAMEL-5334). As well the
>> camel-quickfix module is now enabled again on the Jenkins
>> (Camel.trunk.fulltest.java7).
>>
>> I did test both on OS X as well as WIN (JDK 6 & JDK 7). So let's see how
>> it
>> will go through the next build...
>>
>> Babak
>>
>>
>> Claus Ibsen-2 wrote
>> >
>> > On Sat, Jun 2, 2012 at 10:17 PM, Babak Vahdat
>> > <babak.vahdat@> wrote:
>> >> The Java 7 support is not completely done yet as camel-quickfix is
>> still
>> >> the
>> >> last missing piece of the task (currently disabled on the CI-Server).
>> I
>> >> did
>> >> play around with upgrading to quickfixj 1.5.2 which first had some
>> >> compilation error as well as unit-test failures (NPE) which I easily
>> >> could
>> >> fix locally. I'm just waiting for the bundle of it:
>> >>
>> >> https://issues.apache.org/jira/browse/SMX4-1153
>> >>
>> >
>> > So does quickfix 1.5.2 work with Java 7?
>> >
>> > Regardless of what its not a showstopper for the Camel 2.10 release.
>> > We can add to known issues that camel-quickfix is known to not work
>> > with Java7 due QuickFix itself.
>> >
>> > The release will be built using java 6, and thus the camel-quickfix
>> > component will be included.
>> >
>> >> Babak
>> >>
>> >>
>> >> Claus Ibsen-2 wrote
>> >>>
>> >>> Hi
>> >>>
>> >>> So the Java 7 support is now done.
>> >>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>> >>>
>> >>> I have created a JIRA version 2.11, and moved some tickets from 2.10
>> to
>> >>> that.
>> >>> As we should focus on closing the last bugs, minor improvements etc.
>> >>> And keep eye on the CI servers to have a good build.
>> >>> And test the examples. I think the twitter example is broken.
>> >>>
>> >>> Anything in particular you would like in 2.10, that are not yet done?
>> >>>
>> >>>
>> >>>
>> >>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <dan@> wrote:
>> >>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>> >>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I
>> will
>> >>>>> have
>> >>>>> more often an eye on Jenkis to see whether we have issues we have
>> to
>> >>>>> fix.
>> >>>>> I will support Claus for the outstanding Java 7 issue.
>> >>>>> If everything run's fine, we should start the release procedure in
>> >>>>> this
>> >>>>> or
>> >>>>> next week. Do we already have release manager for this release?
>> >>>>
>> >>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later
>> >>>> tonight
>> >>>> or
>> >>>> tomorrow.
>> >>>>
>> >>>>
>> >>>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>> >>>>> release. I could do this, if no one else want do it.
>> >>>>
>> >>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm
>> also
>> >>>> a
>> >>>> bit uncomfortable saying "last official". 2.8.0 was released last
>> >>>> July
>> >>>> so
>> >>>> I would expect about one more before a full year of patches is up.
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Daniel Kulp
>> >>>> dan@
>> >>>> http://dankulp.com/blog
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Claus Ibsen
>> >>> -----------------
>> >>> FuseSource
>> >>> Email: cibsen@
>> >>> Web: http://fusesource.com
>> >>> Twitter: davsclaus, fusenews
>> >>> Blog: http://davsclaus.com
>> >>> Author of Camel in Action: http://www.manning.com/ibsen
>> >>>
>> >>
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713866.html
>> >> Sent from the Camel Development mailing list archive at Nabble.com.
>> >
>> >
>> >
>> > --
>> > Claus Ibsen
>> > -----------------
>> > FuseSource
>> > Email: cibsen@
>> > Web: http://fusesource.com
>> > Twitter: davsclaus, fusenews
>> > Blog: http://davsclaus.com
>> > Author of Camel in Action: http://www.manning.com/ibsen
>> >
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714066.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714097.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
We have to wait for a few SMX bundle releases (at present, we have SNAPSHOT
dependencies in our features definitions)...
Best,
Christian
On Wed, Jun 6, 2012 at 3:39 PM, Babak Vahdat <ba...@swissonline.ch>wrote:
> Hi
>
> Upgrade to QuickFIX/J 1.5.2 is already done (CAMEL-5334). As well the
> camel-quickfix module is now enabled again on the Jenkins
> (Camel.trunk.fulltest.java7).
>
> I did test both on OS X as well as WIN (JDK 6 & JDK 7). So let's see how it
> will go through the next build...
>
> Babak
>
>
> Claus Ibsen-2 wrote
> >
> > On Sat, Jun 2, 2012 at 10:17 PM, Babak Vahdat
> > <babak.vahdat@> wrote:
> >> The Java 7 support is not completely done yet as camel-quickfix is still
> >> the
> >> last missing piece of the task (currently disabled on the CI-Server). I
> >> did
> >> play around with upgrading to quickfixj 1.5.2 which first had some
> >> compilation error as well as unit-test failures (NPE) which I easily
> >> could
> >> fix locally. I'm just waiting for the bundle of it:
> >>
> >> https://issues.apache.org/jira/browse/SMX4-1153
> >>
> >
> > So does quickfix 1.5.2 work with Java 7?
> >
> > Regardless of what its not a showstopper for the Camel 2.10 release.
> > We can add to known issues that camel-quickfix is known to not work
> > with Java7 due QuickFix itself.
> >
> > The release will be built using java 6, and thus the camel-quickfix
> > component will be included.
> >
> >> Babak
> >>
> >>
> >> Claus Ibsen-2 wrote
> >>>
> >>> Hi
> >>>
> >>> So the Java 7 support is now done.
> >>> And when CXF 2.6.1 is out, we should be in a shape for a release.
> >>>
> >>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
> >>> that.
> >>> As we should focus on closing the last bugs, minor improvements etc.
> >>> And keep eye on the CI servers to have a good build.
> >>> And test the examples. I think the twitter example is broken.
> >>>
> >>> Anything in particular you would like in 2.10, that are not yet done?
> >>>
> >>>
> >>>
> >>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <dan@> wrote:
> >>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
> >>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
> >>>>> have
> >>>>> more often an eye on Jenkis to see whether we have issues we have to
> >>>>> fix.
> >>>>> I will support Claus for the outstanding Java 7 issue.
> >>>>> If everything run's fine, we should start the release procedure in
> >>>>> this
> >>>>> or
> >>>>> next week. Do we already have release manager for this release?
> >>>>
> >>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later
> >>>> tonight
> >>>> or
> >>>> tomorrow.
> >>>>
> >>>>
> >>>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
> >>>>> release. I could do this, if no one else want do it.
> >>>>
> >>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm
> also
> >>>> a
> >>>> bit uncomfortable saying "last official". 2.8.0 was released last
> >>>> July
> >>>> so
> >>>> I would expect about one more before a full year of patches is up.
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Daniel Kulp
> >>>> dan@
> >>>> http://dankulp.com/blog
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Claus Ibsen
> >>> -----------------
> >>> FuseSource
> >>> Email: cibsen@
> >>> Web: http://fusesource.com
> >>> Twitter: davsclaus, fusenews
> >>> Blog: http://davsclaus.com
> >>> Author of Camel in Action: http://www.manning.com/ibsen
> >>>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713866.html
> >> Sent from the Camel Development mailing list archive at Nabble.com.
> >
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > FuseSource
> > Email: cibsen@
> > Web: http://fusesource.com
> > Twitter: davsclaus, fusenews
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
> >
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714066.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
Hi
Upgrade to QuickFIX/J 1.5.2 is already done (CAMEL-5334). As well the
camel-quickfix module is now enabled again on the Jenkins
(Camel.trunk.fulltest.java7).
I did test both on OS X as well as WIN (JDK 6 & JDK 7). So let's see how it
will go through the next build...
Babak
Claus Ibsen-2 wrote
>
> On Sat, Jun 2, 2012 at 10:17 PM, Babak Vahdat
> <babak.vahdat@> wrote:
>> The Java 7 support is not completely done yet as camel-quickfix is still
>> the
>> last missing piece of the task (currently disabled on the CI-Server). I
>> did
>> play around with upgrading to quickfixj 1.5.2 which first had some
>> compilation error as well as unit-test failures (NPE) which I easily
>> could
>> fix locally. I'm just waiting for the bundle of it:
>>
>> https://issues.apache.org/jira/browse/SMX4-1153
>>
>
> So does quickfix 1.5.2 work with Java 7?
>
> Regardless of what its not a showstopper for the Camel 2.10 release.
> We can add to known issues that camel-quickfix is known to not work
> with Java7 due QuickFix itself.
>
> The release will be built using java 6, and thus the camel-quickfix
> component will be included.
>
>> Babak
>>
>>
>> Claus Ibsen-2 wrote
>>>
>>> Hi
>>>
>>> So the Java 7 support is now done.
>>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>>>
>>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
>>> that.
>>> As we should focus on closing the last bugs, minor improvements etc.
>>> And keep eye on the CI servers to have a good build.
>>> And test the examples. I think the twitter example is broken.
>>>
>>> Anything in particular you would like in 2.10, that are not yet done?
>>>
>>>
>>>
>>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <dan@> wrote:
>>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>>>>> have
>>>>> more often an eye on Jenkis to see whether we have issues we have to
>>>>> fix.
>>>>> I will support Claus for the outstanding Java 7 issue.
>>>>> If everything run's fine, we should start the release procedure in
>>>>> this
>>>>> or
>>>>> next week. Do we already have release manager for this release?
>>>>
>>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later
>>>> tonight
>>>> or
>>>> tomorrow.
>>>>
>>>>
>>>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>>>>> release. I could do this, if no one else want do it.
>>>>
>>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also
>>>> a
>>>> bit uncomfortable saying "last official". 2.8.0 was released last
>>>> July
>>>> so
>>>> I would expect about one more before a full year of patches is up.
>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Kulp
>>>> dan@
>>>> http://dankulp.com/blog
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713866.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5714066.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Sun, Jun 3, 2012 at 10:52 AM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> Good morning Claus
>
>> So does quickfix 1.5.2 work with Java 7?
>
> YES, with some really minor changes by it's source I could build it
> successfully (including green unit-tests) *both* using JDK 6 as well as JDK
> 7. However I only tested on my Mac:
>
> ~>mvn -version
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /Users/bvahdat/dev/apache-maven-3.0.4
> Java version: 1.7.0_06-ea, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.7.0_06.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.7.4", arch: "x86_64", family: "mac"
>
> As you already proposed we could also forget this step for 2.10 as a known
> issue. But IMHO that would be really a pitty to skip this for 2.10 as making
> it happen is *so* trivial and easy.
>
> The question is only how long it takes to have a bundle for it (which is a
> easy task as well)?
>
We need other bundles as well for the 2.10 release, such as the AWS
updated bundles.
The AWS 1.3.8 release has some improvements that already is in the
camel-aws components.
But the OSGi bundle is on 1.3.0 release. So we need this updated 1.3.8
bundle release.
Also qpid 0.16 would be nice, for the AMQP stuff. And there may be a
few others as well.
So the 1.5.2 quickfix could be an addition.
We should get on the SMX @dev list and ask them to cut a release of
bundles for us, that we need
for the 2.10 release.
> Babak
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713879.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
Good morning Claus
> So does quickfix 1.5.2 work with Java 7?
YES, with some really minor changes by it's source I could build it
successfully (including green unit-tests) *both* using JDK 6 as well as JDK
7. However I only tested on my Mac:
~>mvn -version
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /Users/bvahdat/dev/apache-maven-3.0.4
Java version: 1.7.0_06-ea, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_06.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.7.4", arch: "x86_64", family: "mac"
As you already proposed we could also forget this step for 2.10 as a known
issue. But IMHO that would be really a pitty to skip this for 2.10 as making
it happen is *so* trivial and easy.
The question is only how long it takes to have a bundle for it (which is a
easy task as well)?
Babak
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713879.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, Jun 2, 2012 at 10:17 PM, Babak Vahdat
<ba...@swissonline.ch> wrote:
> The Java 7 support is not completely done yet as camel-quickfix is still the
> last missing piece of the task (currently disabled on the CI-Server). I did
> play around with upgrading to quickfixj 1.5.2 which first had some
> compilation error as well as unit-test failures (NPE) which I easily could
> fix locally. I'm just waiting for the bundle of it:
>
> https://issues.apache.org/jira/browse/SMX4-1153
>
So does quickfix 1.5.2 work with Java 7?
Regardless of what its not a showstopper for the Camel 2.10 release.
We can add to known issues that camel-quickfix is known to not work
with Java7 due QuickFix itself.
The release will be built using java 6, and thus the camel-quickfix
component will be included.
> Babak
>
>
> Claus Ibsen-2 wrote
>>
>> Hi
>>
>> So the Java 7 support is now done.
>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>>
>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
>> that.
>> As we should focus on closing the last bugs, minor improvements etc.
>> And keep eye on the CI servers to have a good build.
>> And test the examples. I think the twitter example is broken.
>>
>> Anything in particular you would like in 2.10, that are not yet done?
>>
>>
>>
>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <dan@> wrote:
>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>>>> have
>>>> more often an eye on Jenkis to see whether we have issues we have to
>>>> fix.
>>>> I will support Claus for the outstanding Java 7 issue.
>>>> If everything run's fine, we should start the release procedure in this
>>>> or
>>>> next week. Do we already have release manager for this release?
>>>
>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later tonight
>>> or
>>> tomorrow.
>>>
>>>
>>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>>>> release. I could do this, if no one else want do it.
>>>
>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also a
>>> bit uncomfortable saying "last official". 2.8.0 was released last July
>>> so
>>> I would expect about one more before a full year of patches is up.
>>>
>>>
>>>
>>> --
>>> Daniel Kulp
>>> dan@
>>> http://dankulp.com/blog
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713866.html
> Sent from the Camel Development mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Babak Vahdat <ba...@swissonline.ch>.
The Java 7 support is not completely done yet as camel-quickfix is still the
last missing piece of the task (currently disabled on the CI-Server). I did
play around with upgrading to quickfixj 1.5.2 which first had some
compilation error as well as unit-test failures (NPE) which I easily could
fix locally. I'm just waiting for the bundle of it:
https://issues.apache.org/jira/browse/SMX4-1153
Babak
Claus Ibsen-2 wrote
>
> Hi
>
> So the Java 7 support is now done.
> And when CXF 2.6.1 is out, we should be in a shape for a release.
>
> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
> that.
> As we should focus on closing the last bugs, minor improvements etc.
> And keep eye on the CI servers to have a good build.
> And test the examples. I think the twitter example is broken.
>
> Anything in particular you would like in 2.10, that are not yet done?
>
>
>
> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <dan@> wrote:
>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>>> have
>>> more often an eye on Jenkis to see whether we have issues we have to
>>> fix.
>>> I will support Claus for the outstanding Java 7 issue.
>>> If everything run's fine, we should start the release procedure in this
>>> or
>>> next week. Do we already have release manager for this release?
>>
>> We'll need/want to wait for CXF 2.6.1 which I hope to build later tonight
>> or
>> tomorrow.
>>
>>
>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>>> release. I could do this, if no one else want do it.
>>
>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also a
>> bit uncomfortable saying "last official". 2.8.0 was released last July
>> so
>> I would expect about one more before a full year of patches is up.
>>
>>
>>
>> --
>> Daniel Kulp
>> dan@
>> http://dankulp.com/blog
>>
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
--
View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Apache-Camel-2-10-release-tp5691194p5713866.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, Jun 2, 2012 at 6:04 PM, Daniel Kulp <dk...@apache.org> wrote:
> On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen wrote:
>> Hi
>>
>> So the Java 7 support is now done.
>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>>
>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
>> that. As we should focus on closing the last bugs, minor improvements
>> etc. And keep eye on the CI servers to have a good build.
>> And test the examples. I think the twitter example is broken.
>
> Could we NOT do that and just un-assign a fix-version in the future? If
> someone is not actively working on it, it shouldn't have a version (or a an
> assignee). People may see those and say "oh, someone is fixing it for
> 2.11, cool" and then 2.11 comes along and it gets moved.
>
Yeah that could be a good idea next time.
In general though its the people who have tickets assigned that should
once in a while
check their tickets and reassign/move etc. appropriately.
Maybe after the 2.10 release we could also cleanup the JIRA tickets.
There are untouched tickets that are becoming rather old, etc.
Also tickets about technologies that may not be any priority anymore etc.
Anyway lets get the 2.10 out of the door first.
> Dan
>
>>
>> Anything in particular you would like in 2.10, that are not yet done?
>>
>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <da...@kulp.com> wrote:
>> > On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>> >> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>> >> have more often an eye on Jenkis to see whether we have issues we have
>> >> to fix. I will support Claus for the outstanding Java 7 issue.
>> >> If everything run's fine, we should start the release procedure in this
>> >> or next week. Do we already have release manager for this release?
>> >
>> > We'll need/want to wait for CXF 2.6.1 which I hope to build later
>> > tonight or tomorrow.
>> >
>> >> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>> >> release. I could do this, if no one else want do it.
>> >
>> > We'll also need/want to wait for 2.5.4 for a similar reason. I'm also
>> > a
>> > bit uncomfortable saying "last official". 2.8.0 was released last
>> > July so I would expect about one more before a full year of patches is
>> > up.
>> >
>> >
>> >
>> > --
>> > Daniel Kulp
>> > dan@kulp.com
>> > http://dankulp.com/blog
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
+1
On 06/02/2012 02:39 PM, Johan Edstrom wrote:
> +1, would be less confusing.
>
> On Jun 2, 2012, at 12:18 PM, David Karlsen wrote:
>
>> +1 to that.
>>
>> 2012/6/2 Daniel Kulp<dk...@apache.org>:
>>> On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen wrote:
>>>> Hi
>>>>
>>>> So the Java 7 support is now done.
>>>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>>>>
>>>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
>>>> that. As we should focus on closing the last bugs, minor improvements
>>>> etc. And keep eye on the CI servers to have a good build.
>>>> And test the examples. I think the twitter example is broken.
>>>
>>> Could we NOT do that and just un-assign a fix-version in the future? If
>>> someone is not actively working on it, it shouldn't have a version (or a an
>>> assignee). People may see those and say "oh, someone is fixing it for
>>> 2.11, cool" and then 2.11 comes along and it gets moved.
>>>
>>> Dan
>>>
>>>>
>>>> Anything in particular you would like in 2.10, that are not yet done?
>>>>
>>>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp<da...@kulp.com> wrote:
>>>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>>>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>>>>>> have more often an eye on Jenkis to see whether we have issues we have
>>>>>> to fix. I will support Claus for the outstanding Java 7 issue.
>>>>>> If everything run's fine, we should start the release procedure in this
>>>>>> or next week. Do we already have release manager for this release?
>>>>>
>>>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later
>>>>> tonight or tomorrow.
>>>>>
>>>>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>>>>>> release. I could do this, if no one else want do it.
>>>>>
>>>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also
>>>>> a
>>>>> bit uncomfortable saying "last official". 2.8.0 was released last
>>>>> July so I would expect about one more before a full year of patches is
>>>>> up.
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Daniel Kulp
>>>>> dan@kulp.com
>>>>> http://dankulp.com/blog
>>> --
>>> Daniel Kulp
>>> dkulp@apache.org - http://dankulp.com/blog
>>> Talend Community Coder - http://coders.talend.com
>>>
>>
>>
>>
>> --
>> --
>> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Johan Edstrom <se...@gmail.com>.
+1, would be less confusing.
On Jun 2, 2012, at 12:18 PM, David Karlsen wrote:
> +1 to that.
>
> 2012/6/2 Daniel Kulp <dk...@apache.org>:
>> On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen wrote:
>>> Hi
>>>
>>> So the Java 7 support is now done.
>>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>>>
>>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
>>> that. As we should focus on closing the last bugs, minor improvements
>>> etc. And keep eye on the CI servers to have a good build.
>>> And test the examples. I think the twitter example is broken.
>>
>> Could we NOT do that and just un-assign a fix-version in the future? If
>> someone is not actively working on it, it shouldn't have a version (or a an
>> assignee). People may see those and say "oh, someone is fixing it for
>> 2.11, cool" and then 2.11 comes along and it gets moved.
>>
>> Dan
>>
>>>
>>> Anything in particular you would like in 2.10, that are not yet done?
>>>
>>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <da...@kulp.com> wrote:
>>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>>>>> have more often an eye on Jenkis to see whether we have issues we have
>>>>> to fix. I will support Claus for the outstanding Java 7 issue.
>>>>> If everything run's fine, we should start the release procedure in this
>>>>> or next week. Do we already have release manager for this release?
>>>>
>>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later
>>>> tonight or tomorrow.
>>>>
>>>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>>>>> release. I could do this, if no one else want do it.
>>>>
>>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also
>>>> a
>>>> bit uncomfortable saying "last official". 2.8.0 was released last
>>>> July so I would expect about one more before a full year of patches is
>>>> up.
>>>>
>>>>
>>>>
>>>> --
>>>> Daniel Kulp
>>>> dan@kulp.com
>>>> http://dankulp.com/blog
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>
>
>
> --
> --
> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by David Karlsen <da...@gmail.com>.
+1 to that.
2012/6/2 Daniel Kulp <dk...@apache.org>:
> On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen wrote:
>> Hi
>>
>> So the Java 7 support is now done.
>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>>
>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
>> that. As we should focus on closing the last bugs, minor improvements
>> etc. And keep eye on the CI servers to have a good build.
>> And test the examples. I think the twitter example is broken.
>
> Could we NOT do that and just un-assign a fix-version in the future? If
> someone is not actively working on it, it shouldn't have a version (or a an
> assignee). People may see those and say "oh, someone is fixing it for
> 2.11, cool" and then 2.11 comes along and it gets moved.
>
> Dan
>
>>
>> Anything in particular you would like in 2.10, that are not yet done?
>>
>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <da...@kulp.com> wrote:
>> > On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>> >> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>> >> have more often an eye on Jenkis to see whether we have issues we have
>> >> to fix. I will support Claus for the outstanding Java 7 issue.
>> >> If everything run's fine, we should start the release procedure in this
>> >> or next week. Do we already have release manager for this release?
>> >
>> > We'll need/want to wait for CXF 2.6.1 which I hope to build later
>> > tonight or tomorrow.
>> >
>> >> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>> >> release. I could do this, if no one else want do it.
>> >
>> > We'll also need/want to wait for 2.5.4 for a similar reason. I'm also
>> > a
>> > bit uncomfortable saying "last official". 2.8.0 was released last
>> > July so I would expect about one more before a full year of patches is
>> > up.
>> >
>> >
>> >
>> > --
>> > Daniel Kulp
>> > dan@kulp.com
>> > http://dankulp.com/blog
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Daniel Kulp <dk...@apache.org>.
On Saturday, June 02, 2012 02:57:56 PM Claus Ibsen wrote:
> Hi
>
> So the Java 7 support is now done.
> And when CXF 2.6.1 is out, we should be in a shape for a release.
>
> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
> that. As we should focus on closing the last bugs, minor improvements
> etc. And keep eye on the CI servers to have a good build.
> And test the examples. I think the twitter example is broken.
Could we NOT do that and just un-assign a fix-version in the future? If
someone is not actively working on it, it shouldn't have a version (or a an
assignee). People may see those and say "oh, someone is fixing it for
2.11, cool" and then 2.11 comes along and it gets moved.
Dan
>
> Anything in particular you would like in 2.10, that are not yet done?
>
> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <da...@kulp.com> wrote:
> > On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
> >> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
> >> have more often an eye on Jenkis to see whether we have issues we have
> >> to fix. I will support Claus for the outstanding Java 7 issue.
> >> If everything run's fine, we should start the release procedure in this
> >> or next week. Do we already have release manager for this release?
> >
> > We'll need/want to wait for CXF 2.6.1 which I hope to build later
> > tonight or tomorrow.
> >
> >> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
> >> release. I could do this, if no one else want do it.
> >
> > We'll also need/want to wait for 2.5.4 for a similar reason. I'm also
> > a
> > bit uncomfortable saying "last official". 2.8.0 was released last
> > July so I would expect about one more before a full year of patches is
> > up.
> >
> >
> >
> > --
> > Daniel Kulp
> > dan@kulp.com
> > http://dankulp.com/blog
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
Ok, let's focus on the last *MUST* include issues to follow the release
early, release often Apache guideline...
I asked on the ServiceMix dev@ list for a new ServiceMix bundle release.
Best,
Christian
On Sun, Jun 3, 2012 at 9:45 PM, Hadrian Zbarcea <hz...@gmail.com> wrote:
> I have a couple of fixes for camel-jsch and camel-smtp.
> Hadrian
>
>
> On 06/02/2012 08:57 AM, Claus Ibsen wrote:
>
>> Hi
>>
>> So the Java 7 support is now done.
>> And when CXF 2.6.1 is out, we should be in a shape for a release.
>>
>> I have created a JIRA version 2.11, and moved some tickets from 2.10 to
>> that.
>> As we should focus on closing the last bugs, minor improvements etc.
>> And keep eye on the CI servers to have a good build.
>> And test the examples. I think the twitter example is broken.
>>
>> Anything in particular you would like in 2.10, that are not yet done?
>>
>>
>>
>> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp<da...@kulp.com> wrote:
>>
>>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>>>
>>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will
>>>> have
>>>> more often an eye on Jenkis to see whether we have issues we have to
>>>> fix.
>>>> I will support Claus for the outstanding Java 7 issue.
>>>> If everything run's fine, we should start the release procedure in this
>>>> or
>>>> next week. Do we already have release manager for this release?
>>>>
>>>
>>> We'll need/want to wait for CXF 2.6.1 which I hope to build later
>>> tonight or
>>> tomorrow.
>>>
>>>
>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>>>> release. I could do this, if no one else want do it.
>>>>
>>>
>>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also a
>>> bit uncomfortable saying "last official". 2.8.0 was released last
>>> July so
>>> I would expect about one more before a full year of patches is up.
>>>
>>>
>>>
>>> --
>>> Daniel Kulp
>>> dan@kulp.com
>>> http://dankulp.com/blog
>>>
>>>
>>
>>
>>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I have a couple of fixes for camel-jsch and camel-smtp.
Hadrian
On 06/02/2012 08:57 AM, Claus Ibsen wrote:
> Hi
>
> So the Java 7 support is now done.
> And when CXF 2.6.1 is out, we should be in a shape for a release.
>
> I have created a JIRA version 2.11, and moved some tickets from 2.10 to that.
> As we should focus on closing the last bugs, minor improvements etc.
> And keep eye on the CI servers to have a good build.
> And test the examples. I think the twitter example is broken.
>
> Anything in particular you would like in 2.10, that are not yet done?
>
>
>
> On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp<da...@kulp.com> wrote:
>> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will have
>>> more often an eye on Jenkis to see whether we have issues we have to fix.
>>> I will support Claus for the outstanding Java 7 issue.
>>> If everything run's fine, we should start the release procedure in this or
>>> next week. Do we already have release manager for this release?
>>
>> We'll need/want to wait for CXF 2.6.1 which I hope to build later tonight or
>> tomorrow.
>>
>>
>>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>>> release. I could do this, if no one else want do it.
>>
>> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also a
>> bit uncomfortable saying "last official". 2.8.0 was released last July so
>> I would expect about one more before a full year of patches is up.
>>
>>
>>
>> --
>> Daniel Kulp
>> dan@kulp.com
>> http://dankulp.com/blog
>>
>
>
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
So the Java 7 support is now done.
And when CXF 2.6.1 is out, we should be in a shape for a release.
I have created a JIRA version 2.11, and moved some tickets from 2.10 to that.
As we should focus on closing the last bugs, minor improvements etc.
And keep eye on the CI servers to have a good build.
And test the examples. I think the twitter example is broken.
Anything in particular you would like in 2.10, that are not yet done?
On Tue, May 29, 2012 at 3:37 PM, Daniel Kulp <da...@kulp.com> wrote:
> On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
>> Camel 2.9.0 is now out since almost 5 month. In the next days, I will have
>> more often an eye on Jenkis to see whether we have issues we have to fix.
>> I will support Claus for the outstanding Java 7 issue.
>> If everything run's fine, we should start the release procedure in this or
>> next week. Do we already have release manager for this release?
>
> We'll need/want to wait for CXF 2.6.1 which I hope to build later tonight or
> tomorrow.
>
>
>> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
>> release. I could do this, if no one else want do it.
>
> We'll also need/want to wait for 2.5.4 for a similar reason. I'm also a
> bit uncomfortable saying "last official". 2.8.0 was released last July so
> I would expect about one more before a full year of patches is up.
>
>
>
> --
> Daniel Kulp
> dan@kulp.com
> http://dankulp.com/blog
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Daniel Kulp <da...@kulp.com>.
On Monday, May 28, 2012 06:17:27 PM Christian Müller wrote:
> Camel 2.9.0 is now out since almost 5 month. In the next days, I will have
> more often an eye on Jenkis to see whether we have issues we have to fix.
> I will support Claus for the outstanding Java 7 issue.
> If everything run's fine, we should start the release procedure in this or
> next week. Do we already have release manager for this release?
We'll need/want to wait for CXF 2.6.1 which I hope to build later tonight or
tomorrow.
> Afterwards we should roll out Camel 2.8.7., our last official 2.8.
> release. I could do this, if no one else want do it.
We'll also need/want to wait for 2.5.4 for a similar reason. I'm also a
bit uncomfortable saying "last official". 2.8.0 was released last July so
I would expect about one more before a full year of patches is up.
--
Daniel Kulp
dan@kulp.com
http://dankulp.com/blog
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
Camel 2.9.0 is now out since almost 5 month. In the next days, I will have
more often an eye on Jenkis to see whether we have issues we have to fix. I
will support Claus for the outstanding Java 7 issue.
If everything run's fine, we should start the release procedure in this or
next week. Do we already have release manager for this release?
Afterwards we should roll out Camel 2.8.7., our last official 2.8. release.
I could do this, if no one else want do it.
Best,
Christian
On Thu, May 24, 2012 at 12:25 PM, Charles Moulliard <cm...@gmail.com>wrote:
> Hi Claus,
>
> I have finished the modifications (refactor in fact) for camel-websocket
> to support ws:// and wss:// protocols. So the timing sounds good to me to
> promote soon release 2.10
>
> Nevertheless, I would like to dissuccs the following poitn concerning
> Jetty version. We currently use Jetty 7.5.4. According to some discussions
> that I have had with Jean François Arcand and its blog, websocket support
> in Jetty 7.6.3 and 8.1.3 are stable now which is not the case with
> previous versions (http://jfarcand.wordpress.**com/category/websocket-2/<http://jfarcand.wordpress.com/category/websocket-2/>).
> So the point is, are we ok to migrate to 7.6.3 for apache camel project
> globally or only for websocket component ?
>
> Regards,
>
> Charles
>
>
> On 24/05/12 11:08, Claus Ibsen wrote:
>
>> Hi
>>
>> The blueprint issue have been fixed, and backported to 2.9 as well.
>>
>> The Java 7 upgrades seems really good now.
>> I can test all components, examples etc on my windows xp box.
>>
>> Only the osgi have a little issue with pax-exam locking the files, and
>> cannot rename downloaded bundles etc.
>> Thats a problem with pax-exam and not Camel.
>>
>> On the ASF CI servers the java7 tests is also good, they only fail due
>> concurrent testing with the -T option,
>> which triggers a race condition to find a free port number, and
>> causing a "Address already in use" failures.
>>
>> I will look into that later, to improve the camel-test
>> AvailablePortFinder, to use files to lock a given port number,
>> so concurrent JVMs can't compete for the same number.
>>
>>
>> On Tue, May 22, 2012 at 8:19 PM, Raul Kripalani<ra...@fusesource.com>
>> wrote:
>>
>>> Hi
>>>
>>> Found what looks like a bug in camel-blueprint:
>>> https://issues.apache.org/**jira/browse/CAMEL-5299<https://issues.apache.org/jira/browse/CAMEL-5299>.
>>> It would seem reasonable
>>> to fix it before 2.10.
>>>
>>> It basically renders EventNotifiers unusable in Blueprint. Not very
>>> familiar with Blueprint internals, and this is pretty critical init
>>> stuff,
>>> so I might take some time to submit a patch. Is someone willing to take a
>>> stab? (Let me know so we don't duplicate work).
>>>
>>> Thanks,
>>>
>>> *Raúl Kripalani*
>>> Principal Consultant | FuseSource Corp.
>>> raul@fusesource.com | fusesource.com<http://www.**fusesource.com/<http://www.fusesource.com/>
>>> >
>>> skype: raul.fuse | twitter: @raulvk<http://twitter.com/**raulvk<http://twitter.com/raulvk>
>>> >,
>>> @fusenews<http://twitter.com/**fusenews <http://twitter.com/fusenews>>
>>>
>>> <http://twitter.com/fusenews>
>>>
>>> On 22 May 2012 14:18, Claus Ibsen<cl...@gmail.com> wrote:
>>>
>>> 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<cl...@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<cl...@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
>>>>>> <ch...@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<cl...@gmail.com>
>>>>>>>
>>>>>> wrote:
>>>>
>>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp<dk...@apache.org> wrote:
>>>>>>>>
>>>>>>>>> The latest Jenkins build definitely looks a TON better:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> https://builds.apache.org/job/**Camel.trunk.fulltest.java7/82/<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<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<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/
>>>>
>>>>
>>
>>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Charles Moulliard <cm...@gmail.com>.
Hi Claus,
I have finished the modifications (refactor in fact) for camel-websocket
to support ws:// and wss:// protocols. So the timing sounds good to me
to promote soon release 2.10
Nevertheless, I would like to dissuccs the following poitn concerning
Jetty version. We currently use Jetty 7.5.4. According to some
discussions that I have had with Jean François Arcand and its blog,
websocket support in Jetty 7.6.3 and 8.1.3 are stable now which is not
the case with previous versions
(http://jfarcand.wordpress.com/category/websocket-2/). So the point is,
are we ok to migrate to 7.6.3 for apache camel project globally or only
for websocket component ?
Regards,
Charles
On 24/05/12 11:08, Claus Ibsen wrote:
> Hi
>
> The blueprint issue have been fixed, and backported to 2.9 as well.
>
> The Java 7 upgrades seems really good now.
> I can test all components, examples etc on my windows xp box.
>
> Only the osgi have a little issue with pax-exam locking the files, and
> cannot rename downloaded bundles etc.
> Thats a problem with pax-exam and not Camel.
>
> On the ASF CI servers the java7 tests is also good, they only fail due
> concurrent testing with the -T option,
> which triggers a race condition to find a free port number, and
> causing a "Address already in use" failures.
>
> I will look into that later, to improve the camel-test
> AvailablePortFinder, to use files to lock a given port number,
> so concurrent JVMs can't compete for the same number.
>
>
> On Tue, May 22, 2012 at 8:19 PM, Raul Kripalani<ra...@fusesource.com> wrote:
>> Hi
>>
>> Found what looks like a bug in camel-blueprint:
>> https://issues.apache.org/jira/browse/CAMEL-5299. It would seem reasonable
>> to fix it before 2.10.
>>
>> It basically renders EventNotifiers unusable in Blueprint. Not very
>> familiar with Blueprint internals, and this is pretty critical init stuff,
>> so I might take some time to submit a patch. Is someone willing to take a
>> stab? (Let me know so we don't duplicate work).
>>
>> Thanks,
>>
>> *Raúl Kripalani*
>> Principal Consultant | FuseSource Corp.
>> raul@fusesource.com | fusesource.com<http://www.fusesource.com/>
>> skype: raul.fuse | twitter: @raulvk<http://twitter.com/raulvk>,
>> @fusenews<http://twitter.com/fusenews>
>>
>> <http://twitter.com/fusenews>
>>
>> On 22 May 2012 14:18, Claus Ibsen<cl...@gmail.com> wrote:
>>
>>> 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<cl...@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<cl...@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
>>>>> <ch...@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<cl...@gmail.com>
>>> wrote:
>>>>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp<dk...@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/
>>>
>
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
The blueprint issue have been fixed, and backported to 2.9 as well.
The Java 7 upgrades seems really good now.
I can test all components, examples etc on my windows xp box.
Only the osgi have a little issue with pax-exam locking the files, and
cannot rename downloaded bundles etc.
Thats a problem with pax-exam and not Camel.
On the ASF CI servers the java7 tests is also good, they only fail due
concurrent testing with the -T option,
which triggers a race condition to find a free port number, and
causing a "Address already in use" failures.
I will look into that later, to improve the camel-test
AvailablePortFinder, to use files to lock a given port number,
so concurrent JVMs can't compete for the same number.
On Tue, May 22, 2012 at 8:19 PM, Raul Kripalani <ra...@fusesource.com> wrote:
> Hi
>
> Found what looks like a bug in camel-blueprint:
> https://issues.apache.org/jira/browse/CAMEL-5299. It would seem reasonable
> to fix it before 2.10.
>
> It basically renders EventNotifiers unusable in Blueprint. Not very
> familiar with Blueprint internals, and this is pretty critical init stuff,
> so I might take some time to submit a patch. Is someone willing to take a
> stab? (Let me know so we don't duplicate work).
>
> Thanks,
>
> *Raúl Kripalani*
> Principal Consultant | FuseSource Corp.
> raul@fusesource.com | fusesource.com <http://www.fusesource.com/>
> skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>,
> @fusenews<http://twitter.com/fusenews>
>
> <http://twitter.com/fusenews>
>
> On 22 May 2012 14:18, Claus Ibsen <cl...@gmail.com> wrote:
>
>> 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 <cl...@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 <cl...@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
>> >> <ch...@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 <cl...@gmail.com>
>> wrote:
>> >>>
>> >>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dk...@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/
>>
--
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/
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Raul Kripalani <ra...@fusesource.com>.
Hi
Found what looks like a bug in camel-blueprint:
https://issues.apache.org/jira/browse/CAMEL-5299. It would seem reasonable
to fix it before 2.10.
It basically renders EventNotifiers unusable in Blueprint. Not very
familiar with Blueprint internals, and this is pretty critical init stuff,
so I might take some time to submit a patch. Is someone willing to take a
stab? (Let me know so we don't duplicate work).
Thanks,
*Raúl Kripalani*
Principal Consultant | FuseSource Corp.
raul@fusesource.com | fusesource.com <http://www.fusesource.com/>
skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>,
@fusenews<http://twitter.com/fusenews>
<http://twitter.com/fusenews>
On 22 May 2012 14:18, Claus Ibsen <cl...@gmail.com> wrote:
> 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 <cl...@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 <cl...@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
> >> <ch...@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 <cl...@gmail.com>
> wrote:
> >>>
> >>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dk...@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/
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
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 <cl...@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 <cl...@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
>> <ch...@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 <cl...@gmail.com> wrote:
>>>
>>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dk...@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 <cl...@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/
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
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 <cl...@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
> <ch...@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 <cl...@gmail.com> wrote:
>>
>>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dk...@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 <cl...@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/
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
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
<ch...@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 <cl...@gmail.com> wrote:
>
>> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dk...@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 <cl...@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/
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
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 <cl...@gmail.com> wrote:
> On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dk...@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 <cl...@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/
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, May 8, 2012 at 9:02 PM, Daniel Kulp <dk...@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 <cl...@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/
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Daniel Kulp <dk...@apache.org>.
The latest Jenkins build definitely looks a TON better:
https://builds.apache.org/job/Camel.trunk.fulltest.java7/82/
:-)
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?
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 <cl...@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
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Daniel Kulp <dk...@apache.org>.
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.jav
> a7/
>
> Best,
> Christian
>
> On Mon, May 7, 2012 at 4:27 PM, Claus Ibsen <cl...@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&jql
> > 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
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
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].
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.java7/
Best,
Christian
On Mon, May 7, 2012 at 4:27 PM, Claus Ibsen <cl...@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&jqlQuery=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/
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Willem Jiang <wi...@gmail.com>.
Karaf features validate plugin cannot load the full features which was
included. As the camel-itest-osgi can vaild the CXF related feature
works, we can revisit it after fixing the issue of validate plugin.
On 6/12/12 5:50 AM, Christian Müller wrote:
> $camel/platforms/karaf>mvn clean install -Pvalidate
> ...
> [WARNING] Failed to validate feature camel-cxf
> [WARNING] No export found to match
> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.bus.spring;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.i18n;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.attachment;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match javax.wsdl (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.context;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.endpoint;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap.interceptor;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.message;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.continuations;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration.blueprint;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.util;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.jaxws;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap.saaj;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.wsdl11;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.ws.addressing;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.version;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.invoker;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.resource;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.databinding.source;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.support;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.phase;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.security;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.classloader;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.handler;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.impl;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.jaxb;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.interceptors;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.frontend;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.client;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.feature;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.factory;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.staxutils;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.utils;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.databinding;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.jaxrs;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.message;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.interceptor;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Camel :: Platforms :: Apache Karaf ................ SUCCESS [2.800s]
> [INFO] Camel :: Platforms :: Apache Karaf :: Commands .... SUCCESS [7.677s]
> [INFO] Camel :: Platforms :: Apache Karaf :: Features .... FAILURE [6.751s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
>
> It looks there is something wrong with the camel-cxf feature...
>
> Best,
> Christian
>
> On Mon, Jun 11, 2012 at 11:44 PM, Christian Müller<
> christian.mueller@gmail.com> wrote:
>
>> $camel/platforms/karaf>mvn clean install -Pvalidate
>> ...
>> [INFO] BUILD FAILURE
>>
>> because we refer already to
>> org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
>> which isn't released until now...
>>
>> Best,
>> Christian
>>
>>
>> On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen<cl...@gmail.com>wrote:
>>
>>> On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard<cmoulliard@gmail.com
>>>> wrote:
>>>
>>>> I will try to have a look on that next week to allow to add static
>>>> resources
>>>>
>>>>
>>> I have fixed that. The demo works again.
>>>
>>>
>>>
>>>> On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen<cl...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>> I got the twitter websocket example fixed again, but fixing the
>>> websocket
>>>>> component.
>>>>> It failed to support the static resource server after the SSL
>>>>> implementations.
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> FuseSource
>>>>> Email: cibsen@fusesource.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus, fusenews
>>>>> Blog: http://davsclaus.com
>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>>
>>
>
--
Willem
----------------------------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, Jun 12, 2012 at 9:20 AM, Charles Moulliard <cm...@gmail.com>wrote:
> camel-cdi should be improved as we cannot really use it like now in OSGI
> container, .... I will discuss that with openejb team this week. Maybe we
> could postpone this component for camel 2.11
>
>
There is a world outside OSGi, so end users that do not use osgi should
benefit from cdi integration as well.
And its good to get components out to the community, so we can get feedback
/ they can become more mature / people can submit patches etc.
>
> On 12/06/12 04:40, Willem Jiang wrote:
>
>> For the camel-cdi, current we don't have the cdi container works in OSGi,
>> I also checked the code of camel-cdi, it is related on Apache detaspike,
>> we may need some time to get it work with other cdi container.
>>
>>
>> On Tue Jun 12 05:56:56 2012, Christian Müller wrote:
>>
>>> We have a similar issue for camel-cdi. I opened a ticket for it:
>>> https://issues.apache.org/**jira/browse/CAMEL-5360<https://issues.apache.org/jira/browse/CAMEL-5360>
>>>
>>> Best,
>>> Christian
>>>
>>> On Mon, Jun 11, 2012 at 11:50 PM, Christian Müller<
>>> christian.mueller@gmail.com> wrote:
>>>
>>> $camel/platforms/karaf>mvn clean install -Pvalidate
>>>> ...
>>>> [WARNING] Failed to validate feature camel-cxf
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.binding.soap;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.bus.spring;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.common.i18n;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.attachment;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.headers;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.binding.soap.**model;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match javax.wsdl (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.transport;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match org.apache.cxf.wsdl;version="[**
>>>> 2.4,2.7)"
>>>> (imported by mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.common.logging;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match org.apache.cxf.io;version="[2.**
>>>> 4,2.7)"
>>>> (imported by mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match org.apache.cxf;version="[2.4,**2.7)"
>>>> (imported by mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxws.context;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.helpers;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.endpoint;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.binding.soap.**interceptor;version="[2.4,2.7)**"
>>>> (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.message;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.continuations;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.configuration.**blueprint;version="[2.4,2.7)" (imported
>>>> by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.common.util;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.headers;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.configuration;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxws;version="**[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.common.**injection;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.binding.soap.**saaj;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.wsdl11;version=**"[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.ws.addressing;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.version;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.service;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.service.**invoker;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.resource;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.databinding.**source;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxrs.model;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxws.support;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.service.model;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.common.logging;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.phase;version="**[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.security;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.common.**classloader;version="[2.4,2.7)**" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxws.handler;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxrs.impl;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.helpers;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match org.apache.cxf.wsdl;version="[**
>>>> 2.4,2.7)"
>>>> (imported by mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.binding;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.transport;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match org.apache.cxf.jaxb;version="[**
>>>> 2.4,2.7)"
>>>> (imported by mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxws.**interceptors;version="[2.4,2.**7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.frontend;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.service.model;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.configuration.**spring;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.common.**injection;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.binding.soap;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxrs.client;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.feature;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.service.**factory;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.staxutils;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match org.apache.cxf.io;version="[2.**
>>>> 4,2.7)"
>>>> (imported by mvn:org.apache.camel/camel-**cxf-transport/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxrs.utils;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match org.apache.cxf;version="[2.4,**2.7)"
>>>> (imported by mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.databinding;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.jaxrs;version="**[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.message;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.configuration.**spring;version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [WARNING] No export found to match
>>>> org.apache.cxf.interceptor;**version="[2.4,2.7)" (imported by
>>>> mvn:org.apache.camel/camel-**cxf/2.10-SNAPSHOT)
>>>> [INFO]
>>>> ------------------------------**------------------------------**------------
>>>>
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] Camel :: Platforms :: Apache Karaf ................ SUCCESS
>>>> [2.800s]
>>>> [INFO] Camel :: Platforms :: Apache Karaf :: Commands .... SUCCESS
>>>> [7.677s]
>>>> [INFO] Camel :: Platforms :: Apache Karaf :: Features .... FAILURE
>>>> [6.751s]
>>>> [INFO]
>>>> ------------------------------**------------------------------**------------
>>>>
>>>> [INFO] BUILD FAILURE
>>>>
>>>> It looks there is something wrong with the camel-cxf feature...
>>>>
>>>> Best,
>>>> Christian
>>>>
>>>>
>>>> On Mon, Jun 11, 2012 at 11:44 PM, Christian Müller<
>>>> christian.mueller@gmail.com> wrote:
>>>>
>>>> $camel/platforms/karaf>mvn clean install -Pvalidate
>>>>> ...
>>>>> [INFO] BUILD FAILURE
>>>>>
>>>>> because we refer already to
>>>>> org.apache.servicemix.bundles:**org.apache.servicemix.bundles.**quickfix:jar:1.5.2_1
>>>>>
>>>>> which isn't released until now...
>>>>>
>>>>> Best,
>>>>> Christian
>>>>>
>>>>>
>>>>> On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen<cl...@gmail.com>**
>>>>> wrote:
>>>>>
>>>>> On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard<
>>>>>> cmoulliard@gmail.com
>>>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>
>>>>>> I will try to have a look on that next week to allow to add static
>>>>>>> resources
>>>>>>>
>>>>>>>
>>>>>>> I have fixed that. The demo works again.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen<cl...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi
>>>>>>>>
>>>>>>>> I got the twitter websocket example fixed again, but fixing the
>>>>>>>>
>>>>>>> websocket
>>>>>>
>>>>>>> component.
>>>>>>>> It failed to support the static resource server after the SSL
>>>>>>>> implementations.
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Claus Ibsen
>>>>>>>> -----------------
>>>>>>>> FuseSource
>>>>>>>> Email: cibsen@fusesource.com
>>>>>>>> Web: http://fusesource.com
>>>>>>>> Twitter: davsclaus, fusenews
>>>>>>>> Blog: http://davsclaus.com
>>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> FuseSource
>>>>>> Email: cibsen@fusesource.com
>>>>>> Web: http://fusesource.com
>>>>>> Twitter: davsclaus, fusenews
>>>>>> Blog: http://davsclaus.com
>>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>>
>> --
>> Willem
>> ------------------------------**----
>> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
>> FuseSource
>> Web: http://www.fusesource.com
>> Blog: http://willemjiang.blogspot.**com<http://willemjiang.blogspot.com>(English)
>> http://jnn.javaeye.com (Chinese)
>> Twitter: willemjiang
>> Weibo: willemjiang
>>
>>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Charles Moulliard <cm...@gmail.com>.
camel-cdi should be improved as we cannot really use it like now in OSGI
container, .... I will discuss that with openejb team this week. Maybe
we could postpone this component for camel 2.11
On 12/06/12 04:40, Willem Jiang wrote:
> For the camel-cdi, current we don't have the cdi container works in OSGi,
> I also checked the code of camel-cdi, it is related on Apache
> detaspike, we may need some time to get it work with other cdi container.
>
>
> On Tue Jun 12 05:56:56 2012, Christian Müller wrote:
>> We have a similar issue for camel-cdi. I opened a ticket for it:
>> https://issues.apache.org/jira/browse/CAMEL-5360
>>
>> Best,
>> Christian
>>
>> On Mon, Jun 11, 2012 at 11:50 PM, Christian Müller<
>> christian.mueller@gmail.com> wrote:
>>
>>> $camel/platforms/karaf>mvn clean install -Pvalidate
>>> ...
>>> [WARNING] Failed to validate feature camel-cxf
>>> [WARNING] No export found to match
>>> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.bus.spring;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.common.i18n;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.attachment;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.binding.soap.model;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match javax.wsdl (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.wsdl;version="[2.4,2.7)"
>>> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.io;version="[2.4,2.7)"
>>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
>>> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxws.context;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.endpoint;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.binding.soap.interceptor;version="[2.4,2.7)"
>>> (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.message;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.continuations;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.configuration.blueprint;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.common.util;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.configuration;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxws;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.binding.soap.saaj;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.wsdl11;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.ws.addressing;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.version;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.service;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.service.invoker;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.resource;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.databinding.source;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxrs.model;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxws.support;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.phase;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.security;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.common.classloader;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxws.handler;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxrs.impl;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.wsdl;version="[2.4,2.7)"
>>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.binding;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxb;version="[2.4,2.7)"
>>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxws.interceptors;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.frontend;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxrs.client;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.feature;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.service.factory;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.staxutils;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.io;version="[2.4,2.7)"
>>> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxrs.utils;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
>>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.databinding;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.jaxrs;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.message;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [WARNING] No export found to match
>>> org.apache.cxf.interceptor;version="[2.4,2.7)" (imported by
>>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] Reactor Summary:
>>> [INFO]
>>> [INFO] Camel :: Platforms :: Apache Karaf ................ SUCCESS
>>> [2.800s]
>>> [INFO] Camel :: Platforms :: Apache Karaf :: Commands .... SUCCESS
>>> [7.677s]
>>> [INFO] Camel :: Platforms :: Apache Karaf :: Features .... FAILURE
>>> [6.751s]
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> [INFO] BUILD FAILURE
>>>
>>> It looks there is something wrong with the camel-cxf feature...
>>>
>>> Best,
>>> Christian
>>>
>>>
>>> On Mon, Jun 11, 2012 at 11:44 PM, Christian Müller<
>>> christian.mueller@gmail.com> wrote:
>>>
>>>> $camel/platforms/karaf>mvn clean install -Pvalidate
>>>> ...
>>>> [INFO] BUILD FAILURE
>>>>
>>>> because we refer already to
>>>> org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
>>>>
>>>> which isn't released until now...
>>>>
>>>> Best,
>>>> Christian
>>>>
>>>>
>>>> On Fri, Jun 8, 2012 at 11:41 AM, Claus
>>>> Ibsen<cl...@gmail.com>wrote:
>>>>
>>>>> On Fri, Jun 8, 2012 at 11:38 AM, Charles
>>>>> Moulliard<cmoulliard@gmail.com
>>>>>> wrote:
>>>>>
>>>>>> I will try to have a look on that next week to allow to add static
>>>>>> resources
>>>>>>
>>>>>>
>>>>> I have fixed that. The demo works again.
>>>>>
>>>>>
>>>>>
>>>>>> On Fri, Jun 8, 2012 at 11:31 AM, Claus
>>>>>> Ibsen<cl...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> I got the twitter websocket example fixed again, but fixing the
>>>>> websocket
>>>>>>> component.
>>>>>>> It failed to support the static resource server after the SSL
>>>>>>> implementations.
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Claus Ibsen
>>>>>>> -----------------
>>>>>>> FuseSource
>>>>>>> Email: cibsen@fusesource.com
>>>>>>> Web: http://fusesource.com
>>>>>>> Twitter: davsclaus, fusenews
>>>>>>> Blog: http://davsclaus.com
>>>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> -----------------
>>>>> FuseSource
>>>>> Email: cibsen@fusesource.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: davsclaus, fusenews
>>>>> Blog: http://davsclaus.com
>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>
>>>>
>>>>
>>>
>>
>
>
>
> --
> Willem
> ----------------------------------
> CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Willem Jiang <wi...@gmail.com>.
For the camel-cdi, current we don't have the cdi container works in
OSGi,
I also checked the code of camel-cdi, it is related on Apache
detaspike, we may need some time to get it work with other cdi
container.
On Tue Jun 12 05:56:56 2012, Christian Müller wrote:
> We have a similar issue for camel-cdi. I opened a ticket for it:
> https://issues.apache.org/jira/browse/CAMEL-5360
>
> Best,
> Christian
>
> On Mon, Jun 11, 2012 at 11:50 PM, Christian Müller<
> christian.mueller@gmail.com> wrote:
>
>> $camel/platforms/karaf>mvn clean install -Pvalidate
>> ...
>> [WARNING] Failed to validate feature camel-cxf
>> [WARNING] No export found to match
>> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.bus.spring;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.common.i18n;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.attachment;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.binding.soap.model;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match javax.wsdl (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
>> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
>> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxws.context;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.endpoint;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.binding.soap.interceptor;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.message;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.continuations;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.configuration.blueprint;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.common.util;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.configuration;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxws;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.binding.soap.saaj;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.wsdl11;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.ws.addressing;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.version;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.service;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.service.invoker;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.resource;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.databinding.source;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxrs.model;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxws.support;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.phase;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.security;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.common.classloader;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxws.handler;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxrs.impl;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.binding;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match org.apache.cxf.jaxb;version="[2.4,2.7)"
>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxws.interceptors;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.frontend;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxrs.client;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.feature;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.service.factory;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.staxutils;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
>> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxrs.utils;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
>> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.databinding;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.jaxrs;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.message;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [WARNING] No export found to match
>> org.apache.cxf.interceptor;version="[2.4,2.7)" (imported by
>> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Camel :: Platforms :: Apache Karaf ................ SUCCESS [2.800s]
>> [INFO] Camel :: Platforms :: Apache Karaf :: Commands .... SUCCESS [7.677s]
>> [INFO] Camel :: Platforms :: Apache Karaf :: Features .... FAILURE [6.751s]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>>
>> It looks there is something wrong with the camel-cxf feature...
>>
>> Best,
>> Christian
>>
>>
>> On Mon, Jun 11, 2012 at 11:44 PM, Christian Müller<
>> christian.mueller@gmail.com> wrote:
>>
>>> $camel/platforms/karaf>mvn clean install -Pvalidate
>>> ...
>>> [INFO] BUILD FAILURE
>>>
>>> because we refer already to
>>> org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
>>> which isn't released until now...
>>>
>>> Best,
>>> Christian
>>>
>>>
>>> On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen<cl...@gmail.com>wrote:
>>>
>>>> On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard<cmoulliard@gmail.com
>>>>> wrote:
>>>>
>>>>> I will try to have a look on that next week to allow to add static
>>>>> resources
>>>>>
>>>>>
>>>> I have fixed that. The demo works again.
>>>>
>>>>
>>>>
>>>>> On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen<cl...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>> I got the twitter websocket example fixed again, but fixing the
>>>> websocket
>>>>>> component.
>>>>>> It failed to support the static resource server after the SSL
>>>>>> implementations.
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Claus Ibsen
>>>>>> -----------------
>>>>>> FuseSource
>>>>>> Email: cibsen@fusesource.com
>>>>>> Web: http://fusesource.com
>>>>>> Twitter: davsclaus, fusenews
>>>>>> Blog: http://davsclaus.com
>>>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.com
>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>
>>>
>>>
>>
>
--
Willem
----------------------------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
We have a similar issue for camel-cdi. I opened a ticket for it:
https://issues.apache.org/jira/browse/CAMEL-5360
Best,
Christian
On Mon, Jun 11, 2012 at 11:50 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> $camel/platforms/karaf>mvn clean install -Pvalidate
> ...
> [WARNING] Failed to validate feature camel-cxf
> [WARNING] No export found to match
> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.bus.spring;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.i18n;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.attachment;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match javax.wsdl (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.context;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.endpoint;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap.interceptor;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.message;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.continuations;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration.blueprint;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.util;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.headers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap.saaj;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.wsdl11;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.ws.addressing;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.version;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.invoker;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.resource;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.databinding.source;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.support;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.phase;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.security;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.classloader;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.handler;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.impl;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.transport;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.jaxb;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxws.interceptors;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.frontend;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.client;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.feature;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.service.factory;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.staxutils;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs.utils;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
> (imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.databinding;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.jaxrs;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.message;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [WARNING] No export found to match
> org.apache.cxf.interceptor;version="[2.4,2.7)" (imported by
> mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Camel :: Platforms :: Apache Karaf ................ SUCCESS [2.800s]
> [INFO] Camel :: Platforms :: Apache Karaf :: Commands .... SUCCESS [7.677s]
> [INFO] Camel :: Platforms :: Apache Karaf :: Features .... FAILURE [6.751s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
>
> It looks there is something wrong with the camel-cxf feature...
>
> Best,
> Christian
>
>
> On Mon, Jun 11, 2012 at 11:44 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
>> $camel/platforms/karaf>mvn clean install -Pvalidate
>> ...
>> [INFO] BUILD FAILURE
>>
>> because we refer already to
>> org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
>> which isn't released until now...
>>
>> Best,
>> Christian
>>
>>
>> On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen <cl...@gmail.com>wrote:
>>
>>> On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard <cmoulliard@gmail.com
>>> >wrote:
>>>
>>> > I will try to have a look on that next week to allow to add static
>>> > resources
>>> >
>>> >
>>> I have fixed that. The demo works again.
>>>
>>>
>>>
>>> > On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen <cl...@gmail.com>
>>> > wrote:
>>> >
>>> > > Hi
>>> > >
>>> > > I got the twitter websocket example fixed again, but fixing the
>>> websocket
>>> > > component.
>>> > > It failed to support the static resource server after the SSL
>>> > > implementations.
>>> > >
>>> > >
>>> > > --
>>> > > Claus Ibsen
>>> > > -----------------
>>> > > FuseSource
>>> > > Email: cibsen@fusesource.com
>>> > > Web: http://fusesource.com
>>> > > Twitter: davsclaus, fusenews
>>> > > Blog: http://davsclaus.com
>>> > > Author of Camel in Action: http://www.manning.com/ibsen
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -----------------
>>> FuseSource
>>> Email: cibsen@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.com
>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>
>>
>>
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
$camel/platforms/karaf>mvn clean install -Pvalidate
...
[WARNING] Failed to validate feature camel-cxf
[WARNING] No export found to match
org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.bus.spring;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.common.i18n;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.attachment;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.headers;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.binding.soap.model;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match javax.wsdl (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.transport;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxws.context;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.endpoint;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.binding.soap.interceptor;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.message;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.continuations;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.configuration.blueprint;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.common.util;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.headers;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.configuration;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.jaxws;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.binding.soap.saaj;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.wsdl11;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.ws.addressing;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.version;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.service;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.service.invoker;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.resource;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.databinding.source;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxrs.model;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxws.support;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.common.logging;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.phase;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.security;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.common.classloader;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxws.handler;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxrs.impl;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.helpers;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.wsdl;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.binding;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.transport;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.jaxb;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxws.interceptors;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.frontend;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.service.model;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.common.injection;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.binding.soap;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxrs.client;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.feature;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.service.factory;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.staxutils;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.io;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf-transport/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.jaxrs.utils;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.databinding;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match org.apache.cxf.jaxrs;version="[2.4,2.7)"
(imported by mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.message;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.configuration.spring;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[WARNING] No export found to match
org.apache.cxf.interceptor;version="[2.4,2.7)" (imported by
mvn:org.apache.camel/camel-cxf/2.10-SNAPSHOT)
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Camel :: Platforms :: Apache Karaf ................ SUCCESS [2.800s]
[INFO] Camel :: Platforms :: Apache Karaf :: Commands .... SUCCESS [7.677s]
[INFO] Camel :: Platforms :: Apache Karaf :: Features .... FAILURE [6.751s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
It looks there is something wrong with the camel-cxf feature...
Best,
Christian
On Mon, Jun 11, 2012 at 11:44 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> $camel/platforms/karaf>mvn clean install -Pvalidate
> ...
> [INFO] BUILD FAILURE
>
> because we refer already to
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
> which isn't released until now...
>
> Best,
> Christian
>
>
> On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen <cl...@gmail.com>wrote:
>
>> On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard <cmoulliard@gmail.com
>> >wrote:
>>
>> > I will try to have a look on that next week to allow to add static
>> > resources
>> >
>> >
>> I have fixed that. The demo works again.
>>
>>
>>
>> > On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen <cl...@gmail.com>
>> > wrote:
>> >
>> > > Hi
>> > >
>> > > I got the twitter websocket example fixed again, but fixing the
>> websocket
>> > > component.
>> > > It failed to support the static resource server after the SSL
>> > > implementations.
>> > >
>> > >
>> > > --
>> > > Claus Ibsen
>> > > -----------------
>> > > FuseSource
>> > > Email: cibsen@fusesource.com
>> > > Web: http://fusesource.com
>> > > Twitter: davsclaus, fusenews
>> > > Blog: http://davsclaus.com
>> > > Author of Camel in Action: http://www.manning.com/ibsen
>> > >
>> >
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Willem Jiang <wi...@gmail.com>.
quickfix 1.5.2_1 bundle is on the way, we could wait for it a while.
On 6/12/12 5:44 AM, Christian Müller wrote:
> $camel/platforms/karaf>mvn clean install -Pvalidate
> ...
> [INFO] BUILD FAILURE
>
> because we refer already to
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
> which isn't released until now...
>
> Best,
> Christian
>
> On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen<cl...@gmail.com> wrote:
>
>> On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard<cmoulliard@gmail.com
>>> wrote:
>>
>>> I will try to have a look on that next week to allow to add static
>>> resources
>>>
>>>
>> I have fixed that. The demo works again.
>>
>>
>>
>>> On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen<cl...@gmail.com>
>>> wrote:
>>>
>>>> Hi
>>>>
>>>> I got the twitter websocket example fixed again, but fixing the
>> websocket
>>>> component.
>>>> It failed to support the static resource server after the SSL
>>>> implementations.
>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> -----------------
>>>> FuseSource
>>>> Email: cibsen@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus, fusenews
>>>> Blog: http://davsclaus.com
>>>> Author of Camel in Action: http://www.manning.com/ibsen
>>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
>>
>
--
Willem
----------------------------------
CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Christian Müller <ch...@gmail.com>.
$camel/platforms/karaf>mvn clean install -Pvalidate
...
[INFO] BUILD FAILURE
because we refer already to
org.apache.servicemix.bundles:org.apache.servicemix.bundles.quickfix:jar:1.5.2_1
which isn't released until now...
Best,
Christian
On Fri, Jun 8, 2012 at 11:41 AM, Claus Ibsen <cl...@gmail.com> wrote:
> On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard <cmoulliard@gmail.com
> >wrote:
>
> > I will try to have a look on that next week to allow to add static
> > resources
> >
> >
> I have fixed that. The demo works again.
>
>
>
> > On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen <cl...@gmail.com>
> > wrote:
> >
> > > Hi
> > >
> > > I got the twitter websocket example fixed again, but fixing the
> websocket
> > > component.
> > > It failed to support the static resource server after the SSL
> > > implementations.
> > >
> > >
> > > --
> > > Claus Ibsen
> > > -----------------
> > > FuseSource
> > > Email: cibsen@fusesource.com
> > > Web: http://fusesource.com
> > > Twitter: davsclaus, fusenews
> > > Blog: http://davsclaus.com
> > > Author of Camel in Action: http://www.manning.com/ibsen
> > >
> >
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
On Fri, Jun 8, 2012 at 11:38 AM, Charles Moulliard <cm...@gmail.com>wrote:
> I will try to have a look on that next week to allow to add static
> resources
>
>
I have fixed that. The demo works again.
> On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen <cl...@gmail.com>
> wrote:
>
> > Hi
> >
> > I got the twitter websocket example fixed again, but fixing the websocket
> > component.
> > It failed to support the static resource server after the SSL
> > implementations.
> >
> >
> > --
> > Claus Ibsen
> > -----------------
> > FuseSource
> > Email: cibsen@fusesource.com
> > Web: http://fusesource.com
> > Twitter: davsclaus, fusenews
> > Blog: http://davsclaus.com
> > Author of Camel in Action: http://www.manning.com/ibsen
> >
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Charles Moulliard <cm...@gmail.com>.
I will try to have a look on that next week to allow to add static resources
On Fri, Jun 8, 2012 at 11:31 AM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> I got the twitter websocket example fixed again, but fixing the websocket
> component.
> It failed to support the static resource server after the SSL
> implementations.
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I got the twitter websocket example fixed again, but fixing the websocket
component.
It failed to support the static resource server after the SSL
implementations.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
The builds are done and the artifacts published [1]. I will verify the
artifacts and start the vote in the morning. Feel free to commit on trunk.
Hadrian
[1] https://repository.apache.org/content/repositories/orgapachecamel-251/
On 06/19/2012 10:03 AM, Hadrian Zbarcea wrote:
> I'll build the the 2.10.0 kits today. Please delay your commits to trunk
> until the kits are out. Thanks,
> Hadrian
>
> On 06/19/2012 01:08 AM, Claus Ibsen wrote:
>> Hi
>>
>> Okay I think we are getting in shape for cutting a release.
>>
>> The CI servers as ASF are all green (well its actually blue color) for
>> the last many days.
>> I recently did a full windows test with Java7 as well and that was
>> also a 100% success.
>>
>> We need documentation for that recent added component
>> - camel-guava-eventbus
>>
>> But Henryk is aware of this and promised to work on that.
>>
>>
>>
>> --
>> Claus Ibsen
>> -----------------
>> FuseSource
>> Email: cibsen@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus, fusenews
>> Blog: http://davsclaus.com
>> Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I'll build the the 2.10.0 kits today. Please delay your commits to trunk
until the kits are out. Thanks,
Hadrian
On 06/19/2012 01:08 AM, Claus Ibsen wrote:
> Hi
>
> Okay I think we are getting in shape for cutting a release.
>
> The CI servers as ASF are all green (well its actually blue color) for
> the last many days.
> I recently did a full windows test with Java7 as well and that was
> also a 100% success.
>
> We need documentation for that recent added component
> - camel-guava-eventbus
>
> But Henryk is aware of this and promised to work on that.
>
>
>
> --
> Claus Ibsen
> -----------------
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
> Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Okay I think we are getting in shape for cutting a release.
The CI servers as ASF are all green (well its actually blue color) for
the last many days.
I recently did a full windows test with Java7 as well and that was
also a 100% success.
We need documentation for that recent added component
- camel-guava-eventbus
But Henryk is aware of this and promised to work on that.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Thanks Willem.
The last outstanding issue [1] is something Claus is working with
Henryk. @Claus, should we wait? Do you anticipate it being done quickly?
Thanks,
Hadrian
[1] https://issues.apache.org/jira/browse/CAMEL-5341
On 06/18/2012 02:47 AM, Willem Jiang wrote:
> Hi Hadrian,
>
> I just cleaned up the my JIRAs for 2.10. I think you can go on to cut
> the release now.
>
> On Fri Jun 15 22:16:00 2012, Hadrian Zbarcea wrote:
>> There are 3 outstanding issues for 2.10.0, 2 assigned to Willem and 1
>> unassigned.
>>
>> Willem, what are your plans? The unassigned is not clear if it's a bug
>> or not. I'll plan to cut the release builds early next week then.
>>
>> Cheers,
>> Hadrian
>>
>>
>>
>> On 06/15/2012 04:48 AM, Claus Ibsen wrote:
>>> Hi
>>>
>>> Okay so I have fixed camel-rmi to use dynamic port numbers.
>>>
>>> I got 2 osgi failures on windows with java7
>>> 1) JpaBlueprintRouteTest
>>> 2) HdfsBlueprintRouteTest
>>>
>>>
>>> Ad 1)
>>> This fails due the old data from previous test is still around. A
>>> quick fix
>>> would be to change the test to use different entity, so its different
>>> tables.
>>> Or figure out a way to get the **** jpa provider to drop/recreate the
>>> schema.
>>>
>>> 2012-06-15 10:22:51,593 | ERROR | )-192.168.93.128 | DefaultErrorHandler
>>> | 72 - org.apache.camel.camel-core - 2.10.0.SNAPSHOT | Failed
>>> delivery for (MessageId: ID-vomit-4934-1339748567031
>>> -0-3 on ExchangeId: ID-vomit-4934-1339748567031-0-2). Exhausted after
>>> delivery attempt: 1 caught:
>>> org.springframework.transaction.CannotCreateTransactionException:
>>> Could not
>>> open JPA EntityManager for
>>> transaction; nested exception is<openjpa-2.2.0-r422266:1244990 nonfatal
>>> general error> org.apache.openjpa.persistence.PersistenceException:
>>> Table/View 'SENDEMAIL' already exists in Schema 'APP'. {st
>>> mnt 17844447 CREATE TABLE SENDEMAIL (id BIGINT NOT NULL, address
>>> VARCHAR(255), PRIMARY KEY (id))} [code=30000, state=X0Y32]
>>> org.springframework.transaction.CannotCreateTransactionException:
>>> Could not
>>> open JPA EntityManager for transaction; nested exception is
>>> <openjpa-2.2.0-r422266:1244990 nonfatal general error> org.apach
>>> e.openjpa.persistence.PersistenceException: Table/View 'SENDEMAIL'
>>> already
>>> exists in Schema 'APP'. {stmnt 17844447 CREATE TABLE SENDEMAIL (id
>>> BIGINT
>>> NOT NULL, address VARCHAR(255), PRIMARY KEY (id))}
>>> [code=30000, state=X0Y32]
>>> at
>>> org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:382)[115:org.springframework.orm:3.0.7.RELEASE]
>>>
>>>
>>> at
>>> org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)[79:org.springframework.transaction:3.0.7.RELEASE]
>>>
>>>
>>> at
>>> org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127)[79:org.springframework.transaction:3.0.7.RELEASE]
>>>
>>>
>>> at
>>> org.apache.camel.component.jpa.JpaTemplateTransactionStrategy.execute(JpaTemplateTransactionStrategy.java:78)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
>>>
>>>
>>> at
>>> org.apache.camel.component.jpa.JpaProducer.process(JpaProducer.java:50)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
>>>
>>>
>>> at
>>> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[72:org.apache.camel.camel-core:2.10.0.SNAPSHOT]
>>>
>>>
>>>
>>>
>>>
>>> Ad 2)
>>>
>>> I guess maybe its something with the camel-hdfs feature. I could not
>>> find
>>> much in the logs.
>>>
>>> -------------------------------------------------------------------------------
>>>
>>>
>>> Test set: org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest
>>> -------------------------------------------------------------------------------
>>>
>>>
>>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>>> 91.875 sec
>>> <<< FAILURE!
>>> testWriteAndReadString:HdfsBlueprintRouteTest.testWriteAndReadString:KarafTestContainer{mvn:org.apache.karaf/apache-karaf/2.2.7/tar.gz}(org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest)
>>>
>>>
>>> Time elapsed: 20.719 sec<<< FAILURE!
>>> java.lang.AssertionError: Gave up waiting for service
>>> (&(objectClass=org.apache.camel.CamelContext)(camel.context.symbolicname=CamelBlueprintHdfsTestBundle))
>>>
>>>
>>> at org.junit.Assert.fail(Assert.java:93)
>>> at
>>> org.ops4j.pax.exam.junit.JUnit4TestRunner$3.evaluate(JUnit4TestRunner.java:293)
>>>
>>>
>>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>>>
>>
>
>
>
> --
> Willem
> ----------------------------------
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
> Weibo: willemjiang
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Willem Jiang <wi...@gmail.com>.
Hi Hadrian,
I just cleaned up the my JIRAs for 2.10. I think you can go on to cut
the release now.
On Fri Jun 15 22:16:00 2012, Hadrian Zbarcea wrote:
> There are 3 outstanding issues for 2.10.0, 2 assigned to Willem and 1
> unassigned.
>
> Willem, what are your plans? The unassigned is not clear if it's a bug
> or not. I'll plan to cut the release builds early next week then.
>
> Cheers,
> Hadrian
>
>
>
> On 06/15/2012 04:48 AM, Claus Ibsen wrote:
>> Hi
>>
>> Okay so I have fixed camel-rmi to use dynamic port numbers.
>>
>> I got 2 osgi failures on windows with java7
>> 1) JpaBlueprintRouteTest
>> 2) HdfsBlueprintRouteTest
>>
>>
>> Ad 1)
>> This fails due the old data from previous test is still around. A
>> quick fix
>> would be to change the test to use different entity, so its different
>> tables.
>> Or figure out a way to get the **** jpa provider to drop/recreate the
>> schema.
>>
>> 2012-06-15 10:22:51,593 | ERROR | )-192.168.93.128 | DefaultErrorHandler
>> | 72 - org.apache.camel.camel-core - 2.10.0.SNAPSHOT | Failed
>> delivery for (MessageId: ID-vomit-4934-1339748567031
>> -0-3 on ExchangeId: ID-vomit-4934-1339748567031-0-2). Exhausted after
>> delivery attempt: 1 caught:
>> org.springframework.transaction.CannotCreateTransactionException:
>> Could not
>> open JPA EntityManager for
>> transaction; nested exception is<openjpa-2.2.0-r422266:1244990 nonfatal
>> general error> org.apache.openjpa.persistence.PersistenceException:
>> Table/View 'SENDEMAIL' already exists in Schema 'APP'. {st
>> mnt 17844447 CREATE TABLE SENDEMAIL (id BIGINT NOT NULL, address
>> VARCHAR(255), PRIMARY KEY (id))} [code=30000, state=X0Y32]
>> org.springframework.transaction.CannotCreateTransactionException:
>> Could not
>> open JPA EntityManager for transaction; nested exception is
>> <openjpa-2.2.0-r422266:1244990 nonfatal general error> org.apach
>> e.openjpa.persistence.PersistenceException: Table/View 'SENDEMAIL'
>> already
>> exists in Schema 'APP'. {stmnt 17844447 CREATE TABLE SENDEMAIL (id
>> BIGINT
>> NOT NULL, address VARCHAR(255), PRIMARY KEY (id))}
>> [code=30000, state=X0Y32]
>> at
>> org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:382)[115:org.springframework.orm:3.0.7.RELEASE]
>>
>> at
>> org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)[79:org.springframework.transaction:3.0.7.RELEASE]
>>
>> at
>> org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127)[79:org.springframework.transaction:3.0.7.RELEASE]
>>
>> at
>> org.apache.camel.component.jpa.JpaTemplateTransactionStrategy.execute(JpaTemplateTransactionStrategy.java:78)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
>>
>> at
>> org.apache.camel.component.jpa.JpaProducer.process(JpaProducer.java:50)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
>>
>> at
>> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[72:org.apache.camel.camel-core:2.10.0.SNAPSHOT]
>>
>>
>>
>>
>> Ad 2)
>>
>> I guess maybe its something with the camel-hdfs feature. I could not
>> find
>> much in the logs.
>>
>> -------------------------------------------------------------------------------
>>
>> Test set: org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest
>> -------------------------------------------------------------------------------
>>
>> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> 91.875 sec
>> <<< FAILURE!
>> testWriteAndReadString:HdfsBlueprintRouteTest.testWriteAndReadString:KarafTestContainer{mvn:org.apache.karaf/apache-karaf/2.2.7/tar.gz}(org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest)
>>
>> Time elapsed: 20.719 sec<<< FAILURE!
>> java.lang.AssertionError: Gave up waiting for service
>> (&(objectClass=org.apache.camel.CamelContext)(camel.context.symbolicname=CamelBlueprintHdfsTestBundle))
>>
>> at org.junit.Assert.fail(Assert.java:93)
>> at
>> org.ops4j.pax.exam.junit.JUnit4TestRunner$3.evaluate(JUnit4TestRunner.java:293)
>>
>> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Hadrian Zbarcea <hz...@gmail.com>.
There are 3 outstanding issues for 2.10.0, 2 assigned to Willem and 1
unassigned.
Willem, what are your plans? The unassigned is not clear if it's a bug
or not. I'll plan to cut the release builds early next week then.
Cheers,
Hadrian
On 06/15/2012 04:48 AM, Claus Ibsen wrote:
> Hi
>
> Okay so I have fixed camel-rmi to use dynamic port numbers.
>
> I got 2 osgi failures on windows with java7
> 1) JpaBlueprintRouteTest
> 2) HdfsBlueprintRouteTest
>
>
> Ad 1)
> This fails due the old data from previous test is still around. A quick fix
> would be to change the test to use different entity, so its different
> tables.
> Or figure out a way to get the **** jpa provider to drop/recreate the
> schema.
>
> 2012-06-15 10:22:51,593 | ERROR | )-192.168.93.128 | DefaultErrorHandler
> | 72 - org.apache.camel.camel-core - 2.10.0.SNAPSHOT | Failed
> delivery for (MessageId: ID-vomit-4934-1339748567031
> -0-3 on ExchangeId: ID-vomit-4934-1339748567031-0-2). Exhausted after
> delivery attempt: 1 caught:
> org.springframework.transaction.CannotCreateTransactionException: Could not
> open JPA EntityManager for
> transaction; nested exception is<openjpa-2.2.0-r422266:1244990 nonfatal
> general error> org.apache.openjpa.persistence.PersistenceException:
> Table/View 'SENDEMAIL' already exists in Schema 'APP'. {st
> mnt 17844447 CREATE TABLE SENDEMAIL (id BIGINT NOT NULL, address
> VARCHAR(255), PRIMARY KEY (id))} [code=30000, state=X0Y32]
> org.springframework.transaction.CannotCreateTransactionException: Could not
> open JPA EntityManager for transaction; nested exception is
> <openjpa-2.2.0-r422266:1244990 nonfatal general error> org.apach
> e.openjpa.persistence.PersistenceException: Table/View 'SENDEMAIL' already
> exists in Schema 'APP'. {stmnt 17844447 CREATE TABLE SENDEMAIL (id BIGINT
> NOT NULL, address VARCHAR(255), PRIMARY KEY (id))}
> [code=30000, state=X0Y32]
> at
> org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:382)[115:org.springframework.orm:3.0.7.RELEASE]
> at
> org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)[79:org.springframework.transaction:3.0.7.RELEASE]
> at
> org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127)[79:org.springframework.transaction:3.0.7.RELEASE]
> at
> org.apache.camel.component.jpa.JpaTemplateTransactionStrategy.execute(JpaTemplateTransactionStrategy.java:78)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
> at
> org.apache.camel.component.jpa.JpaProducer.process(JpaProducer.java:50)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
> at
> org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[72:org.apache.camel.camel-core:2.10.0.SNAPSHOT]
>
>
>
> Ad 2)
>
> I guess maybe its something with the camel-hdfs feature. I could not find
> much in the logs.
>
> -------------------------------------------------------------------------------
> Test set: org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 91.875 sec
> <<< FAILURE!
> testWriteAndReadString:HdfsBlueprintRouteTest.testWriteAndReadString:KarafTestContainer{mvn:org.apache.karaf/apache-karaf/2.2.7/tar.gz}(org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest)
> Time elapsed: 20.719 sec<<< FAILURE!
> java.lang.AssertionError: Gave up waiting for service
> (&(objectClass=org.apache.camel.CamelContext)(camel.context.symbolicname=CamelBlueprintHdfsTestBundle))
> at org.junit.Assert.fail(Assert.java:93)
> at
> org.ops4j.pax.exam.junit.JUnit4TestRunner$3.evaluate(JUnit4TestRunner.java:293)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
>
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Okay so I have fixed camel-rmi to use dynamic port numbers.
I got 2 osgi failures on windows with java7
1) JpaBlueprintRouteTest
2) HdfsBlueprintRouteTest
Ad 1)
This fails due the old data from previous test is still around. A quick fix
would be to change the test to use different entity, so its different
tables.
Or figure out a way to get the **** jpa provider to drop/recreate the
schema.
2012-06-15 10:22:51,593 | ERROR | )-192.168.93.128 | DefaultErrorHandler
| 72 - org.apache.camel.camel-core - 2.10.0.SNAPSHOT | Failed
delivery for (MessageId: ID-vomit-4934-1339748567031
-0-3 on ExchangeId: ID-vomit-4934-1339748567031-0-2). Exhausted after
delivery attempt: 1 caught:
org.springframework.transaction.CannotCreateTransactionException: Could not
open JPA EntityManager for
transaction; nested exception is <openjpa-2.2.0-r422266:1244990 nonfatal
general error> org.apache.openjpa.persistence.PersistenceException:
Table/View 'SENDEMAIL' already exists in Schema 'APP'. {st
mnt 17844447 CREATE TABLE SENDEMAIL (id BIGINT NOT NULL, address
VARCHAR(255), PRIMARY KEY (id))} [code=30000, state=X0Y32]
org.springframework.transaction.CannotCreateTransactionException: Could not
open JPA EntityManager for transaction; nested exception is
<openjpa-2.2.0-r422266:1244990 nonfatal general error> org.apach
e.openjpa.persistence.PersistenceException: Table/View 'SENDEMAIL' already
exists in Schema 'APP'. {stmnt 17844447 CREATE TABLE SENDEMAIL (id BIGINT
NOT NULL, address VARCHAR(255), PRIMARY KEY (id))}
[code=30000, state=X0Y32]
at
org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:382)[115:org.springframework.orm:3.0.7.RELEASE]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:371)[79:org.springframework.transaction:3.0.7.RELEASE]
at
org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:127)[79:org.springframework.transaction:3.0.7.RELEASE]
at
org.apache.camel.component.jpa.JpaTemplateTransactionStrategy.execute(JpaTemplateTransactionStrategy.java:78)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
at
org.apache.camel.component.jpa.JpaProducer.process(JpaProducer.java:50)[126:org.apache.camel.camel-jpa:2.10.0.SNAPSHOT]
at
org.apache.camel.util.AsyncProcessorConverterHelper$ProcessorToAsyncProcessorBridge.process(AsyncProcessorConverterHelper.java:61)[72:org.apache.camel.camel-core:2.10.0.SNAPSHOT]
Ad 2)
I guess maybe its something with the camel-hdfs feature. I could not find
much in the logs.
-------------------------------------------------------------------------------
Test set: org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest
-------------------------------------------------------------------------------
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 91.875 sec
<<< FAILURE!
testWriteAndReadString:HdfsBlueprintRouteTest.testWriteAndReadString:KarafTestContainer{mvn:org.apache.karaf/apache-karaf/2.2.7/tar.gz}(org.apache.camel.itest.osgi.hdfs.HdfsBlueprintRouteTest)
Time elapsed: 20.719 sec <<< FAILURE!
java.lang.AssertionError: Gave up waiting for service
(&(objectClass=org.apache.camel.CamelContext)(camel.context.symbolicname=CamelBlueprintHdfsTestBundle))
at org.junit.Assert.fail(Assert.java:93)
at
org.ops4j.pax.exam.junit.JUnit4TestRunner$3.evaluate(JUnit4TestRunner.java:293)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
The 2.10 starts to look good, and the tests are all green (occasionally 1
weird failure from time to time) now on the CI servers.
eg the camel-rmi component do not use dynamic port numbers so the Spring
3.1 project failed with port number in use.
But overall the testing seems really good.
I am running Windows testing on my XP box, and so all the components are
100% passed on Java 7.
Its currently working its way with the OSGi tests.
I think we should start shape this into cutting a RC for the 2.10.
Anyone got any last minute stuff they want in this release.
Then its time to speak up.
And as usually we love feedback, and if you plan to upgrade to Camel 2.10.
Then give the current codebase a test spin.
Then we can do any corrections *before* the release.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
The CXF osgi tests fails. Could be the 2.6.1 upgrade or whatnot.
I have logged a ticket.
https://issues.apache.org/jira/browse/CAMEL-5362
On Tue, Jun 12, 2012 at 1:16 PM, Claus Ibsen <cl...@gmail.com> wrote:
> Hi
>
> The SMX team have released the latest batch of bundle upgrades.
> So I have committed pom.xml changes to upgrade in Camel as well.
>
> So the OSGi features should be okay now, and ready for testing.
>
>
>
> --
> Claus Ibsen
> -----------------
>
> FuseSource
> Email: cibsen@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.com
>
> Author of Camel in Action: http://www.manning.com/ibsen
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks for that Claus,
I'm going to run some tests.
Regards
JB
On 06/12/2012 01:16 PM, Claus Ibsen wrote:
> Hi
>
> The SMX team have released the latest batch of bundle upgrades.
> So I have committed pom.xml changes to upgrade in Camel as well.
>
> So the OSGi features should be okay now, and ready for testing.
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] - Apache Camel 2.10 release
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
The SMX team have released the latest batch of bundle upgrades.
So I have committed pom.xml changes to upgrade in Camel as well.
So the OSGi features should be okay now, and ready for testing.
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen