[
https://issues.apache.org/jira/browse/CAMEL-4398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13094501#comment-13094501
]
Claus Ibsen commented on CAMEL-4398:
------------------------------------
Sorry the issue is the tools JAR is added as dep on the SNAPSHOTs, but not on
the releases etc. So its a bit weird. Track down to be possible in
parent/pom.xml with some antrun tasks that does some osgi versioning regex
replacement.
And since this dependency is added to camel-core it gets inheirted by all the
other artifcats. But only for SNAPSHOTs, and not releases. So I guess the
release profile makes something different.
The tools JAR is thus not needed at all as a dependency to use Camel, so what
we want is to get rid of tools JAR in the camel-core/pom.xml file.
> Add profile to camel-core pom.xml to have tools.jar added as dependency which
> is needed for CI servers
> ------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4398
> URL: https://issues.apache.org/jira/browse/CAMEL-4398
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.9.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Jenkins-dependency-in-camel-core-pom-xml-for-SNAPSHOTs-tp4749494p4749494.html
> Jenkins will by default insert dependency if missing in published pom.xml,
> which have hardcoded link path to jenkins server.
> Instead we need to add a profile which is based on java.home path.
> See the links from the nabble talk above.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
