[
https://issues.apache.org/jira/browse/CAMEL-3773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004975#comment-13004975
]
Claus Ibsen commented on CAMEL-3773:
------------------------------------
Btw there is a FAQ about the uber JAR issue
http://camel.apache.org/why-do-camel-throw-so-many-noclassdeffoundexception-on-startup.html
> Apache Camel version banner is wrong in uber-jar
> ------------------------------------------------
>
> Key: CAMEL-3773
> URL: https://issues.apache.org/jira/browse/CAMEL-3773
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.6.0
> Reporter: Arkadi Shishlov
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.8.0
>
>
> At context start a version banner is printed to the log:
> Apache Camel 2.6.0 (CamelContext: camel) started in 2.436 seconds
> The version string is calculated by ServiceSupport.getVersion():
> Package aPackage = getClass().getPackage();
> if (aPackage != null) {
> version = aPackage.getImplementationVersion();
> if (version == null) {
> version = aPackage.getSpecificationVersion();
> }
> }
> but, in Maven shade-plugin packaged project (to create single uber-jar for
> distribution to SE environment), the Manifest versions are project version,
> not Camel. So the wrong version is printed. It would be nice to have this
> improved to print real Camel version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
