I tried your configuration and noted one thing,
It did not work for me when the plugin definition is done under
<plugins> section in <pluginManagement>
but it does work if the plugin definition is done in <plugins> section
in <build>
I am using Maven 2.2.1 Could you try defining your plugin under <build>?
Here is the my config
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<id>copy-dependencies</id>
<phase>prepare-package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<outputDirectory>./target/lib</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
Thanks,
Kalpak
but this can't be really the problem, because my maven version allready knows
the command prepare-package, my version is 2.2.1
after changing the phase to package und running mvn package - gues what,
still nothing happens
I'm gettint more and more frustrated because of this bug / error / wrong
configuration, what ever it is, that maven doesn't copy my jars to the
target folder....
Jörg Schaible-2 wrote:
Hi Nathan,
nsowatsk wrote:
The plugin will be called in the prepare-package phase.
Beware, this phase is quite new (don't know when it was introduced, it
might
have been M2.2 or M3 actually).
There is no asdf
phase, so that won't work.
In older versions it is therefore ignored like "asdf" ... ;-)
- Jörg
---------------------------------------------------------------------
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]
