Benjamin Bentmann a écrit :
dugueperoux.este...@free.fr wrote:

My modules pom.xml

<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
   <modelVersion>4.0.0</modelVersion>

   <groupId>com.miasoftware</groupId>
   <artifactId>com.miasoftware.miastudio.model</artifactId>
   <packaging>zip</packaging>
   [...]
</project>


<project xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
   <modelVersion>4.0.0</modelVersion>

   <groupId>com.miasoftware</groupId>
   <artifactId>com.miasoftware.miastudio.model.edit</artifactId>
   <packaging>zip</packaging>
   [...]

<dependencies>
   <dependency>
     <groupId>com.miasoftware</groupId>
     <artifactId>com.miasoftware.miastudio.model</artifactId>
     <version>1.0-SNAPSHOT</version>
   </dependency>
 </dependencies>
</project>

Try adding
  <type>zip</type>
to your dependency to have it match your <packaging>. If omitted, the type defaults to "jar" but as you already noted, your modules produce ZIPs and not JARs.

See [0] and [1] for some background on project packaging and artifact type.


Benjamin


[0] http://maven.apache.org/pom.html#Maven_Coordinates
[1] http://maven.apache.org/pom.html#Dependencies

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Hi Benjamin,

In fact I have done a mistake, I tried to manage my plugins dependencies with maven while eclipse plugins dependencies are managed by MANIFEST.MF like that pde-maven-plugin is just a proxy to pde build. Now it works with a "mvn package" on feature pom.xml. But pde-maven-plugin doesn't seem work on Linux, I tried tutorial example from http://snapshots.repository.codehaus.org/org/codehaus/mojo/pde-maven-plugin/ .
It works on Windows but not on Linux
, I received a BUILD ERROR with exit code to 13
with -e switch I have the following stack trace :

org.apache.maven.lifecycle.LifecycleExecutionException: Error executing command line. Exit code:13 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
       at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
       at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
       at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
       at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error executing command line. Exit code:13 at org.codehaus.mojo.pde.AbstractEclipsePDEMojo.executeCommandLine(AbstractEclipsePDEMojo.java:228) at org.codehaus.mojo.pde.EclipsePDEMojo.execute(EclipsePDEMojo.java:99) at org.codehaus.mojo.pde.EclipsePDEExtMojo.execute(EclipsePDEExtMojo.java:48) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
       ... 16 more

I have see this report bug http://jira.codehaus.org/browse/MOJO-827
but this happens only on Linux not on Windows and my target directory contains only pdeBuilder/build.xml not log.

Are there people who have already tested this maven plugin on Linux ?

Best Regards.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to