Carsten Karkola schrieb:
So I have to specify the dependencies twice? First time in the
parent/pom.xml and second time in rar/pom.xml (there using
<scope>provided</scope>? I have to play with this, because some of the
dependencies are internal jars from other subprojects.
In my example the dependency is actually referenced/specified three times:
I.
In the <dependencyManagement> section of the parent pom the dependency is defined
including the version to use.
II.
In the rar pom with scope 'provided'. The version is inherited from the parent.
III.
In the ear pom. The version is inherited from the parent.
You only need to touch the ear and rar pom's once to define the dependency and if the
version of the dependency changes you just need to modify the parent pom.
As far as I can see, a workaround is to specifiy all dependencies for the rar-
modules with <scope>provided</scope> and add them a second time to the
ear pom.
Wouldn't it be nice to have some option? Or wouldn't it be enough to say if
I specify manifest classpath entries, I can leave out the dependencies from
the rar archive?
Can you elaborate on this a bit more? This isn't entirely clear to me.
Modules: I use bundelFileName there.
[...]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
