[
http://jira.codehaus.org/browse/MEAR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86015
]
Stephane Nicoll commented on MEAR-57:
-------------------------------------
It's not a bug. You have to specify the ${basedir} in a multi-modules build.
> Path to application.xml doesn't resolve properly in a multi-module build
> ------------------------------------------------------------------------
>
> Key: MEAR-57
> URL: http://jira.codehaus.org/browse/MEAR-57
> Project: Maven 2.x Ear Plugin
> Issue Type: Bug
> Reporter: Jason Melnick
> Priority: Minor
>
> I have three poms - BasePOM <- MultiModulePOM <- EarPOM. My application.xml
> is at the the root of the project in META-INF.
> BasePOM declares plugin configuration as such:
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-ear-plugin</artifactId>
> <configuration>
>
> <generateApplicationXml>false</generateApplicationXml>
>
> <applicationXml>META-INF/application.xml</applicationXml>
>
> <manifestFile>META-INF/MANIFEST.MF</manifestFile>
> <archive>
> <manifest>
>
> <addClasspath>false</addClasspath>
> </manifest>
>
> <manifestFile>META-INF/MANIFEST.MF</manifestFile>
> </archive>
> </configuration>
> </plugin>
> When EarPOM is run separately the plugin does what it is supposed to do and
> finds both the application.xml and MANIFEST.MF.
> As soon as I attempt to run a multi-module build using the MultiModulePOM
> (which runs the EarPOM as a module) the application.xml can not be found (but
> oddly enought the MANIFEST.MF can be found).
> If I change the <applicationXml>META-INF/application.xml</applicationXml> to:
> <applicationXml>${basedir}/META-INF/application.xml</applicationXml>
> it works fine in both solo and multi-module.
--
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
