If you want it in, it is a dependency.
Being a dependency does not have any religious significance, it just
means that you think that mod1 will not run without that abc.jar being
there.
Maven makes no value judgments about why you want it included.
If you say you need it Maven will include it.
Ron
On 04/06/2010 11:18 AM, maven-user wrote:
Thanks Ron,
But the abc.jar I want to refer to is created in mod2 using assembly plug-in
as an executable jar
mod2/target/abc.jar
It is not a direct dependency of mod1 . When I use dependency-with-war or
dependencyset in my assembly for mod1.1, it is able to refer all other jar
in Mod2 except abc.jar ... My issue is when creating a distribution in
Mod1.1 , I want to include the abc.jar (created in mod2 target).
Thanks
ronatartifact wrote:
On 03/06/2010 12:00 PM, maven-user wrote:
Hi,
I have multi module project structure as shown below . In mod2 target
directory I have created executable jar, say abc.jar . Now I want to
include
this jar in the archive of mod1.1 that I'm creating using assembly.xml.
My
question is how can I refer to this abc.jar which is a runtime artifact
of
mod2..?
myproject
|__mod1
| |_mod1.1
|_mod2
Thanks.
It is a dependency of mod1 and if your use jar-with-dependency it will
be picked up. Google maven jar with dependency.
Ron
---------------------------------------------------------------------
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]
