You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org> on 2006/01/12 21:07:01 UTC
[jira] Reopened: (MNGECLIPSE-8) Jar from remote repo not loaded and
causes error in POM
[ http://jira.codehaus.org/browse/MNGECLIPSE-8?page=all ]
Eugene Kuleshov reopened MNGECLIPSE-8:
--------------------------------------
> Jar from remote repo not loaded and causes error in POM
> -------------------------------------------------------
>
> Key: MNGECLIPSE-8
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-8
> Project: Maven 2.x Plug-in for Eclipse
> Type: Improvement
> Versions: 0.0.3
> Environment: Windows XP, Eclipse 3.1, MyEclipse, local repo, no mirrors, central repo is IBiblio, maven2 eclipse plugin 0.0.3
> Reporter: Lee Meador
> Assignee: Eugene Kuleshov
> Priority: Minor
>
>
> It seems like the code that transfers things from the POM to the Eclipse classpath needs the jar to be in the local repository but the repository searcher looks in the central repository. That means you can pick a dependency in the searcher and, if its in a remote repository, although the dependency is added to the POM, the guy that is updating the Eclipse classpath seems to look in the POM and then look in the local repo. Finding it isn't there, we get a red X on the POM and no valid maven classpath at all.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org