maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Sesterhenn (JIRA) <j...@codehaus.org>
Subject [jira] (MECLIPSE-748) eclipse:eclipse generates .classpath with nonexisting artifacts
Date Thu, 14 Nov 2013 14:32:20 GMT

     [ https://jira.codehaus.org/browse/MECLIPSE-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jörg Sesterhenn updated MECLIPSE-748:
-------------------------------------

    Description: 
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.


  was:
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 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.


    
> eclipse:eclipse generates .classpath with nonexisting artifacts
> ---------------------------------------------------------------
>
>                 Key: MECLIPSE-748
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-748
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.9
>            Reporter: Jörg Sesterhenn
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message