[
http://jira.codehaus.org/browse/MWAR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90285
]
Stephane Nicoll commented on MWAR-77:
-------------------------------------
Milos, how can we reproduce this one easily? Using the eclipse plugin?
> calls to DirectoryScanner.setBasedir(String) fail in embedded environment
> -------------------------------------------------------------------------
>
> Key: MWAR-77
> URL: http://jira.codehaus.org/browse/MWAR-77
> Project: Maven 2.x War Plugin
> Issue Type: Bug
> Affects Versions: 2.0.1
> Environment: maven embedded (2.1-SNAPSHOT) in mevenide/netbeans 2.2
> Reporter: Milos Kleint
> Priority: Critical
>
> when the user declares a resource with relative path, eg.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.0</version>
> <configuration>
> <webResources>
> <resource>
> <!-- this is relative to the pom.xml directory -->
> <directory>resource/files</directory>
> <filtering>true</filtering>
> <excludes>
> <exclude>**/*bak</exclude>
> </excludes>
> </resource>
> </webResources>
> </configuration>
> </plugin>
> then the build fails to process the resource correctly. I've traced that back
> to the DirectoryScanner.setBasedir(String) method which will not construct a
> path relative to the pom file, but to the directory where the IDE was started.
--
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
