Hi there,

  I'm facing a strange behavior with the dependency plugin. Here is my
configuration

<plugin>
 <groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
 <version>2.1</version>
<executions>
<execution>
 <id>copy-dependencies</id>
<phase>process-sources</phase>
 <goals>
<goal>copy-dependencies</goal>
</goals>
 <configuration>
<outputDirectory>${basedir}/target/site/demo</outputDirectory>
 <overWriteReleases>false</overWriteReleases>
<overWriteSnapshots>true</overWriteSnapshots>
 <overWriteIfNewer>true</overWriteIfNewer>
<excludeTransitive>true</excludeTransitive>
 </configuration>
</execution>
<execution>
 <id>unpack</id>
<phase>process-sources</phase>
 <goals>
<goal>unpack</goal>
</goals>
 <configuration>
<artifactItems>
<artifactItem>
 <groupId>net.sourceforge.floggy</groupId>
<artifactId>floggy-persistence-weaver</artifactId>
 <outputDirectory>${basedir}/target/site</outputDirectory>
<includes>schema/*</includes>
 </artifactItem>
</artifactItems>
   </configuration>
 </execution>
</executions>
</plugin>

  For the copy-dependencies execution it works fine but for the unpack
execution it claims that cannot revolve the dependency
net.sourceforge.floggy:floggy-persistence-weaver BUT this dependency is
declared at dependencies section and it is a sibling project of the current
one in a multi module project. The only difference that I can observe is
that in one execution (unpack ID) I made an explicit reference to the
dependency.
  Any clue why? Any workaround?

  Thanks

  Thiago Moreira

Reply via email to