You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by rocket <ni...@gmail.com> on 2014/02/07 13:26:43 UTC
Karaf & Jenkins
Sorry for this double post
(http://karaf.922171.n3.nabble.com/Jenkins-and-Karaf-3-0-0-td4031506.html)
but there seem to be no action else but here?
Currently we're using both native container and in parallel Karaf 2.3.2 with
pax exam 3.4 to run our tests and it works fine.
But when I try to bump the Karaf version to 3.0.0, tests start to fail and
the reason is "Caused by: org.ops4j.pax.exam.TestContainerException:
java.lang.NoClassDefFoundError:"/"Caused by:
java.lang.ClassNotFoundException"(even though we can see that the class
exist in the bundle/jar).
The test cases run fine in both terminal and in eclipse when we're using the
same setup with Karaf 3.0.0 so the problem only exist on Jenkins.
I did as they did in https://ops4j1.jira.com/browse/PAXEXAM-543 and that
solved some initial issues with Karaf 3.0.0, before that Karaf didn't find
any artefacts.
The bundle Karaf/Jenkins can't find is a local/project bundle and not a 3pp.
I thought that it maybe had something to do with our manual setting of
repo.local etc on Jenkins so I ran with "mvn clean install
-Dmaven.repo.local=.repo -Dorg.ops4j.pax.url.mvn.localRepository=.repo
-Djava.io.tmpdir=.tmp" but still all the test run green in terminal
So what am I missing?
Regards,
--
View this message in context: http://karaf.922171.n3.nabble.com/Karaf-Jenkins-tp4031573.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Karaf & Jenkins
Posted by Achim Nierbeck <bc...@googlemail.com>.
hmm, this is rather strange then.
Might be a bug, could you open an issue for it at the Pax Exam Jira with a
working sample for reproduction?
regards, Achim
2014-02-12 12:45 GMT+01:00 rocket <ni...@gmail.com>:
> "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."
>
> depends-maven-plugin and curator-client was in the POM all the time the
> only
> thing i added was the .version(2.3.0) i dont know if its a bug or a feature
> but it did work without .version(2.3.0) in karaf 2.3.2 and native
> container.
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Karaf-Jenkins-tp4031573p4031636.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/>
Re: Karaf & Jenkins
Posted by rocket <ni...@gmail.com>.
"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."
depends-maven-plugin and curator-client was in the POM all the time the only
thing i added was the .version(2.3.0) i dont know if its a bug or a feature
but it did work without .version(2.3.0) in karaf 2.3.2 and native container.
--
View this message in context: http://karaf.922171.n3.nabble.com/Karaf-Jenkins-tp4031573p4031636.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Karaf & Jenkins
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi,
see my comments inline.
regards, Achim
2014-02-12 12:27 GMT+01:00 rocket <ni...@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/>
Re: Karaf & Jenkins
Posted by rocket <ni...@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"),
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
--
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.