[ http://jira.codehaus.org/browse/MEAR-17?page=all ]
Stephane Nicoll closed MEAR-17.
-------------------------------
Resolution: Won't Fix
If you use dependencies you should update the manifest of the ejb modules
accordingly (Class-Path). This is the way recommended by the spec.
> Jar files packed in the EAR file should also be added to application.xml or
> manifest.mf
> ---------------------------------------------------------------------------------------
>
> Key: MEAR-17
> URL: http://jira.codehaus.org/browse/MEAR-17
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Reporter: Kristoffer Peterhäesel
> Assigned To: Stephane Nicoll
>
> While attempting to package an EAR for deployment on JBoss I have come across
> a (for me) major issue with the way this module works.
> The issue is that there are a lot dependency jars included by default. That
> by itself isn't the problem. The problem is there is no way to include it in
> the classpath without defining all the dependencies again in the pom.xml for
> the EAR.
> In an ideal world (for me) the jars would be an easy way to add the jars to
> the classpath since I want to include all I need in the EAR to make it as
> easy as possible to set up a depoyment environment.
> There are really two options for how to do that. Either the jar files are
> added to the generated Manifest.MF file or else there should be a simple
> option to include all packed jar files to the application.xml. Both should
> (AFAIK) work in any standard-compliant container.
> The option of putting all the jar files in APP-INF/lib only works on Weblogic.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
