[DISCUSS] - Apache Camel 2.10 release
Locked
123
123
Re: [DISCUSS] - Apache Camel 2.10 release
 
|
+1, would be less confusing.
On Jun 2, 2012, at 12:18 PM, David Karlsen wrote: > +1 to that. > > 2012/6/2 Daniel Kulp <[hidden email]>: >> 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 <[hidden email]> 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 >>>> [hidden email] >>>> http://dankulp.com/blog >> -- >> Daniel Kulp >> [hidden email] - 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
|
In reply to this post by Claus Ibsen-2
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
|
Re: [DISCUSS] - Apache Camel 2.10 release
|
On Sat, Jun 2, 2012 at 10:17 PM, Babak Vahdat
<[hidden email]> 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: [hidden email] 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
|
|
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 |
Re: [DISCUSS] - Apache Camel 2.10 release
|
|
On Sun, Jun 3, 2012 at 10:52 AM, Babak Vahdat
<[hidden email]> 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: [hidden email] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen |
|
In reply to this post by Johan Edstrom-2
+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<[hidden email]>: >>> 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<[hidden email]> 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 >>>>> [hidden email] >>>>> http://dankulp.com/blog >>> -- >>> Daniel Kulp >>> [hidden email] - http://dankulp.com/blog >>> Talend Community Coder - http://coders.talend.com >>> >> >> >> >> -- >> -- >> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen > |
|
|
In reply to this post by Claus Ibsen-2
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<[hidden email]> 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 >> [hidden email] >> http://dankulp.com/blog >> > > > |
Re: [DISCUSS] - Apache Camel 2.10 release
|
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 <[hidden email]> 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<[hidden email]> 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 >>> [hidden email] >>> http://dankulp.com/blog >>> >>> >> >> >> |
Re: [DISCUSS] - Apache Camel 2.10 release
|
|
In reply to this post by dkulp@apache.org
On Sat, Jun 2, 2012 at 6:04 PM, Daniel Kulp <[hidden email]> 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 <[hidden email]> 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 >> > [hidden email] >> > http://dankulp.com/blog > -- > Daniel Kulp > [hidden email] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com > -- Claus Ibsen ----------------- FuseSource Email: [hidden email] 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
|
|
In reply to this post by Charles Moulliard
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
|
Re: [DISCUSS] - Apache Camel 2.10 release
|
|
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: [hidden email] 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
|
|
On Tue, Jun 5, 2012 at 5:36 PM, Claus Ibsen <[hidden email]> 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: [hidden email] > 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: [hidden email] 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
|
|
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
|
|
|
In reply to this post by Claus Ibsen-2
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
|
|
In reply to this post by Claus Ibsen-2
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
|
Re: [DISCUSS] - Apache Camel 2.10 release
|
|
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 <[hidden email]>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
|
|
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
|
Re: [DISCUSS] - Apache Camel 2.10 release
|
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 [hidden email] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com |
Re: [DISCUSS] - Apache Camel 2.10 release
|
|
In reply to this post by Claus Ibsen-2
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: [hidden email] 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
|
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 <[hidden email]> 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: [hidden email] > Web: http://fusesource.com > Twitter: davsclaus, fusenews > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen >
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Email: [hidden email] Twitter : @cmoulliard, @fusenews Blog : http://cmoulliard.blogspot.com |
«
Return to Camel Development
|
1 view|%1 views
Loading...
| Powered by Nabble | Edit this page |