1) Working directory
Is there a way to change the working directory for the plugin? I've tried
<param>--workingDirectory=${basedir}/target/runner</param>
but now I have two directories "target/runner" used by Pax Runner and
"runner" used by maven-pax-plugin.
2) Conflicts with Tycho
I'm using Tycho to build OSGi bundles with Maven packaging type
eclipse-plugin.
I tried adding the maven-pax-plugin to an eclipse-plugin POM like this:
<plugin>
<groupId>org.ops4j</groupId>
<artifactId>maven-pax-plugin</artifactId>
<configuration>
<noDependencies>true</noDependencies>
<deployURLs>
<!-- lots of mvn: URLs -->
</deployURLs>
<provision>
<param>--platform=equinox</param>
</provision>
</configuration>
</plugin>
which results in an error message
org.ops4j.pax.runner.platform.PlatformException:
[mvn:com.googlecode.osgi-enterprise/com.googlecode.osgienterprise.blog.wicket/0.0.1-SNAPSHOT/eclipse-plugin]
could not be downloaded
This seems to be caused by the following section in
runner/deploy-pom.xml generated by the pax-maven-plugin:
<dependencies>
<dependency>
<groupId>com.googlecode.osgi-enterprise</groupId>
<artifactId>com.googlecode.osgienterprise.blog.wicket</artifactId>
<version>0.0.1-SNAPSHOT</version>
<type>eclipse-plugin</type>
<scope>provided</scope>
</dependency>
</dependencies>
eclipse-plugin is just a packaging (like "bundle"), but not a type (like
"test-jar").
See
http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_dependency
As a workaround, I moved my maven-pax-plugin configuration to a separate
POM-only project.
Best regards,
Harald
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
