[
https://jira.codehaus.org/browse/MECLIPSE-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-240.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> cannot use maven eclipse plugin to resolve installed dependencies that are
> also available in the eclipse workspace
> ------------------------------------------------------------------------------------------------------------------
>
> Key: MECLIPSE-240
> URL: https://jira.codehaus.org/browse/MECLIPSE-240
> Project: Maven Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.0
> Environment: eclipse 3.2.2.
> maven 2.0 plugin integration or latest fix 0.11.20070304-1200
> using other plugins (for svn)
> jdk 1.5.0.1
> os: windows server 2K3
> Reporter: Son, the blue mountain
> Attachments: pb.GIF
>
>
> when adding dependency against another maven artifact but who is locally
> built in the same eclipse workspace, the dependency resolution tries to use
> the eclipse project self.
> however, this looks just like an icon.
> in the code, i cannot reference any class that come from such artifact.
> should i eventually rollback to 0.04 version ?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)