[
http://jira.codehaus.org/browse/MRESOURCES-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=218371#action_218371
]
Tim Astle commented on MRESOURCES-121:
--------------------------------------
There is a workaround for this, by simply specifying the earlier version of the
resources plugin in your POM file. Below is how you'd modify your plugins
section.
<plugins>
<plugin>
<artifactId>maven-resources-plugin</artifactId>
<version>2.2</version>
</plugin>
</plugins>
> expansion of ${pom.basedir} on windows
> ---------------------------------------
>
> Key: MRESOURCES-121
> URL: http://jira.codehaus.org/browse/MRESOURCES-121
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: windows 7
> Reporter: Marco Laponder
>
> when filtering resource the variable ${pom.basedir} expands on my windows
> system to:
> C\:\path\to\pom
> this contains one slash too may, this is an illegal filename which I cannot
> use anymore to open it from my java class.When I remove the first backslash
> so it expands to
> C:\path\to\pom
> the file name is valid
--
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
