You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Andri Saar (JIRA)" <ji...@codehaus.org> on 2007/12/29 18:08:57 UTC
[jira] Created: (MEAR-81) Suppressing application.xml creation (and
inclusion) completely
Suppressing application.xml creation (and inclusion) completely
---------------------------------------------------------------
Key: MEAR-81
URL: http://jira.codehaus.org/browse/MEAR-81
Project: Maven 2.x Ear Plugin
Issue Type: Improvement
Affects Versions: 2.3.1
Environment: Glassfish V2 appserver
Reporter: Andri Saar
Priority: Minor
Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Commented: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168765#action_168765 ]
Stephane Nicoll commented on MEAR-81:
-------------------------------------
why do you care? It's a plugin config thing. It's not linked to a particular mojo
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Commented: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168769#action_168769 ]
Bugittaa Pahasti commented on MEAR-81:
--------------------------------------
Good question. :) I have always thought that only the parameters listed for the goal are used, i.e. that the goal lists all the parameters it uses. If that's not the case, how can I know which parameters the goal will actually use?
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Commented: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168771#action_168771 ]
Stephane Nicoll commented on MEAR-81:
-------------------------------------
you don't need to worry about it. Say that you're interested by the generation of application xml, you look to the parameters, you add the ones you want in the plugin config. Same for the main goal. There's no difference.
As you may guess, it is obvious that the generate application xml mojo (ans so the ear:generate-application-xml goal) is responsible to decide whether or not the application.xml should be generated. Again, you don't care as a user because the only thing you would do is 'mvn package' or 'mvn deploy' or ...
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Updated: (MEAR-81) Suppressing application.xml creation (and
inclusion) completely
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MEAR-81:
--------------------------------
Fix Version/s: 2.3.2
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Closed: (MEAR-81) Suppressing application.xml creation (and
inclusion) completely
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll closed MEAR-81.
-------------------------------
Resolution: Fixed
This is done. If you set the version to 5 and generateApplicationXml to false it won't complain anymore.
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Commented: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118202 ]
Stephane Nicoll commented on MEAR-81:
-------------------------------------
oops my bad. I thought it was done but it isn't actually.
Will do.
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Priority: Minor
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Issue Comment Edited: (MEAR-81) Suppressing application.xml
creation (and inclusion) completely
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168764#action_168764 ]
Bugittaa Pahasti edited comment on MEAR-81 at 3/10/09 9:34 AM:
---------------------------------------------------------------
Hmm, I can't spot that parameter from http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html? Am I missing something?
Edit: Seems to be listed here: http://maven.apache.org/plugins/maven-ear-plugin/generate-application-xml-mojo.html. But isn't it applicable also for the ear task?
was (Author: bugittaa):
Hmm, I can't spot that parameter from http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html? Am I missing something?
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Commented: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Andri Saar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118134 ]
Andri Saar commented on MEAR-81:
--------------------------------
Disregard the part about how semantics change, I was an idiot and the real culprit was found elsewhere.
However, this doesn't change the fact that it'd be nice to be able to suppress the inclusion of application.xml :)
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Priority: Minor
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Commented: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Bugittaa Pahasti (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=168764#action_168764 ]
Bugittaa Pahasti commented on MEAR-81:
--------------------------------------
Hmm, I can't spot that parameter from http://maven.apache.org/plugins/maven-ear-plugin/ear-mojo.html? Am I missing something?
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Work started: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MEAR-81 started by Stephane Nicoll.
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Assignee: Stephane Nicoll
> Priority: Minor
> Fix For: 2.3.2
>
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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
[jira] Commented: (MEAR-81) Suppressing application.xml creation
(and inclusion) completely
Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118201 ]
Stephane Nicoll commented on MEAR-81:
-------------------------------------
Set the version to 5 and it won't complain anymore.
> Suppressing application.xml creation (and inclusion) completely
> ---------------------------------------------------------------
>
> Key: MEAR-81
> URL: http://jira.codehaus.org/browse/MEAR-81
> Project: Maven 2.x Ear Plugin
> Issue Type: Improvement
> Affects Versions: 2.3.1
> Environment: Glassfish V2 appserver
> Reporter: Andri Saar
> Priority: Minor
>
> Currently, the maven EAR plugin requires you to include an application.xml descriptor in every EAR file; however, according to the Java EE 5 spec, this descriptor is now considered optional.
> Furthermore, the existence of application.xml appears to change the semantics of how the application is deployed, at least on Glassfish V2 (if application.xml exists, EJB3 beans with just a local
> interface are not registered in the JNDI directory; if application.xml is not there, all beans are registered in JNDI).
> I can suppress the automatic creation of application.xml with the generateApplicationXml parameter; however, if I do that, maven-ear-plugin starts complaining about not finding application.xml, and currently there is no way (or at least I didn't find any easy way) to stop maven-ear-plugin from trying to include the application.xml.
> It would be great if maven-ear-plugin provided a parameter, say suppressApplicationXml, with what you could force maven-ear-plugin not to include an application.xml in the generated EAR file.
--
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