Hi,
see my comments inline.
regards, Achim
2014-02-12 12:27 GMT+01:00 rocket <nicholas.martens...@gmail.com>:
> I also saw this warning/error:
> 10:58:35,291 WARN [Start Level Event Dispatcher] Error when installing
> feature test-dependencies: java.io.IOException: Error resolving artifact
> org.apache.curator:curator-client:jar:LATEST
>
> when provisioning the bundles I changed
>
> mavenBundle().groupId("org.apache.curator").artifactId("curator-client"),
> to
>
>
> mavenBundle().groupId("org.apache.curator").artifactId("curator-client").version("2.3.0"),
>
if you didn't define this dependency in your POM and if you didn't run the
needed maven plugin
depends-maven-plugin it won't work.
> and voila all the tests run green on jenkins.
>
> next step is to understand why this bundle isnt active.
> 46 | Resolved | 20 | 1.0.0 | Apache Aries Blueprint
> Core
> Compatiblity Fragment Bundle, Hosts:4
>
>
A fragment bundle never is started/active since it's attached to it's host
bundle, at this point it's bundle 4
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Karaf-Jenkins-tp4031573p4031634.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
Commiter & Project Lead
blog <http://notizblog.nierbeck.de/>
