maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <>
Subject [jira] (MEAR-88) Improve documentation on combining Eclipse and Maven Integration
Date Thu, 21 Nov 2013 19:47:45 GMT


Robert Scholte commented on MEAR-88:

[~afloom] sure, go ahead. It must be clear that this is a special case. Users of Kepler and
some previous version can skip this page.
> Improve documentation on combining Eclipse and Maven Integration
> ----------------------------------------------------------------
>                 Key: MEAR-88
>                 URL:
>             Project: Maven Ear Plugin
>          Issue Type: Improvement
>            Reporter: Chris Graham
>            Assignee: Robert Scholte
>            Priority: Trivial
>             Fix For: 2.9
> This could be implemented as another example.
> Eclipse and Maven Integration
> If you have used {{mvn eclipse:eclipse}} to generate the metadata for an EAR project,
it will want the {{application.xml}} file in the {{src\main\application\META-INF}} directory.

> If you edit application.xml using the WTP based Application Deployment Descriptor editor,
it will use the name of the projects (Web, EJB etc) as the name of the modules. Here is an
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <application xmlns="" xmlns:xsi=""
>   <display-name>FireDragon</display-name>
>   <module>
>     <web>
>       <web-uri>FireDragonWeb.war</web-uri>
>       <context-root>firedragon</context-root>
>     </web>
>   </module>
> </application>
> {code}
> Obviously this does not have the typical maven based version naming convention applied
to it. This allows us to run the application internally within eclipse/rsa using the test
> However, when maven is used to create the ear using mvn package, it will create the versionised
application.xml file, if told to. However, by default it will not pick up the generated (versionized)
one, it will use the existing one in the {{src\main\application\META-INF}} directory.
> The solution to resolve this conflict is to have maven generate the application.xml and
use the generated one as opposed to the existing one.
> This can be achieved via these two directives:
> {code:xml}
> <generateApplicationXml>true</generateApplicationXml>
> <applicationXml>${}/application.xml</applicationXml>
> {code}
> The first line tells maven to generate a new application.xml file, by default in the
target directory.
> The second line tells maven to use it.
> Simple!
> -Chris

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message