[
https://issues.apache.org/jira/browse/MECLIPSE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MECLIPSE-748.
-----------------------------------
Resolution: Won't Fix
Assignee: Robert Scholte
The Apache Maven team has decided to retire the maven-eclipse-plugin, so this
issue won't be fixed.
> eclipse:eclipse generates .classpath with nonexisting artifacts
> ---------------------------------------------------------------
>
> Key: MECLIPSE-748
> URL: https://issues.apache.org/jira/browse/MECLIPSE-748
> Project: Maven Eclipse Plugin (RETIRED)
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.9
> Reporter: Jörg Sesterhenn
> Assignee: Robert Scholte
>
> Setup:
> Local maven repo contains lastupdated-metadata for non existing artifacts.
> This can happen if you have a typo in your dependency version number (e.g.
> 11.1 instead of 1.1.1) and execute install.
> Then (later) enter LATEST as version for said artifact dependency and execute
> eclipse:eclipse.
> Unexpected but observed behavior:
> The .classpath will contain an entry for the non existing version (if there
> is no newer version).
> Expected behavior:
> The .classpath should contain the LATEST existing resolvable version of the
> artifact.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)