Bug 344990

Description Michael Wenig 2011-05-06 11:38:20 EDT

(we are using M2Eclipse 0.12.1)

We have some archetypes in our enterprise-Nexus. M2Eclipse uses per Default the catalog of the "everything" Nexus group and therefore contains release and snapshot versions of the archetypes.

e.g. my-archetype:

1.0
2.0
3.0
3.1-SNAPSHOT

When we try to create a new maven project (or module) per default "show only latest version" is activated and "include snapshots" is deactivated (which is is a good thing).

The problem now is that the "latest" version points to "3.1-SNAPSHOT" which is not shown as it is a snapshot version and the release versions are also not shown as they are not the latest versions.

=> so nothing is shown for our archetypes.

I would expect that version "3.0" would be shown as it is the latest release version

If we active "include snapshots" the latest snapshot (3.1-SNAPSHOT) is shown. When we deactivate "latest only" all versions are shown.


So I think it should be:

latest active + include snapshot: show latest (either Snaphsot or release - similar to Maven version LATEST)

latest inactive + include snapshots: show all (currently correct)

latest active + snapshots inactive: show latest version (similar to Maven RELEASE)

latest inactive + snapshots inactive: show all release versions (this is currently correct).

This is a critical issue as all of out developers claims that none of our archetypes are present (as latest are always snapshots for internal archetypes)