> elsewhere. You will have to modify the MANIFEST.MF files of your
> modules (ejb, war, etc.) to load classes from the specific jars. Not
> sure, but am willing to bet a nickle that Maven can do the manifest
> stuff for you. (NOTE: I have no specific experience using the ear
> plugin, just creating and deploying EAR files in general.)
>
I faced this 3 weeks ago, most of the manifest is generated, but not the classpath for
jars and wars (ejbs: yes it does).
Using a base manifest file can do the job for the classpath, but this way you have to
maintain the dependency list in the project file and in the manifest. Not fun :(
The patch was already in JIRA for the wars plugin. For jars it's similar and I posted
the fix in the dev list 3 weeks ago, I don't know if they have integrated it. In both
cases It's a modified jelly script that add the classpath if a property is set on the
dependencies.
> (2) Not sure that the ear plugin will do what you want w/o the
> modification you made. Does not appear so from the docs. I would
adding
<properties>
<ear.bundle>true</ear.bundle>
</properties>
In the dependencies do the job for the ear.
You may also be wondering, application.xml get generated when specifying the option,
but it includes a module for every dependencies if I remember well.
Take a look at thew maven magic article it discuss some of thoses issues about J2EE.
http://www.ajlopez.net/ArticuloVe.php?Id=306
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
