Re: Integration Test: Dependency problem

2015-03-27 Thread Christian Eugster
After moving the dependencies to the parent pom and add them in the itest pom without version tag, I get in the itest pom following error for the following three depeondencies: org.apache.camel.karaf apache-camel

Re: Integration Test: Dependency problem

2015-03-27 Thread Stuart McCulloch
type is not quite the same as packaging - packaging defines the lifecycle used to build the project (what plugins get called for each phase) whereas type is more about the final artifact and defines the extension amongst other things. The bundle lifecycle does define a type called 'bundle' with an

Re: Integration Test: Dependency problem

2015-03-27 Thread Christian Eugster
So I can remove the type tag from dependencies. Is then tag type only used once, when introducing a new artifact in tag packaging? Regards Christian Christian Eugster Grissian 14 I-39010 Tisens I: +39 0473 420 873 CH: +41 79 107 92 27 christian.eugs...@gmx.net > Am 27.03.2015 um 17:50 schri

Re: Integration Test: Dependency problem

2015-03-27 Thread Stuart McCulloch
I see you're declaring dependencies with bundle whereas you should just leave them with the default type (jar). While the packaging type is "bundle" (to activate the different packaging lifecycle) the artifacts produced are declared as type jar and can be referenced as dependencies with the default

Re: Integration Test: Dependency problem

2015-03-27 Thread Christian Eugster
I changed the type of the bundles to jar. It does not help. Regards Christian Christian Eugster Grissian 14 I-39010 Tisens I: +39 0473 420 873 CH: +41 79 107 92 27 christian.eugs...@gmx.net > Am 27.03.2015 um 17:35 schrieb Christian Eugster : > > Hi, > > but as I understand, the bundles h

Re: Integration Test: Dependency problem

2015-03-27 Thread Christian Eugster
Hi, but as I understand, the bundles have - as the normal jars - the extension jar, the unique difference are some extra entries in the MANIFEST.MF file. Is that wrong? I added the frequently used dependencies to the parents pom as managed dependencies and added those required for itest in th

Re: Integration Test: Dependency problem

2015-03-27 Thread Stuart McCulloch
The log shows that it’s looking for artifacts with an extension of ‘bundle’, whereas the bundle packaging type actually produces artifacts with an extension of ‘jar’ - this suggests that the bundle lifecycle extension has not been installed for the itest project. What does the sip-detection pom

Integration Test: Dependency problem

2015-03-27 Thread Christian Eugster
Hi, I am quite new to maven and I have the following problem: I have a project with several modules (api and impl) and one of them is an integration test module, that contains only a test class. The pom of this module references (as I see) all dependencies. When I run the parents pom all modul