You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mark Chesney (JIRA)" <ji...@codehaus.org> on 2006/03/27 01:38:11 UTC
[jira] Commented: (MEAR-17) Jar files packed in the EAR file should
also be added to application.xml or manifest.mf
[ http://jira.codehaus.org/browse/MEAR-17?page=comments#action_61995 ]
Mark Chesney commented on MEAR-17:
----------------------------------
I thought Maven was supposed to "provide guidelines for best practices development". This new property really seems like a hack. The entire Chapter 8 in the J2EE 1.4 spec (See http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf) is dedicated to J2EE assembly and packaging use cases which are required to be supported by any J2EE container. To acheive these use cases with Maven requires redundant, hackish, fragile configuration. Can we look at the big picture and set a Maven standard for J2EE packaging which covers these use cases?
> 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
> Type: Improvement
> Reporter: Kristoffer Peterhäesel
> Assignee: Stephane Nicoll
> Fix For: 2.2
>
>
> 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