maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard van der Hoff (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MASSEMBLY-162) In a multiproject environment, assembly takes wrong dependencies
Date Mon, 26 Mar 2007 18:39:34 GMT

    [ http://jira.codehaus.org/browse/MASSEMBLY-162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91068
] 

Richard van der Hoff commented on MASSEMBLY-162:
------------------------------------------------

Sounds like the original issue has been resolved, but replaced with MASSEMBLY-179.

could it be marked as such?


> In a multiproject environment, assembly takes wrong dependencies
> ----------------------------------------------------------------
>
>                 Key: MASSEMBLY-162
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-162
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: M. van Leeuwen
>            Priority: Critical
>             Fix For: 2.2
>
>
> With a projectstructure like 'Project/{ejb,war,ear,client}' packaging the client as a
fat jar-with-dependencies, it works fine using the following configuration.
> === etc/fatjar.xml ====
> <id>fat</id>
>   <formats><format>jar</format></formats>
>   <includeBaseDirectory>false</includeBaseDirectory>
>   <fileSets><fileSet>
>       <directory>target/classes</directory>
>       <outputDirectory>/</outputDirectory>
>     </fileSet></fileSets>
>   <dependencySets>
>     <dependencySet>
>       <outputDirectory>/</outputDirectory>
>       <unpack>true</unpack>
>       <scope>runtime</scope>
>     </dependencySet>
>   </dependencySets>
> </assembly>
> === pom.xml ===
> <?xml version="1.0"?><project>
>   <version>0.3-SNAPSHOT</version>
>   <modelVersion>4.0.0</modelVersion>
>   <groupId>mygroup</groupId>
>   <artifactId>myapp-client</artifactId>
>   <name>My Application</name>
>   <dependencies>
> <!-- stripped -->
>   </dependencies>
>     <build>
>         <plugins>
>             <plugin>
>                 <artifactId>maven-assembly-plugin</artifactId>
>                 <version>2.1</version>
>                 <configuration>
>                     <descriptors><descriptor>etc/fatjar.xml</descriptor></descriptors>
>                     <archive>
>                         <manifest><mainClass>path.to.MainClass</mainClass><manifest>
>                     </archive>
>                 </configuration>
>                 <executions><execution>
>                     <phase>package</phase>
>                     <goals><goal>assembly</goal></goals>
>                   </execution></executions>
>             </plugin>
>         </plugins>
>     </build>
> </project>
> But when I'm on the level above (packaging all) it just assembles all underlying dependencies
into my clientjar, and not the dependencies of the childproject.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message