> Different version from parent (where the parent if jclouds). I think that's > it.
See [this comment](https://issues.apache.org/jira/browse/JCLOUDS-104?focusedCommentId=13723974&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13723974) in the JIRA issue: my assumption is that this version difference is only required _for releases_, i.e. during development, the snapshot version of jclouds and the dependent project can always be the same. If we need to support differing snapshot versions _during development_ then, yes, we'd need an explicit `<version>` in the dependent project's "project POM", i.e. the one that directly inherits from jclouds-project. If we only need to support different versions (of the dependent project and jclouds) for releases, it seems the Maven release plugin can handle that automatically. OSGi imports are an unresolved issue, however. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-karaf/pull/22#issuecomment-21804938
