[
http://jira.codehaus.org/browse/MECLIPSE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127837
]
Benjamin Bentmann commented on MECLIPSE-404:
--------------------------------------------
bq. On windows, I always saw /some/path to be resolved by default to
c:\some\path.
On Windows, a path like "/path" is known as a drive-relative path, i.e. its
effective absolute value depends on your current working directory/drive. Run
Maven on a project located somewhere on "C:" and your local repo is assumed to
reside in "C:\path". Run Maven on a project located on drive "X:" and it will
happily re-download the world to your other local repo at "X:\path" ;-)
That's nothing which Maven specifically does, it's just blindly passing the
user's config setting to the java.io.File API.
bq. I guess that it would be far better for maven-eclipse-plugin to support
this format since maven does, isn't it?
The question is: Is the current behavior of Maven a bug or a feature? I am
tempted to call it a missing validation of input parameters but have just
mailed the dev list to get some clarification on this [path
topic|http://www.nabble.com/Relative-path-to-local-repository--to16132131s177.html].
> Duplicated local repository path in the generated .classpath file
> -----------------------------------------------------------------
>
> Key: MECLIPSE-404
> URL: http://jira.codehaus.org/browse/MECLIPSE-404
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Workspace settings
> Affects Versions: 2.5
> Reporter: Baptiste MATHUS
>
> The generated .classpath is not correct.
> This problem seems to be related to using a non default repository location.
> In fact, if localRepository (in settings.xml) is the following:
> <localRepository>/path/to/repository</localRepository>
> Then all classpathentries in the .classpath file are generated as in the
> following example:
> M2_REPO/projet/MIPIH/repository/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
> instead of
> M2_REPO/classworlds/classworlds/1.1-alpha-2/classworlds-1.1-alpha-2.jar
> I can create a dedicated testcase project if necessary (if you have problem
> reproducing this issue) but I think this will be easy to reproduce by just
> testing with a non default repository location.
> Thanks a lot.
> Cheers.
--
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
