You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Kristoffer Peterh?esel (JIRA)" <ji...@codehaus.org> on 2006/01/24 16:43:06 UTC
[jira] Created: (MEAR-17) Jar files packed in the EAR file should
also be added to application.xml or manifest.mf
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
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MEAR-17) Jar files packed in the EAR file should
also be added to application.xml or manifest.mf
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-17?page=comments#action_58425 ]
Stephane Nicoll commented on MEAR-17:
-------------------------------------
Adding an entry in the manifest on the EAR won't work but I guess you've discovered it meanwhile.
Regarding your other option, only ejb-client module should be included in a <module> <java> entry (see the spec). We already discussed this issue on the user list. I know that JBoss won't complain about this, though.
What about 'profiles'. With the Weblogic profile, we would copy things over APP-INF/lib ; With JBoss, we wil include it in the application.xml.
Thoughts?
> 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
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MEAR-17) Jar files packed in the EAR file should
also be added to application.xml or manifest.mf
Posted by "Kristoffer Peterh?esel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-17?page=comments#action_58426 ]
Kristoffer Peterhäesel commented on MEAR-17:
--------------------------------------------
Hmmm. I see. Never been much of a spec reader myself. But I guess either I've completely misunderstood how to use an appserver or it's another one of those areas where the Sun spec mostly solves theoretical issues and leaves the actual implementation and real world issues to the implementers.
Ah well. Since there is no standard way of doing this I suppose a method of adapting to specific targets would have to be in place. So some kind of profile system would be in order. Out of convenience I have only really looked at JBoss for now. But I guess I'll have to look around and see how I'd solve this issue on other servers to get a better idea if this is really the way to go then.
In the end I presume appservers are supposed to include the required 3rd party libs inside it's installation instead of in individual EAR files. But that don't really work too well with how Maven works. Unless we should completely stop packaging dependencies inside the EAR and instead install them in the server install. In that case a profile approach would definitely be needed as the install structure of the different servers are obviously very different.
Anyway this would move the responsibility of handling dependencies out of the EAR packager and into the domain of one of the deployment modules.
> 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
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MEAR-17) Jar files packed in the EAR file should
also be added to application.xml or manifest.mf
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-17?page=comments#action_58899 ]
Stephane Nicoll commented on MEAR-17:
-------------------------------------
Karthik, I have removed your sub-task, it has nothing to do here. See MEAR-20 for your request.
> 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
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MEAR-17) Jar files packed in the EAR file should
also be added to application.xml or manifest.mf
Posted by "Kristoffer Peterh?esel (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-17?page=comments#action_56906 ]
Kristoffer Peterhäesel commented on MEAR-17:
--------------------------------------------
After having read a bit more on my homework I should revise my suggestion to say that the manifest.mf files to add class-path information to should be the modules bundled in the ear. That of course makes it a bit more complicated to implement since it requires the module to reopen a jar file and modify (or create) the file in them before packaging them in the ear.
Simply adding an option to write all included jars (that are not ejb modules) into the application.xml is by far an easier method of doing this.
> 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
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MEAR-17) Jar files packed in the EAR file should
also be added to application.xml or manifest.mf
Posted by "Karthik (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-17?page=comments#action_58891 ]
Karthik commented on MEAR-17:
-----------------------------
There should atleast be a parameter in the EAR plugin which when set should not bundle the system dependency within the EAR.
> 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
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org