Hi Alexander,
this is an old thread, but no one has replied yet.
While I think this is possible – what are you trying to achieve?
Or in other words: WHY do you need the dependencies unpacked? What do
you do with them?
Regards,
Ben
On 2020/08/19 18:23:06, Alexander Broekhuis wrote:
> Hi all,
>
).
Mystery solved, not a maven issue, just my misuse of bash.
Dan
From: Sander Verhagen san...@sanderverhagen.net
mailto:san...@sanderverhagen.net
Subject: RE: Dependency plugin: tree, CLI substitution error
Date: May 30, 2015 at 2:28:11 AM EDT
To: Maven Users List users@maven.apache.org
Hi,
Seems like your property is interpreted by BASH, which I don't think is what
you want.
${BLAH} is a BASH variable, mostly equivalent to $BASH. I think what you meant
is '${BLAH}', i.e. not substituted by BASH, giving Maven a chance to
substitute. FYI, you wouldn't want ${BLAH} either
It turns out dependency plugin is using an old version of doxia (version
1.0, latest released is 1.4) that has known thread safety issues. You
*might* be able to work around this by adding the following dependencies to
the dependency-plugin in your pom:
dependency
I fixed the problem on trunk in dependency plugin.
You should be able to modify the deps in your current version to work
around this,
but you need to mimic what I did in the actual fix:
http://svn.apache.org/viewvc?view=revisionrevision=1591759
Kristian
2014-05-01 21:25 GMT+02:00 Kristian
Many thanks Kristian!
I am currently dealing with another emergency but as soon as that is over I
will track down the maven plugins directory and make the change.
I'll add the bug in JIRA as soon as I am able.
Thanks again!
Anthony
On Thu, May 1, 2014 at 4:08 PM, Kristian Rosenvold
Maven will use the dependency plugin from the super pom.
Which you can found at
http://maven.apache.org/ref/3.2.1/maven-model-builder/super-pom.html
On Fri, Apr 18, 2014 at 5:09 PM, Cintia Del Rio miladyarte...@gmail.comwrote:
Hi,
I was reading
It makes a lot of sense.
Cheers,
On 18 April 2014 19:20, MK Tan mktan...@gmail.com wrote:
Maven will use the dependency plugin from the super pom.
Which you can found at
http://maven.apache.org/ref/3.2.1/maven-model-builder/super-pom.html
On Fri, Apr 18, 2014 at 5:09 PM, Cintia Del Rio
The crucial detail was omitted... what version of Maven?
I suspect it could be a transitive dependency with system scope causing a
bug of some sort.
Most likely if you switch to a different version of Maven the command will
work... in which case you might be able to construct a test case to
Hi,
I have already seen such error.
It is caused by the combination of a managed dependency (through
dependencyManagement) defining a dependency with system scope + Maven 3 +
Sonar. The same with Maven 2.2.1 should work.
Though, I have never seen it directly in a dependency:tree execution; only
After Stephen mentioned trying different versions, I had the developer try
out maven 2.2.1. I was about to report back that this worked and how
strange it was -- but before sending I saw this email from Vincent.
I'll pass along the system scope issue - perhaps that is the nail in the
coffin. We
Hi Roy,
Can you use a bisect-style debugging approach? Remove half of the modules
from the build and run dependency:tree again. If it works, add half back in
again; if not, remove half of what remains. Etc. Then at least you might
isolate the problem a bit more. It also might make it easier to
Iirc the latest version does, but older versions didn't (except with m3
where the older versions might also pull from reactor)
On Wednesday, 28 March 2012, Benson Margulies bimargul...@gmail.com wrote:
Does dependency:copy (note, not copy-dependencies) interact with the
reactor? In a
On 13 February 2012 18:20, chad.da...@emc.com wrote:
I'm wondering what the difference would be between the following two ways of
handling copying of a certain type of maven dependency. The dependency I'm
talking about is something like, for instance, a self-extracting installer
that I
I can switch back and forth between versions 2.1, 2.2, and 2.3. With 2.1
I don't get timestamped snapshots, with 2.2 and 2.3 I do get timestamped
snapshots for artifacts that don't come from the reactor. The snapshots
were deployed with Maven 3 to our Nexus server. I think, the fact that
you
Brian, the changes in 2.2 were in the copy goal. the copy-dependencies goal
is the one being used by Reinhart
Reinhart, are you sure this is a change between 2.2 and 2.1, and nite some
side-effect of having run the install phase on your dependencies locally? if
the artifact is resolved from the
If the snapshot was resolved from a repo then it will be timestamped,
if it came from the reactor or local repo, then it will be -SNAPSHOT.
The plugin calls into the maven resolution logic so this is core maven
behavior.
In 2.2, resolution from the reactor was introduced for these goals,
Hmm it seems I solved this by adding:
preparationGoalsclean install/preparationGoals to release plugin.
But still, should reactor be searched be dependency plugin.
On Fri, Jul 30, 2010 at 12:05 PM, Bartosz Baranowski baran...@gmail.comwrote:
Hi
Im having problem with dependency plugin and
I would phrase it differently:
The copy/unpack goals where designed to manipulate files that aren't
normal classpath dependencies of your project such as zips. The
plugin does its own resolution of these artifacts, but doesn't support
ranges or artifacts in the reactor.
The xxx-dependencies
On Tue, Jan 26, 2010 at 9:29 AM, Thiago Moreira (timba)
tmoreira2...@gmail.com wrote:
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
dependency:unpack works on artifacts that are not produced as part of your
build and are not listed as dependencies, as a result you must specify the
full GAV coordinates to resolve the artifact, and if you are foolish enough
to use it for an artifact that is produced as part of the same build
Hi Stephen,
Thank you for the explanation. The documentation is not clear about which
dependency the plugin will work on (from the repository or produced by the
build). For those of you interested in the configuration that fixed my issue
here it go:
execution
idcopy-dependencies/id
mvn dependency:tree -DoutputFile:C:\TMP\out.txt
Why not just use mvn dependency:tree c:\tmp\out.txt?
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Because the I end up with other outputs I don't need, like
Reactor Summary, BUILD SUCCESSFUL,
Sonia
Wayne Fay wrote:
mvn dependency:tree -DoutputFile:C:\TMP\out.txt
Why not just use mvn dependency:tree c:\tmp\out.txt?
Wayne
It means that the transitive version would have been 5.0.0.CR1 but
4.0.4 was explicitly asked for in the project's dependency management
block.
Mark
2009/4/1 Melanie S tech...@yahoo.com:
When I run the dependency plug-in (mvn dependency:tree), I get an output
such as the following:
[INFO]
[mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2008 10:11 PM
To: Maven Users List
Subject: Re: dependency plugin
well, the whole point is that... If module A's jar is a dependency thats
needed for compilation of Module B.
I don't need to use the install goal. Module B finds the Module
It is this goal in the dependency plugin, but in general when working
with multimodule builds, you should just do install. Other plugins can
have the same problems.
Sent from my iPhone
On Sep 12, 2008, at 10:10 PM, Build Guy [EMAIL PROTECTED] wrote:
well, the whole point is that... If
did you use install goal ?
-D
On Fri, Sep 12, 2008 at 6:54 PM, Build Guy [EMAIL PROTECTED] wrote:
Can some one please shine some light on the following scenario..
I have parent pom and 2 modules.
Module A produces a jar file
Module B has Module A's jar as dependency, but it uses the
well, the whole point is that... If module A's jar is a dependency thats
needed for compilation of Module B.
I don't need to use the install goal. Module B finds the Module A jar
when building from the parent.
How ever. If I further want to do something with Module A's jar in
Module B. Like
On Fri, Sep 12, 2008 at 7:10 PM, Build Guy [EMAIL PROTECTED] wrote:
But this means the
release plugin won't properly work from the parent pom unless I release
Module A and B individually.
Not necessarily. You can configure the release plugin to run all the
way through install in the prepare
I see, so what you suggest is add install to the goals conf of the
release plugin?
Cheers
Wendy Smoak wrote:
On Fri, Sep 12, 2008 at 7:10 PM, Build Guy [EMAIL PROTECTED] wrote:
But this means the
release plugin won't properly work from the parent pom unless I release
Module A and B
I am not sure why you are reluctant to run install goal? This sort of
thing works
for me every day. Have you try cut release from the parent pom?
-D
On Fri, Sep 12, 2008 at 7:31 PM, Build Guy [EMAIL PROTECTED] wrote:
I see, so what you suggest is add install to the goals conf of the release
Whether you use assembly or dependency, you will still need to list
the version of the artifact. If you put the version in
dependencyManagement, you can skip the version in the plugin config
for dependency
Sent from my iPhone
On Jul 18, 2008, at 5:48 PM, Kathryn Huxtable [EMAIL PROTECTED]
Use the assembly plugin instead. It's very customizable and can likely
do what you want.
-K
On Jul 18, 2008, at 7:43 AM, Laura Lozano wrote:
Hello,
I'm using the dependency plugin in order to copy the dependencies
from the
repository to a target platform. The problem is that I need to
Wayne,
This is an annoyance. Actually I do not want to keep the jars in my
project directory. I am using the dependency plugin for copying the
third party jars to a directory where i am testing my app. So, I just
need to run this plugin only when there is and addition to my dependency
list.
Is this really a problem for you, or just an annoyance?
Wayne
On 2/27/08, Shakun Gupta [EMAIL PROTECTED] wrote:
Hi All,
I am using the dependency plugin to copy all the dependencies to an
output directory. But, the dependencies are also copied in my
target/dependency directory, i.e., the
Thanks, added that extra dependency and now the warning is gone.
regards,
Wim
2007/11/21, [EMAIL PROTECTED] [EMAIL PROTECTED]:
AFAIK, this shows the dependencies from which your code is using classes,
but which are not declared in your pom file, but by another dependency.
ie.
You -
AFAIK, this shows the dependencies from which your code is using classes, but
which are not declared in your pom file, but by another dependency.
ie.
You - Project A - Project B
And one of your classes imports something from Project B. This will compile.
Project A releases a new versions,
Just wanted to report back that I finally go this to work by doing
this (thanks for the clues along the way):
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
webResources
resource
The dependency plugin doesn't support versions in the copy/unpack goals.
You could try the unpack-dependencies goal instead since that allows
maven core to resolve it. You would then use the filters to get only the
file you want.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
Hmm, I'm having trouble getting 'unpack-dependencies' to work the way
I want. It seems that much more is included in my war file than
'unpack' would give (and unpack would give exactly what I wanted).
Originally I was trying to follow this:
Ok, I got this to include only what I want by changing the phase from
'process-resources' to 'package'. However, because of the
dependencies, the jars are placed under WEB-INF/lib in the war file,
which is not correct.
On Nov 19, 2007 3:53 PM, deckrider [EMAIL PROTECTED] wrote:
Hmm, I'm having
.
Nor did I understand what this message means:
[INFO] No goals needed for project - skipping
Any ideas?
William
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 24 July 2007 11:36 PM
To: Maven Users List
Subject: [***POSSIBLE SPAM***] - RE: dependency
-analyze Mojo which
does exactly what I need.
William
-Original Message-
From: Eric Redmond [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 24 July 2007 11:22 PM
To: Maven Users List
Subject: [***POSSIBLE SPAM***] - Re: dependency-plugin without forking -
Email has different SMTP TO: and MIME
-Original Message-
From: Eric Redmond [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 24 July 2007 11:22 PM
To: Maven Users List
Subject: [***POSSIBLE SPAM***] - Re: dependency-plugin without forking -
Email has different SMTP TO: and MIME TO: fields in the email addresses
dependency:analyze is meant
dependency:analyze is meant to help people check their project dependencies
occasionally and fix accordingly? What use-case do you have for requiring it
to run every time? If you just want a print-out, there is always the
dependency report.
Eric
On 7/23/07, William Ferguson [EMAIL PROTECTED]
Actually in the unreleased snapshot, there is a goal called (i think)
just-analyze that does exactly what you ask ;-)
From: William Ferguson [mailto:[EMAIL PROTECTED]
Sent: Tue 7/24/2007 12:21 AM
To: Maven Users List
Subject: dependency-plugin without forking
Brian, you need to notify repository@apache.org when you do this kind
of changes.
You removed it from apache but it was already in central and all the mirrors.
I moved it out of the way now
On 3/13/07, Brian E. Fox [EMAIL PROTECTED] wrote:
Hi Sorry about that. Alpha-2 was not supposed to be on
Users List
Cc: repository@apache.org
Subject: Re: dependency plugin
Brian, you need to notify repository@apache.org when you do this kind of
changes.
You removed it from apache but it was already in central and all the
mirrors.
I moved it out of the way now
On 3/13/07, Brian E. Fox [EMAIL PROTECTED
PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
Sanchez
Sent: Wednesday, March 14, 2007 1:49 PM
To: Maven Users List
Cc: repository@apache.org
Subject: Re: dependency plugin
Brian, you need to notify repository@apache.org when you do this kind of
changes.
You removed it from apache
Hi Sorry about that. Alpha-2 was not supposed to be on central yet. I
have updated the metadata files by hand to make it go away...it will
take a few hours to rsync to the repo. The good news is that alpha-2 is
staged and being voted on. Baring any sudden issues, it should be
released in ~60hrs
Hi Gerald,
I'm hoping to finish up the 3-4 remaining issues in alpha-2 and call
another release in the next few weeks. The Maven Devs have decided to
always publish the latest version of the sites. The drawback is that
sometimes new goals are listed that haven't been released. The upshot is
that
of exclusions tags with artifactItem ?
Thanks for your help,
Sebastien
-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 7:18 PM
To: Maven Users List
Subject: Re: dependency plugin
The main purpose of artifactItems is so that we dont need to use
:[EMAIL PROTECTED]
Sent: Wednesday, November 08, 2006 7:18 PM
To: Maven Users List
Subject: Re: dependency plugin
The main purpose of artifactItems is so that we dont need to use
dependencies elements.
perhaps, you need
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-dependenc
ies
?
Thanks for your help,
Sebastien
-Original Message-
From: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 11:17 AM
To: Maven Users List
Subject: Re: dependency plugin
artifactItem does not support transitive dependencies. so no need for
exclusion.
But you need
: Dan Tran [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 09, 2006 11:17 AM
To: Maven Users List
Subject: Re: dependency plugin
artifactItem does not support transitive dependencies. so no need for
exclusion.
But you need to specify every item.
-D
On 11/9/06, Sebastien Brunot [EMAIL PROTECTED
The main purpose of artifactItems is so that we dont need to use
dependencies elements.
perhaps, you need
http://maven.apache.org/plugins/maven-dependency-plugin/unpack-dependencies-mojo.html
-D
On 11/8/06, Sebastien Brunot [EMAIL PROTECTED] wrote:
Hi all,
is it possible to parameterize
Certainly. I have already undertaken a major refactoring of the code
because it had growing pains. Go ahead and submit the patch and I'll
include it with the refactor. BTW, the svn version 1.1 can control
SNAPSHOT and release overwrites separately...maybe that's all you need?
-Original
58 matches
Mail list logo
