For the record, it seems that the issue i encountered is the same as
http://jira.codehaus.org/browse/MASSEMBLY-190

Luc

On Mon, Jun 23, 2008 at 3:14 PM, Bengali Bengali <[EMAIL PROTECTED]>
wrote:

> Hi,
>
> I started another thread from my previous one since my issue seems to be
> tied to the maven assembly plugin
> (Maven 2.0.8, assembly 2.1).
>
> I have a multimodule project and  one assembly that is executed in 1
> project messes up dependencies on another.
> (When i disable assembly plugin execution i don't have that behaviour).
>
> I really need help on this:
>
> I ran a mvn dependency:tree from my parent and here's the output for the
> dependencies of my child project:
>
> [INFO] [dependency:tree]
> [INFO] biz.dewavrin.seamphony.sip-os
> :SIP-OS-ESB-CRM2BACKEND:esb:1.0.00-SNAPSHOT
> [INFO] +- junit:junit:jar:4.3.1:test
> [INFO] +- javax.mail:mail:jar:1.4:test
> [INFO] +-
> biz.dewavrin.seamphony.sip-gs:SIP-GS-WAR-WS:jar:wsclient:1.0.00-SNAPSHOT:compil
> e
>
> When i ran my build from my parent i get other dependencies transitively
> (here SIP-GS-JAR-CORE) and it shouldn't happen:
> [DEBUG]
> biz.dewavrin.seamphony.sip-gs:SIP-GS-WAR-WS:jar:wsclient:1.0.00-SNAPSHOT:compile
> (selected for compile)
> [DEBUG]
> biz.dewavrin.seamphony.sip-gs:SIP-GS-JAR-CORE:jar:1.0.00-SNAPSHOT:compile
> (selected for compile)
>
> I don't understand since the SIP-GS-JAR-CORE dependency  has been
> explicitely excluded from my child pom
> (and not defined in the parent):
>
>         <dependency>
>           <groupId>biz.dewavrin.seamphony.sip-gs</groupId>
>           <artifactId>SIP-GS-WAR-WS</artifactId>
>           <version>${version}</version>
>           <classifier>wsclient</classifier>
>           <exclusions>
>             <exclusion>
>                <groupId>biz.dewavrin.seamphony.sip-gs</groupId>
>                <artifactId>SIP-GS-JAR-CORE</artifactId>
>             </exclusion>
>           </exclusions>
>         </dependency>
>
> The SIP-GS-JAR-CORE dependency is packaged in my child artifact but it
> shouldn't since it has been excluded.
>
> This behaviour occurs only when i execute the assembly plugin in the
> SIP-GS-WAR-WS project and i suspect
> it to alter the dependencies of my project.
>
> The assembly plugin is bound to the package phase in the SIP-GS-WAR-WS
> project and the single goal is executed :
>           <plugin>
>                 <artifactId>maven-assembly-plugin</artifactId>
>                 <version>2.1</version>
>                 <executions>
>                   <execution>
>                     <id>make-assembly</id>
>                     <phase>package</phase>
>                     <goals>
>                       <goal>single</goal>
>                     </goals>
>                   </execution>
>                 </executions>
>                 <inherited>false</inherited>
>                 <configuration>
>                   <descriptors>
>                     <descriptor>src/main/assembly/assembly.xml</descriptor>
>                   </descriptors>
>                 </configuration>
>            </plugin>
>
> Thanks in advance,
> Luc
>
>

Reply via email to