Re: Assembly plugin for multi module project

Fri, 24 Nov 2006 07:25:06 -0800 

Hi,

Thanks for the help. But I still have some problems.

I do not really understand the reason for the <project>-build module.
Do you use the module just for creating the assemblies?
I tried to invoke the assembly plugin from the top level directory.
The invokation should call all configured assemblies of the submodules.

Is this possible?

Thanks

Timo


On Nov 23, 2006, at 12:48 PM, Barrie Treloar wrote:


On 11/23/06, Paolo Bacci <[EMAIL PROTECTED]> wrote:

Nabble archives don't open here, returns timeout everytime.
Does it have protection from brazilian ips? If so, a proxy would help.
Barrie Treloar, could you send an example of your assembly descriptor? 

No Idea why Nabble is blocking you.
The link you want is:
http://www.nabble.com/forum/ViewPost.jtp? post=5936062&framed=y&skin=177 http://www.nabble.com/forum/ViewPost.jtp? post=5954911&framed=y&skin=177 


I have cut-n-paste the email here:
http://www.nabble.com/forum/ViewPost.jtp? post=5936062&framed=y&skin=177 

My project layout is:
ROOT/
- pom.xml
- module1
- moduleN
- <project>-build
 - pom.xml

In <project>-build/pom.xml I have:
   <dependencies>
       <dependency>
           <groupId>my.group</groupId>
           <artifactId>module1Artifact</artifactId>
           <version>1.0-SNAPSHOT</version>
           <type>zip</type>
       </dependency>
       <dependency>
           <groupId>my.group</groupId>
           <artifactId>module2Artifact</artifactId>
           <version>1.0-SNAPSHOT</version>
           <classifier>bin</classifier>
           <type>zip</type>
       </dependency>
       <dependency>
           <groupId>my.group</groupId>
           <artifactId>module3Artifact</artifactId>
           <version>1.0-SNAPSHOT</version>
           <classifier>bin</classifier>
           <type>zip</type>
       </dependency>
       <dependency>
           <groupId>my.group</groupId>
           <artifactId>module4Artifact</artifactId>
           <version>1.0-SNAPSHOT</version>
           <type>ear</type>
       </dependency>
   </dependencies>

So my main build collects 4 artifacts:
- a client side eclipse RCP (artifact1) as a zip
- 2 standalone applications (artifact2, artifact3) as binary builds
(these are the attached binary assemblies created when you install
artifact2 and artifact3)
- an ear file (artifact4)

My assembly in <project>-build/src/main/assembly/bin.xml:
<assembly>
   <id>bin</id>
   <formats>
<!-- There is a defect http://jira.codehaus.org/browse/ MASSEMBLY-119 
        that means dir format will attempt to attach this format into
the repository
        and will cause the build to fail.
       <format>dir</format>
       -->
       <format>zip</format>
   </formats>
   <includeBaseDirectory>true</includeBaseDirectory>
   <dependencySets>
       <dependencySet>
         <unpack>false</unpack>
         <outputFileNameMapping>
${artifactId}-${baseVersion}.${extension}</ outputFileNameMapping> 
         <excludes>
           <!--
           There is little documentation on this format.
It is of the form of DefaultArtifact.getDependencyConflictId() 
           which is <groupId>:<artifactId>:<type>:<classifier>
           or you can use the short form (hard coded into assembly) of
           <groupId>:<artifactId>
           This is a String equality match not a pattern match.
See Project Transitive Dependencies in site/ dependencies.html 
           for easy cut and paste values to put in here
           -->
           <exclude>commons-beanutils:commons-beanutils</exclude>
           <exclude>
commons-beanutils:commons-beanutils-bean-collections</ exclude> 
           <exclude>commons-beanutils:commons-beanutils-core</exclude>
           <exclude>commons-collections:commons-collections</exclude>
<exclude>commons-configuration:commons-configuration</ exclude> 
           <exclude>commons-digester:commons-digester</exclude>
           <exclude>commons-lang:commons-lang</exclude>
           <exclude>commons-logging:commons-logging</exclude>
           <exclude>easyconf:easyconf</exclude>
           <exclude>log4j:log4j</exclude>
           <exclude>weblogic:weblogic</exclude>
           <exclude>xstream:xstream</exclude>
         </excludes>
       </dependencySet>
   </dependencySets>
</assembly>

You need all those excludes because you dependency on the binary
artifact also depends upon the jars which get included even though
those same jars have already been included in the binary assembly.
http://www.nabble.com/forum/ViewPost.jtp? post=5954911&framed=y&skin=177 

Module 1 to Module N have assemblies like src/main/assembly/bin.xml
(which is building a binary distribution for an artifact say
my.group:mouldeA):

I have:

<assembly>
 <id>bin</id>
 <formats>
   <format>dir</format>
   <format>zip</format>
 </formats>
 <includeBaseDirectory>true</includeBaseDirectory>
 <fileSets>
   <fileSet>
     <directory>src/main/config</directory>
     <outputDirectory>config/</outputDirectory>
     <includes>
       <include>*</include>
     </includes>
   </fileSet>
   <fileSet>
     <directory>target</directory>
     <outputDirectory></outputDirectory>
     <includes>
       <include>${artifactId}-${version}.jar</include>
     </includes>
   </fileSet>
 </fileSets>
 <files>
   <file>
     <source>src/main/scripts/start_debug.bat</source>
     <filtered>false</filtered>
   </file>
   <file>
     <source>src/main/scripts/start.bat</source>
     <filtered>false</filtered>
   </file>
   <file>
     <source>src/main/scripts/stop.bat</source>
     <filtered>false</filtered>
   </file>
 </files>
 <dependencySets>
   <dependencySet>
     <outputDirectory>lib</outputDirectory>
     <unpack>false</unpack>
     <outputFileNameMapping>
${artifactId}-${baseVersion}.${extension}</ outputFileNameMapping> 
   </dependencySet>
 </dependencySets>
</assembly>


HTH

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to