jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Donald Kennedy <notificati...@github.com>
Subject Re: [jclouds] Allow other version strings with arbitrary labels (#792)
Date Wed, 01 Jul 2015 14:50:58 GMT
@nacx @demobox You're right, and we actually also do that. We would like a predictable set
of dependencies, so we end up making effectively a pre-release version of jclouds that can
be used as a fixed dependency, with a different groupId. It works fine if we have a single
release made for that jclouds version, but because the release cycles of Brooklyn and Clocker
are different from that of jclouds, we may want to depend on the code present in a -SNAPSHOT
version at different stages. So changing the groupId is not ideal, since we don't want to
encode the patch level there, it really belongs in the version, maybe as `+` separated metadata,
as suggested by the sematic versioning spec.

Basically we are looking for the equivalent of nightly version numbers and builds, or something
similar if not as frequent, fixed to a particular tag or commit id on the -SNAPSHOT development
branch. Is that possible?

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/792#issuecomment-117705047
Mime
View raw message