work from the command line, don't put it inside an executions block. (this
is a maven issue, there is talk about it in the plugin faq)
-Original Message-
From: Norbert Lazzeri [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2008 9:29 AM
To: Maven Users List
Subject: Re: copy
7;t put it inside an executions block. (this
is a maven issue, there is talk about it in the plugin faq)
-Original Message-
From: Norbert Lazzeri [mailto:[EMAIL PROTECTED]
Sent: Monday, September 29, 2008 9:29 AM
To: Maven Users List
Subject: Re: copy libraries to classpath
yeah i red tha
yeah i red that too. but i thought this would refer to the
configuration-section of the plugin :-S
cheers
norbert
Nick Stolwijk schrieb:
I think the outputDirectory is ignored because of the ArtifactItem
(whatever that may be... ;) )
>From the documentation:
outputDirectory :
Default locati
I think the outputDirectory is ignored because of the ArtifactItem
(whatever that may be... ;) )
>From the documentation:
outputDirectory :
Default location used for mojo unless overridden in ArtifactItem
* Type: java.io.File
* Since: 1.0
* Required: No
* Expression: ${outputDir
using the maven-dependency-plugin with:
org.apache.maven.plugins
maven-dependency-plugin
copy-dependencies
package
Hi,
is it possible to let maven copy all dependencies to my classpath?
my jar-configuration looks like:
org.apache.maven.plugins
maven-jar-plugin
true
