github maven project's versions are being misreported by VersionEye

[Former user]

I have been trying without success to figure out why versioneye running from your site on my github project has been producing incorrect version mismatches

https://github.com/andyglick/cucumber-spring-eclipselink

https://www.versioneye.com/user/projects/570d35bffcd19a0045440b35

I am attaching the results of running "mvn dependency:resolve" and of running "mvn versioneye:list" and the pom file itself. None of the version numbers that are being called out on your website are being used by the project. As far as I can tell, there are only 2 artifacts that the versions-maven-plugin believes are out of date, and those have to do with numbering sequence issues.

I'd appreciate it if you could take a look.

[Andy Glick]

This turns out to have been caused by operator error. I had thought, obviously incorrectly, that VersionEye would read my pom.xml after it was checked into my github project. I finally realized that the versioneye-maven-plugin could be used to update the dependencies as seen by VersionEye. I executed versioneye:update and all is better now.

[Robert Reiz]

Hey @andyglick. VersionEye does not actively detect new files in your git repository. Our approach is that you have to pick a file which VersionEye should monitor for you. We want to collect as less personal data as possible.

For big Java Projects the VersionEye Maven Plugin is the way to go, because it resolves all dependencies locally and only sends the results as JSON object to the VersionEye API. I recommend it to run it on each build on your CI server.

Can I close this ticket? Or do you still have questions open?