--- Micha³ Stochmia³ek <[EMAIL PROTECTED]> wrote:
>
>
> > I've got ear multiproject that contain several web and ejb modules.
> Those
> > ejbs and wars have dependency on jar with application logic. Of
> course,
> > application logic has huge number of other 3th party dependencies.
> When
> > I'm building ear, all wars archives contain their own dependencies
> > (including contain application logic and all 3th party
> dependencies). Ear
> > archive contain all ejbs dependencies (also including application
> logic
> > and all 3th party dependencies).
> >
> > In result, I have application logic and all 3th party dependencies
> in each
> > war and also in ear. This includes all configuration files of
> application
> > logic. So if I want to change single property I must change it in
> every
> > application logic jar in each war and ear.
> >
> > What I want to achieve? I want all dependencies from wars in ear
> bundle,
> > not in WEB-INF/lib.
> >
> > I tried to exclude all jars in WEB-INF/lib using exclude tag in war
> > configuration. It works - directory WEB-INF/lib is empty, but it
> didn't
> > solve the problem, since those excluded jars weren't added to ear.
> >
> > Do you know any solution for the problem?
> >
> > best regards,
>
>
> I believe that the problem is connected to issue "Ability to disable
> transitive dependency in a bundle artifact" (MNG-818). This issue
> have been fixed and transitive dependencies of bundle artifacts are
> disabled by default. Is there a way to enable them?
Looking at MNG-818, I don't get what the fix is. Is it true that, as
Michael says, transitive dependencies for war artifacts are disabled by
default ?
If this is true then how can I specify which dependencies should go to
WEB-INF/lib and which should be packaged in the ear and be referenced
through the <war>/META-INF/MANIFEST.MF ?
Please don't tell me that I have to specify the latter in both the war
and the ear poms.
Compare this to maven 1 which uses the properties war.bundle and
war.manifest.classpath in the war project.xml. I think something
similar is needed in maven 2 to distinguish the two cases. The ear
plugin could read them from the war pom.xml to help it select the
dependencies that it should transitively include.
I'm not saying that dependencies should have properties again, but I am
saying that it is the responsability of the war pom.xml to describe
which dependencies it will include itself and which ones should be
provided by its containg ear.
Regards,
Marcel Schutte
__________________________________________
Yahoo! DSL Something to write home about.
Just $16.99/mo. or less.
dsl.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
