The Apache Jenkins build system has built Camel.trunk.notest (build #1998)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1998/
to view the results.
Hi,
The wrap bundle doesn't work as you want.
You can need to apply the customer OSGi meta inform to control the import and
export packages yourself to workaround the issue.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blo
The Apache Jenkins build system has built Camel.2.12.x.notest (build #28)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.2.12.x.notest/28/
to view the results.
Some more progress, ...
Current feature config:
camel
wrap:mvn:javax.mail/mail/1.4
wrap:mvn:javax.servlet/servlet-api/2.4
wrap:mvn:commons-codec/commons-codec/1.3
wrap:mvn:jdom/jdom/1.0
wrap:mvn:javax.servlet/jsp-api/2.0
wrap:mvn:commons-jxpath/commons-jxp
May be add
wrap:mvn:com.mysema.querydsl/querydsl-annotations/0.2.8
Hope this helps...
Best,
Christian
-
Software Integration Specialist
Apache Camel committer: https://camel.apache.org/team
V.P. Apache Camel: https://www.apache.org/foundation/
Apache Member: https://www.apache.o
Dear all,
I also made some progress, but it seems that there is still something missing.
The feature config looks now like:
camel
mvn:org.springframework/spring-expression/3.1.4.RELEASE
mvn:org.springframework/spring-asm/3.1.4.RELEASE
mvn:org.springframework/spring-co
The Camel community announces the immediate availability of the new patch
release Camel 2.11.2. This bug fix release is issued after 2 month of
intense efforts of the Camel 2.11.x maintenance branch and resolves 120
issues in total.
The artifacts are published and ready for you to download [1] eit
GitHub user mzapletal opened a pull request:
https://github.com/apache/camel/pull/45
CAMEL-5771 IOHelper.getCharsetName() should lookup CHARSET_NAME in heade...
...rs if exchange property is not set
You can merge this pull request into a Git repository by running:
$ git pull ht
Yes, this was exactly what I encountered. I just had the feeling, that I might
not want to include all those dependencies to get the component started.
Of course, upgrading might help. As far as I've seen, there are already some
changes towards proper OSGi bundle build in some new dependency ver
