Not sure we have a Jenkins server ;)
Anyway, the dependencies can be pushed on the Jenkins server local repo
(we just have to avoid to remove the local repo on each build).
Regards
JB
On 10/06/2015 10:19 PM, Christian Müller wrote:
How do we "install" the dependency on the Jenkins CI server?
How do we "install" the dependency on the Jenkins CI server?
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/64
The component has to be built by the user, it doesn't ship the IBM MQ jar.
The dependencies specified in the pom have to be present in the user
local repo (installed using mvn install:install-file command).
So, the codebase is OK (it's already used in production), but the build
has to be done
And here is a third IBM one (the CICS component):
https://github.com/camel-extra/camel-extra/pull/10
Unsure how we should go about the library issue. We definitively cannot
upload it to central, but might set the scope to provided and so some
pre-build hack to download and install it for building:
Hi
Yeah it would be good to get camel-extra back on track. Hopefully at
the github home.
That said your components uses IBM. There was another talk for some
other camel-extra IBM component.
http://camel.465427.n5.nabble.com/Camel-WXS-component-tp5772096.html
I would like to know more about the i
