That is the main issue… There is no packaging type called sar so I've left it
as the default (jar).
What is happening is that in the target folder of the project the file is named
with .sar extension while it is being renamed to .jar in the repository.
Yoram
From: Kevin Stembridge [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 09, 2007 12:13 PM
To: [email protected]
Subject: Re: [mojo-user] jboss-packaging-maven-plugin repository
Hi,
What is the packaging type of your sar project? I can't see it in the pom.xml
fragments you've shown so I'm guessing it is the default, jar.
What happens if you try <packaging>jboss-sar</packaging> ?
On Sun, 2007-12-09 at 08:04 +0200, Yoram Michaeli wrote:
Hi,
I’m using jboss-packaging-maven-plugin to create a SAR and it works fine for
me, but only the created JAR file is deployed in the repository so I can’t use
the SAR to be included in my EAR project.
How can I force it to deploy my SAR into the repository?
Below is the relevant code:
--- SAR pom.xml ---
<groupId>com.test</groupId>
<artifactId>mySar</artifactId>
<name>mySar</name>
…
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jboss-packaging-maven-plugin</artifactId>
<version>2.0-SNAPSHOT</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>sar</goal>
</goals>
<configuration>
<jbossServiceFile>src/conf/jboss-service.xml</jbossServiceFile>
<excludes>
<exclude>jboss:jboss-system</exclude>
<exclude>jboss:jboss-jmx</exclude>
<exclude>jboss:jboss-common</exclude>
</excludes>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
--- EAR pom.xml ---
<modules>
<sarModule>
<groupId>com.test</groupId>
<artifactId>mySar</artifactId>
</sarModule>
…
<dependency>
<groupId> com.test </groupId>
<artifactId> mySar </artifactId>
<version>1.0-SNAPSHOT<version>
<type>sar</type>
</dependency>
--------------------
Thanks,
Yoram