replace the ...'s as necessary
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
I have this working no problem but I am on vacation til monday, so do
not have access to a sample pom
2009/4/2 David Hoffer dhoff...@gmail.com
I did use excludeTransitive but did not help so I just can't fall back
to unpack-dependencies. I'm in trouble if unpack has trouble with the
Please send sample when you get back.
Dave Hoffer
- sent via G1
On Apr 3, 2009 12:51 AM, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
I have this working no problem but I am on vacation til monday, so do
not have access to a sample pom
2009/4/2 David Hoffer dhoff...@gmail.com
You should use the includeArtifactId to filter exactly the ones you want for
each folder. It looks like it¹s picking up both of your files in both
executions so you just need to be more specific which artifacts to unpack.
On 4/1/09 11:42 PM, David Hoffer dhoff...@gmail.com wrote:
I'm having
I tried that with no success. I explicitly set the one I want and
excluded the one I didn't want but it still did both. There is some
majic in there that I just don't understand.
I had to separate my project into to multi-module builds and use the
unpack goal instead. This one actually works,
I've run into this too. I inferred that the dependency plugin's
unpack-dependencies goal was simply not written in a way that allows it
to be executed twice in the same project. I can see how that could
happen, if one were not pretty careful in the execute() method about
making the scratchpad
It's things like this that give maven a bad rep. Folks spend hours
trying to get it to work and never do. Fixing it is in order, but why
on earth can't the keepers of the plugin document this in an obvious
place?
-Dave
On Thu, Apr 2, 2009 at 11:41 AM, Bryan Loofbourrow
It's things like this that give maven a bad rep. Folks spend hours
trying to get it to work and never do. Fixing it is in order, but why
on earth can't the keepers of the plugin document this in an obvious
place?
Because that assumption below isn't true. The unpack and copy goals allow you
2009/4/2 Brian E. Fox bri...@reply.infinity.nu
It's things like this that give maven a bad rep. Folks spend hours
trying to get it to work and never do. Fixing it is in order, but why
on earth can't the keepers of the plugin document this in an obvious
place?
Because that assumption below
I did use excludeTransitive but did not help so I just can't fall back
to unpack-dependencies. I'm in trouble if unpack has trouble with the
release goal.
I just want to unpack two artifacts at two locations before package
phase, is there a different plugin that can handle this simple case?
10 matches
Mail list logo
