RE: [ear plugin] Including "common" jars into ear
> 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 true 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]
Re: [ear plugin] Including "common" jars into ear
I believe this is done in CVS already. -- dIon Gillard, Multitask Consulting "Teemu Hiltunen" <[EMAIL PROTECTED]> wrote on 04/03/2004 10:05:23 PM: > Greetings! > > We're trying to create an ear with some ejb-modules and a war-module. The > ejb-modules and war uses some common jars. I was wondering whether it is > even legal to put these commons jars into ear root without the need to put > them each into an ejb-module and war-module? And if it is legal (should be) > then the Maven ear-plugin should be modified to include jars without making > a -element into application.xml - because the common jars are not > application client jars. We have some problems with Oracle AS when deploying > an ear where all the correct jars are inside each ejb or war module. > > I modified the ear-plugins (version 1.3) plugin.jelly file: > > > > > > ... > > ... > > and added into project.xml in common jars (log4j for example): > > > log4j > log4j > 1.2.8 > jar > > >true >false > > > > Now I can create an ear which doesn't have a -element for log4j.jar. > > So, my question; is it legal to create an ear with "common" jars that are > not application-clients and if so should the ear-plugin to be modified > accordingly? > > > --teemu > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
Re: [ear plugin] Including "common" jars into ear
(1) Yes, you can add POJJ (plain ol' java jars) to an EAR file, root or 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.) (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 suggest checking JIRA for a pre-existing request, or create a new one, to which to submit this as a patch. jeff Teemu Hiltunen wrote: Greetings! We're trying to create an ear with some ejb-modules and a war-module. The ejb-modules and war uses some common jars. I was wondering whether it is even legal to put these commons jars into ear root without the need to put them each into an ejb-module and war-module? And if it is legal (should be) then the Maven ear-plugin should be modified to include jars without making a -element into application.xml - because the common jars are not application client jars. We have some problems with Oracle AS when deploying an ear where all the correct jars are inside each ejb or war module. I modified the ear-plugins (version 1.3) plugin.jelly file: ... ... and added into project.xml in common jars (log4j for example): log4j log4j 1.2.8 jar true false Now I can create an ear which doesn't have a -element for log4j.jar. So, my question; is it legal to create an ear with "common" jars that are not application-clients and if so should the ear-plugin to be modified accordingly? --teemu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- jeff bonevich mailto: [EMAIL PROTECTED] "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." Rich Cook "All programmers are playwrights and all computers are lousy actors." Unknown - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ear plugin] Including "common" jars into ear
Greetings! We're trying to create an ear with some ejb-modules and a war-module. The ejb-modules and war uses some common jars. I was wondering whether it is even legal to put these commons jars into ear root without the need to put them each into an ejb-module and war-module? And if it is legal (should be) then the Maven ear-plugin should be modified to include jars without making a -element into application.xml - because the common jars are not application client jars. We have some problems with Oracle AS when deploying an ear where all the correct jars are inside each ejb or war module. I modified the ear-plugins (version 1.3) plugin.jelly file: ... ... and added into project.xml in common jars (log4j for example): log4j log4j 1.2.8 jar true false Now I can create an ear which doesn't have a -element for log4j.jar. So, my question; is it legal to create an ear with "common" jars that are not application-clients and if so should the ear-plugin to be modified accordingly? --teemu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
