[
http://jira.codehaus.org/browse/MECLIPSE-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier updated MECLIPSE-206:
-------------------------------------
Component/s: Workspace settings
> IdeUtils.toRelativeAndFixSeparator broken on Windows
> ----------------------------------------------------
>
> Key: MECLIPSE-206
> URL: http://jira.codehaus.org/browse/MECLIPSE-206
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Workspace settings
> Environment: Windows XP
> Reporter: Barrie Treloar
> Priority: Critical
> Attachments: MECLIPSE-206-patch.txt
>
>
> See http://www.nabble.com/forum/ViewPost.jtp?post=7753417&framed=y&skin=177
> The problem is that IdeUtils.toRelativeAndFixSeparator attempts to
> canonicalise relative paths.
> This will cause the result to be based on the current directory of the
> processor and not the project basedir as intended.
> This causes the build to fail with canonicalisation errors.
> I have supplied a patch against r485327 which includes extra test cases and
> all test cases pass.
> I have also:
> * removed the project
> * removed use of assertTrue and converted to assertEquals (tests were
> succeeding when they should not have because the check was on the trailing
> path not the entire path)
> * removed MavenProject from extractResourceDirs (it was never used)
> Some other comments:
> baseDir and projectBaseDir seem to be used but I can not see any use cases
> where these two are not the same value. Shouldn't the pom file always be
> located at the top of the eclipse project workspace? The similar names and
> mostly the same value caused me trouble in understanding the system. If they
> could get removed it would make things easier.
--
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
