I guess you can't add the assembly plugin to a pom packaging project... I have to add the assembly-plugin to each of my modules I wanted to be assembled.
But I'm certainly interested in a better solution :) Denis. Damien Viel wrote: > > Thank for your help. > > I've tried your solution with a dedicated project for the build which > has dependencies on the binary assemblies. But my assembly still empty. > > Here is my new pom of the build-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>fr.toto.corp</groupId> > <artifactId>project-build</artifactId> > <packaging>pom</packaging> > <name>PROJECT-BUILD</name> > <version>${buildVersion}</version> > <url>${siteURL}</url> > > <build> > <sourceDirectory>${basedir}/src/java</sourceDirectory> > <testSourceDirectory>${basedir}/src/test</testSourceDirectory> > <plugins> > <plugin> > <artifactId>maven-assembly-plugin</artifactId> > <version>2.2-SNAPSHOT</version> > > </plugin> > </plugins> > </build> > > <dependencies> > > <dependency> > <groupId>fr.toto.corp</groupId> > <artifactId>mod1</artifactId> > <version>1.3</version> > </dependency> > <dependency> > <groupId>fr.toto.corp</groupId> > <artifactId>mod2</artifactId> > <version>1.0</version> > </dependency> > </dependencies> > > > </project> > > And I call the pre-defined Descriptor Files : jar-with-dependencies. > http://maven.apache.org/plugins/maven-assembly-plugin/predefined.html > > Damien > > > > Barrie Treloar a écrit : >> On 7/25/06, Damien Viel <[EMAIL PROTECTED]> wrote: >>> With the standard goals "jar-with-dependencies" it works fine on each >>> modules. But when I call the goal from the parent pom, the assembly is >>> empty. >> [del] >>> <assembly> >>> <id>jar-with-dependencies</id> >>> <formats> >>> <format>zip</format> >>> <format>dir</format> >>> </formats> >>> <includeBaseDirectory>false</includeBaseDirectory> >>> <fileSets> >>> <fileSet> >>> <directory>target/classes</directory> >>> <outputDirectory>/</outputDirectory> >>> </fileSet> >>> </fileSets> >>> <dependencySets> >>> <dependencySet> >>> <outputDirectory>/</outputDirectory> >>> <unpack>false</unpack> >>> <scope>runtime</scope> >>> </dependencySet> >>> </dependencySets> >>> </assembly> >> >> Your parent pom doesn't have any dependency hence it won't include >> anything. >> >> You will need to create your own assembly descriptor and make use of >> the moduleSets. >> I've never used the moduleSets myself. >> >> Our build includes a client side app, an ear, and a standalone >> application. So the way I build a distributable is to have another >> module called <project>-build which has dependencies on the binary >> assemblies of these other projects and to use dependencySet to pull >> them in. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > -- > -------------------------------------------------- > Damien Viel | +33 1 41 97 83 20 | [EMAIL PROTECTED] > -------------------------------------------------- > | http://www.improve-foundations.com > __/ \__ | http://www.improve.fr > improve | http://www.application-servers.com > /_____\-| http://www.improve-technologies.com > -------------------------------------------------- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/modules-and-assembly-problem-tf1997680.html#a5486737 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
