> @@ -61,10 +64,12 @@ limitations under the License.
> <dependency>
> <groupId>org.apache.jclouds</groupId>
> <artifactId>jclouds-compute</artifactId>
> + <version>${jclouds.version}</version>
> might not be snapshot dependencies if the project or project parent are not
> specified as snapshot?
During development, `${project.version}` will always be a snapshot dependency -
at least, that's what I'm assuming. The only interesting moment is at release
time. Then, `${project.version}` will be a non-snapshot _but may different from
the jclouds main version_, e.g. if we release a hypothetical
jclouds-karaf-1.7.0.fixup.1 (or whatever), this should probably still use 1.7.0
as the "main" dependency.
@iocanel: any thoughts on how to handle that case without a `<jclouds.version>`
property?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/22/files#r5513174
