> @@ -20,8 +20,8 @@
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> <modelVersion>4.0.0</modelVersion>
> <parent>
> - <groupId>org.apache.jclouds.labs</groupId>
> - <artifactId>jclouds-labs-openstack</artifactId>
> + <groupId>org.apache.jclouds</groupId>
> + <artifactId>jclouds-project</artifactId>
> <version>1.7.0-SNAPSHOT</version>
> So: make sure each project has defined, and set to 1.7.0-snapshot
I guess you mean "defined `<version>` tag? Yes, I think that's the suggestion.
> Then dependencies should use the parent version (instead of jclouds.version
> or version).
I think that _should_ work, but it would need to be tested, especially with
nested projects. Specifically, if say "jclouds-labs-toplevel" declares a
dependency with version `${parent.version}` and that dependency is inherited by
a "jclouds-labs-someapi" that has "jclouds-labs-toplevel" as its parent, does
`${parent.version}` resolve to the _jclouds-project_ version or the
_jclouds-labs-toplevel_ version? Since these may be different, we need to
ensure the _jclouds-project_ version is the one that's used!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-openstack/pull/11/files#r4966173
