Hi Karl - thanks for this, but I really _want_ different versions of the
bundles, that's the problem.
I'd like to be able to follow OSGi semantic versioning for bundles, that
means that the versions will necessarily be different for sub-modules. I
understand that the alternative is to release each bundle independently
(this is what Sling do) - but we have a very large number of bundles and
they are usefully grouped into modules.
So, I'm looking for some way to override the check that happens in the
release prepare, or something like that. It's a bit frustrating that the
-DdryRun all works OK :-/
Zoe
Hi,
the problem i oberserve is that you have different versions in your
components. A usual multimodule build contains only a single version number
at root.
myproject
\_myproject-parent (version 1.0.1-SNAPSHOT)
\_myproject-api
\_myproject-impl
All other modules have only a reference to their parent
<parent>
<groupId>..</groupId>
<artifactId>..</artifactId>
<version>1.0.1-SNAPSHOT>
</parent>
<artifactId>myproject-impl</artifactId>
Take a look at this simple example:
https://github.com/khmarbaise/testprojects
Kind regards
Karl Heinz Marbaise
-----
Kind regards
Karl Heinz Marbaise
----
http://www.soebes.de
http://www.skmwiki.de
http://supose.org/wiki/supose
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
