What happens with migrated / moved projects?

[Oliver Kopp]

How does versioneye handle libraries which moved the group?

For instance, pdfbox is now org.apache.pdfbox, but https://www.versioneye.com/java/pdfbox:pdfbox still shows 0.7.3 as latest released version, whereas 1.8.9 should be the lastest release: https://www.versioneye.com/java/org.apache.pdfbox:pdfbox

Same question for jackson 1.x and jackson 2.x: https://www.versioneye.com/java/org.codehaus.jackson:jackson-core-asl vs. https://www.versioneye.com/java/com.fasterxml.jackson.core:jackson-core

The Jackson case is a very special case: The 1.x branch is still maintained and maybe users don't want to switch to the most recent branch. Does versioneye support sticking to one branch?

The behavior should be described in the FAQ.

[Robert Reiz]

@koppor Right now VersionEye is not handling this problem. I want to open VersionEye more for the community. I will give core committers write permission to their pages. That way they could leave a not and link to the new packages. What do you think?

I just updated the FAQs: https://www.versioneye.com/faq.