> @@ -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>
> Alright, I removed the jclouds-version and made sure each project has its own > version. Cool! Simple test, I think: 1. Change the jclouds-project version to 1.6.1-incubating or some other version 2. Leave the labs projects' version at 1.7.0-SNAPSHOT 3. Run `mvn dependency:list` in e.g. openstack-swift and see which version of jclouds-core it reports Should be 1.6.1-incubating, **not** 1.7.0-SNAPSHOT. If that _doesn't_ work I fear we'll have to go back to having an explicit `jclouds.version` property set in the jclouds-labs-openstack POM :-( Thanks, @zack-shoylev ! --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/11/files#r4969884
