Re: [m2][maven-dependency-plugin] unpack-dependencies issue

[Adrian Herscu]

Hi Brian,

Thanks for your suggestion!
I have changed the includeGroupIds clause to be more specific and now it 
builds correctly from the parent and this solved my problem.
However, there is still something wrong, because with the previous 
configuration, the child was successfully built when activated directly.

Adrian.

Brian E. Fox wrote:
Based on the fact that the [dependency:unpack-dependencies {execution:
default}]
Is showing up, the plugin is executing, it's possible that it isn't
finding anything to copy. Try removing the includes and excludes and let
it run with default behavior, you should see it copying all dependencies
of this project. You can then start narrowing it down.

-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: Tuesday, March 27, 2007 1:39 PM
To: users@maven.apache.org
Subject: Re: [m2][maven-dependency-plugin] unpack-dependencies issue

Hi Brian,

Here are the relevant POM sections (if you need the entire POMs, please
let me know):

The parent

   <modules>
    <module>samples</module>
    <module>lang</module>
   </modules>


1nd child -- samples

     <build>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-dependency-plugin</artifactId>
         <version>2.0-alpha-3</version>
         <executions>
           <execution>
             <phase>process-resources</phase>
             <goals>
               <goal>unpack-dependencies</goal>
             </goals>
             <configuration>
 
<outputDirectory>${project.build.outputDirectory}</outputDirectory>
             </configuration>
           </execution>
         </executions>
       </plugin>
       ...
     </build>


2nd child -- lang -- depends on the first child

     <build>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-dependency-plugin</artifactId>
         <version>2.0-alpha-3</version>
         <executions>
           <execution>
             <id>unpack-samples-and-decompiler</id>
             <phase>generate-test-resources</phase>
             <goals>
               <goal>unpack-dependencies</goal>
             </goals>
             <configuration>
 
<outputDirectory>${project.build.directory}/unpacked-dependencies</outpu
tDirectory>
               <includeScope>test</includeScope>
               <excludeTransitive>true</excludeTransitive>
               <includeGroupIds>org.wirexn</includeGroupIds>
             </configuration>
           </execution>
         </executions>
       </plugin>
       ...
     </build>

Thanks for your fast reply,
Adrian.

Brian E. Fox wrote:
Can you paste your config?

-----Original Message-----
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Adrian Herscu
Sent: Tuesday, March 27, 2007 8:14 AM
To: users@maven.apache.org
Subject: [m2][maven-dependency-plugin] unpack-dependencies issue

Hi all,

When running the maven-dependency-plugin in a multi-project, it works 
only for the first child project. The following messages appear on the
console:

[INFO] [dependency:unpack-dependencies {execution: default}] [INFO] 
Expanding: C:\some.war into C:\target\somefiles

It does not work in any child projects afterwards. Only this message 
will appear on the console:

[INFO] [dependency:unpack-dependencies {execution: default}]

Any suggestion?
Adrian.


---------------------------------------------------------------------
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]


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