`mvn dependency:build-classpath -DincludeScope=test`
doesn't show test jars that have been added to the pom.xml
org.apache.spark
spark-streaming_${scala.binary.version}
${project.version}
org.apache.spark
spark-streaming_
using version 2.5.1 of the maven-dependency-plugin.
My project is buiding a zip file containing a set of dependency jars and
i am also generating 2 files containing the classpath (generated using
dependency:build-classpath) and the list of jars (generated using
dependency:list).
Unfortunately
Hi,
I am using version 2.5.1 of the maven-dependency-plugin.
My project is buiding a zip file containing a set of dependency jars and i am
also generating 2 files containing the classpath (generated using
dependency:build-classpath) and the list of jars (generated using
dependency:list
of the maven-dependency-plugin.
My project is buiding a zip file containing a set of dependency jars and
i am also generating 2 files containing the classpath (generated using
dependency:build-classpath) and the list of jars (generated using
dependency:list).
Unfortunately the output for the version
I have driven myself bonkers on this one. I seem to be able to set the path
separator as any value except the new line character. Is there a limitation I
should be aware of?
I am trying via the bash prompt. My tests with shell scripts seem to show I have
actually passed in the new line, but maven
I have driven myself bonkers on this one. I seem to be able to set the path
separator as any value except the new line character. Is there a limitation
I have no idea if there is a limitation or not, but it seems to me
that using new line as a path separator is a bad character to use. Can
you
I am trying to use dependency:build-classpath. If I run mvn
dependency:analyze all seems fine, but if I do mvn
dependency:build-classpath, it seems to ignore my configuration. For
example, the scope and outputFileFilter settings are ignored in the
second case. Am I doing something wrong
i don't think the classpath is filtered based on those values in this
goal, it just dumps the actual classpath that would match the desired
scope.
On Mon, Jan 17, 2011 at 10:52 AM, John Anderson dayt...@comcast.net wrote:
I am trying to use dependency:build-classpath. If I run mvn
I'm trying to use the dependency plugin to record classpaths, but it
doesn't seem to write to a file as documented. What have I done wrong?
TIA,
John
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
Is it just printing the classpath instead, or is it not doing anything?
-Original Message-
From: John Coleman [mailto:[EMAIL PROTECTED]
Sent: Friday, February 01, 2008 7:09 AM
To: Maven Users List
Subject: Dependency:build-classpath
I'm trying to use the dependency plugin to record
Hi,
Somehow I managed to get an alpha version in my repos, once I changed
version to specify 2.0, was fine!
Regards,
John
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: 01 February 2008 14:41
To: Maven Users List
Subject: RE: Dependency:build-classpath
Any idea ?
$ mvn dependency:build-classpath
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO]
[ERROR] BUILD FAILURE
[INFO
want to see what jars are on your classpath for specific goals,
just use the -X option.
-Brad
On Fri, 2007-02-23 at 15:59 -0800, Jagan Padmanabha Pillai -X (jpadmana
- Insight Solutions, Inc. at Cisco) wrote:
Any idea ?
$ mvn dependency:build-classpath
[INFO] Scanning for projects
: dependency:build-classpath
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Thu Jan 18 16
14 matches
Mail list logo