[
http://jira.codehaus.org/browse/MECLIPSE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127814
]
Benjamin Bentmann commented on MECLIPSE-404:
--------------------------------------------
bq. we should still be able to use forward slashes
There is nothing wrong with the slashes themselves, "C:\nemours\..." and
"C:/nemours/..." wil work equally well on Windows. The important difference is
between "C:/nemours/..." and "/nemours/...": The first path being recognized as
absolute, the later one as relative.
Up to 2.4, the plugin's {{EclipseClassPathWriter}} did not check for a relative
path when generating the ".classpath". This has been changed in
[r616816|http://svn.apache.org/viewvc?view=rev&revision=616816] to solve
MECLIPSE-344.
bq. In our organization we use a distributed settings.xml that all developers
use.
To my knowledge, the settings.xml is not meant for such a scenario. In general,
there is simply no portable way of specifying an absolute path across Win/Unix
with a simple string constant: What the one system considers absolute will the
other system consider relative.
Therefore, you might want to consider to replace the localRepository value (or
at least some prefix) with an expression, e.g.
{code:xml}
<localRepository>${env.M2_REPO}</localRepository>
{code}
This way, developers could deal with the different filesystems but still share
the rest of the settings.xml.
In the end, that's a general configuration issue... let's see what Arnaud
thinks.
> 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
