[
http://jira.codehaus.org/browse/MECLIPSE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127779
]
Will Hoover commented on MECLIPSE-404:
--------------------------------------
I have the same issue when using maven-eclipse-plugin 2.5 (maven v2.0.8,
Windows XP)
For example:
mvn eclipse:clean eclipse:eclipse
<settings>
...
<localRepository>/path/to/repo</localRepository>
...
</settings>
2.5 produces:
M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
2.4 produces:
M2_REPO/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
> 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
