Hello Claus! See my comments inline.
Best, Christian On Sat, Apr 20, 2013 at 12:08 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > iBatis is a dead project, so people should favor using MyBatis. > > When you install features camel (eg just camel) then it will install > camel-spring and camel-blueprint AFAIR. > So when you later install other features then spring should be there > already. > That's right. But should we expect, the user already installed the camel or camel-spring or camel-blueprint feature? Shouldn't we simply add this dependency into the feature? > > But I guess iBatis requires javax TX, and thus some bundle for that is > being installed as part of camel-spring / spring. eg spring-tx. So > when that is already installed, then you wont have that problem. > > > On Sat, Apr 20, 2013 at 12:00 PM, Christian Müller > <christian.muel...@gmail.com> wrote: > > +0 > > > > I upgraded the Camel in Action source code (and some of my projects). I > > only had the following issue: > > camelinaction.ScalabilityTest failed. I think this is a regression > > > > I also test the examples which failed with the last RC successful. > > > > I checked that the camel-jclouds feature could be installed. > > > > When I install camel-ibatis, I get the following error: > > karaf@root> features:install camel-ibatis > > Error executing command: Could not start bundle > > > mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-dbcp/1.4_3 > > in feature(s) camel-quartz-2.11.0, camel-jpa-2.11.0, > camel-mybatis-2.11.0, > > camel-ibatis-2.11.0, camel-bam-2.11.0: Unresolved constraint in bundle > > org.apache.servicemix.bundles.commons-dbcp [64]: Unable to resolve 64.0: > > missing requirement [64.0] osgi.wiring.package; > > (osgi.wiring.package=javax.transaction) > > > > Installing camel-spring before resolves the error. > > > > Best, > > Christian > > > > > > On Wed, Apr 17, 2013 at 10:11 PM, Christian Müller < > > christian.muel...@gmail.com> wrote: > > > >> After 9 month of development, we have a new minor release candidate > >> apache-camel-2.11.0 ready. > >> It comes with 679 issues resolved: new features, improvements and bug > >> fixes [1]. You can find the release notes here [2]. > >> > >> Please find the staging repo here: > >> https://repository.apache.org/content/repositories/orgapachecamel-112/ > >> > >> The tarballs are here > >> > >> > https://repository.apache.org/content/repositories/orgapachecamel-112/org/apache/camel/apache-camel/2.11.0/ > >> > >> Tag: > >> http://svn.apache.org/repos/asf/camel/tags/camel-2.11.0/ > >> > >> Please review, help out with testing and vote to approve this release > >> binary. Please mention what you tested to prevent duplicate work. Your > vote > >> counts! > >> > >> [ ] +1 Release the binary as Apache Camel 2.11.0 > >> [ ] -1 Veto the release (provide specific comments) > >> Vote is open for at least 72 hours. > >> > >> Thanks in advance, > >> Christian > >> > >> [1] > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CAMEL%20AND%20fixVersion%20%3D%20%222.11.0%22 > >> [2] > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12321695 > >> > > > > -- > Claus Ibsen > ----------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen >
