[
http://jira.codehaus.org/browse/MECLIPSE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131241#action_131241
]
Hayo commented on MECLIPSE-404:
-------------------------------
I have a very similar issue that i already tried to report at the wrong place
[MECLIPSE]. Here is what i wrote:
The local repository was set as follows
[code]<localRepository>${user.home}/.m2/repository</localRepository>[/code]
which is documented as the default to do.
When i run "mvn eclipse:eclipse" Maven2 produces entries in .classpath which
all contain a superflouous .m2/repository. E.g.
[code]<classpathentry kind="var"
path="M2_REPO/.m2/repository/javamail/activation/1.4.1/activation-1.4.1.jar"/>[/cod]
Of course, the project will not compile under Eclipse.
In a second project i have additionally set this file as the global
settings.xml in the Sonatype Maven Integration. In that case, when i run the
maven scripts from inside Eclipse, the problem does not appear.
Affects Versions: 0.9.2
Environment: Windows XP, Maven 2.0.7/2.0.8, Eclipse 3.3.2
settings.xml in %USERPROFILE%\.m2 directory
> 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
