Leaving capsule.version unspecified *currently* resolves to an unstable snapshot

[chrisfjones]

I came across the following issue when trying to build a new capsule project:
puniverse/capsule#55
This came up because my project (using capsule-maven-plugin v0.10.0) was resolving the latest capsule version (which happened to be 1.0-rc1-SNAPSHOT and contained the bug above).
Ideally, capsule-maven-plugin would ignore '*-SNAPSHOT' capsule versions when resolving the 'latest' capsule version.
I've been able to work around this issue by explicitly setting capsule.version:
<capsule.version>0.10.0</capsule.version>

[chrisdchristo]

Ah yeah you're right, thanks for reporting. Will issue a fix.

[chrisdchristo]

This is actually a bug in the way VersionRangeRequest (incorrectly) works - see here.

In any case, I've managed to write additional code to skip the SNAPSHOT version and find the latest non-snapshot version. Resolved in 0.10.3