[
http://jira.codehaus.org/browse/MNG-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96557
]
Mark Jeffery commented on MNG-2382:
-----------------------------------
Isn't this a duplicate of MWAR-79 which has been resolved ?
> relative path of webResources in parent pom not anchored correctly when run
> from parent
> ---------------------------------------------------------------------------------------
>
> Key: MNG-2382
> URL: http://jira.codehaus.org/browse/MNG-2382
> Project: Maven 2
> Issue Type: Improvement
> Affects Versions: 2.0.4
> Reporter: David Smiley
> Priority: Minor
> Fix For: 2.0.x
>
>
> In my parent POM, in pluginManagement, I have:
> {quote}
> <plugin>
> <artifactId>maven-war-plugin</artifactId>
> <configuration>
> <webResources>
> <resource>
> <directory>src/webapp</directory>
> </resource>
> </webResources>
> </configuration>
> </plugin>
> {quote}
> If I run {{mvn package}} when at the child module with war packaging, this
> works fine. But when I run that at the parent module, the {{src/webapp}}
> path is not interpreted as relative to the child module being built, as it
> should (I think). By comparison, when I configure my source directory, test
> source directory, or resources in the parent pom using a relative path, they
> are correctly interpreted as relative to the module being built, regardless
> of wether I run it from the parent or child module.
> As a work-around, I am forced to prefix the relative path with ${basedir},
> which should not be necessary.
--
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
