[jira] Issue Comment Edited: (MEAR-81) Suppressing application.xml creation (and inclusion) completely

["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