[
http://jira.codehaus.org/browse/MECLIPSE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127818
]
Arnaud Heritier commented on MECLIPSE-404:
------------------------------------------
I stopped to think a long long time ago ;-)
I agree with Benjamin. What you used was an hack over a bug to try to have
portable settings.
Why I could recommend instead of trying to have an ugly fix in the plugin is
that you use 2 profiles in your settings. Those profiles are activated with the
OS and define the good path for the local repository. It will be transparent
for your team but it will be in the maven way. WDYT ?
> 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
