I'm afraid your question is about a deprecated feature...
The maven-paxexam-plugin is no longer supported in Pax Exam 2.0.0 and higher, and Pax Exam 1.x has reached end-of-life.
As an alternative, you can use org.apache.servicemix.tooling:depends-maven-plugin, see [1] for an example.
You can use MavenUrlReference.versionAsInProject() as a shortcut for .version(MavenUtils.asInProject()).
I must admit I've never tried this approach with a version range - I just hope the depends-maven-plugin does the right thing in this case.
[1] http://team.ops4j.org/wiki/display/paxexam/Pax+Exam+-+Tutorial+1. Hope that helps, Harald Am 25.05.2012 23:00, schrieb Rosenkoetter.Kent:
Hello, I am trying to use Pax Exam for our internal projects. We are using Maven to create OSGi bundles, and I want to use Pax Exam to test these bundles and verify they work. I set up a new Maven module that depends on one of our OSGi modules/bundles. The new module only houses integration tests. In the Foo-test module POM, I declare a dependency on the Foo module using a version range, [1.2.1-SNAPSHOT,1.3.0) so we don't need to modify the test module every time we revision the Foo module. This causes a problem where the goal org.ops4j.pax.exam:maven-paxexam-plugin:1.2.4:generate-config fails to find artifact com.mycompany.foo:com.mycompany.bar:jar:[1.2.1-SNAPSHOT,1.3.0) but the repository clearly has several artifacts within that version range. Maven itself is able to resolve the version range into a specific version, and the depends-maven-plugin:1.2:generate-depends-file also resolves down to one specific version. But maven-paxexam-plugin:1.2.4:generate-config fails. I suspect the problem is in the class org.ops4j.pax.exam.mavenplugin.GenerateConfigMojo, method writeProvisioning, line 230. The line is: VersionRange.createFromVersion(dependency.getVersion()) I believe changing this to: VersionRange.createFromVersionSpec(dependency.getVersion()) May fix my problem. The docs I found said Dependency.getVersion() can return a version range in Maven 2 and later, which is why I believe this fix is correct. How would I go about testing this short of downloading and building my own private copy of the plugin? -thanks, Kent, Double Down Interactive _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
