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 extract it using dependency unpack.
I can't, unless I 1st run install goal from Module A. But this means the
release plugin won't properly work from the parent pom unless I release
Module A and B individually.
Here's what my project looks like:
-parent pom
| - Module A (produces Jar)
| - Module B (includes jar)
I'm wondering if this is just a limitation of the dependency plugin.. :-/
I've been struggling with this for quite some time.
Thought? thanks!
Taras
Dan Tran wrote:
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 dependency plugin
to unpack it.
If I run mvn package from the parent. Module B's dependency plugin is always
trying to take the jar from the repository, not from Module A's target
So my build fails with [INFO] Unable to find artifact.
I always have to run mvn install on Module A before using Module B. Quite
tedious..
And I do have the jar listed in Module B as a dependency and then again in
he plugin like so:
foo.bar
myjar
1.0.0-SNAPSHOT
jar
compile
org.apache.maven.plugins
maven-dependency-plugin
2.0
getjar
generate-sources
unpack
foo.bar
myjar
jar
true
target/tmp
true
true
Any thoughts?
Thanks!
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
