License not recognized for "dropwizard-auth-jwt"

Robert Reiz

changed status to resolved

@McPringle True. But as you can see here the "newest" version in our database is "0.8.1-0". VersionEye currently don't have the version '0.8.1-1', that's the problem. But that's not really a bug. VersionEye is crawling Maven Central every day, but Sonatype does NOT update the maven index every day. Unfortunately they only update their index once a week :-( I contacted them already and asked them for a daily update, but I didn't got a positive feedback. For ALL other languages we have daily up-to-date infos in our database. But for Java it is just up-to-date on a weekly basis. Sorry for that. Do you have a good idea how to resolve this problem?

2015-05-26T21:35:11+00:00

Marcus Fihlon reporter

Hi @reiz, thanks for explaining the problem. Unfortunately I don't have a good idea how to solve this issue, if Sonatype don't want to update the Maven Central on a daily basis. But I want to suggest a UI modification in VersionEye to limit the bug reports of this problem:

If the provided version number is not equals to the "newest" version in your database, you could check if the provided version is newer than the "newest" version (e.g. provided version "0.8.1-1" is newer than your version "0.8.1-0"). This could be done by comparing the version string from left to right. If this check is true, you could show an icon at the version entry with a tooltip explaining the problem (newer version, Maven Central updates only weekly).

If VersionEye itself is open source, I could suggest to implement this at our next Hackergarten event!

2015-05-29T11:04:55+00:00

Robert Reiz

Hi @McPringle. That is a good idea. The part which is responsible for comparing the version strings is open source. It is the naturalsorter project. Even if you are not familiar with Ruby you could add some simple test cases here. Or here some tests with more context. I appreciate any input :-)

2015-06-03T07:55:37+00:00

Comments (3)