Updates are broken / slow for certain packages

[[e-mail]]

I noticed that there are some packages that aren't updating. For example, closure compiler hasn't picked up the update for over a week:

https://www.versioneye.com/java/com.google.javascript:closure-compiler/v20141215

and iojs missed yesterday's 1.2.0 update:

https://www.versioneye.com/nodejs/iojs-linux-x64/1.1.0

Is this a known issue / intended behavior?

[Robert Reiz]

That's not the intended behaviour ;) The NodeJS Crawler didn't run yesterday. Some problem with the infrastructure. We are working on it and that should be fixed today!

[Robert Reiz]

Here is our landing page for NodeJS: https://www.versioneye.com/Node.JS As you can see the bar for yesterday is missing.

[Robert Reiz]

The AWS instance for the NPM Crawler was not reacting somehow. Just started a new machine for the job. The NPM crawler is running right now! In ~ 2 hours we re in sync again.

[Robert Reiz]

@avindra VersionEye is currently tracking 123K Java projects. See here: https://www.versioneye.com/java But we are not tracking them from SCMs like GitHub. We track them from package managers. Especially search.maven.org, jCenter and a hand full other ones. The newest git tag on that Java Project is not yet published on search.maven.org. See here: http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22com.google.javascript%22%20AND%20a%3A%22closure-compiler%22 The current version on Maven Central is the same we have listed on VersionEye.

The first "bug" you described here is not a bug, it works like intended. However it sounds like a good feature request. We have a crawler for GitHub tags and it would be possible to track some Java projects on GitHub as well. Please open for that a new ticket as feature request.

[[e-mail]]

I saw your other comment on the package too. Makes sense :) I'll open another ticket now.

[Robert Reiz]

I consider this ticket as resolved. Discussions continue in other tickets.