On 24/02/2011 18:49, Marcin Kuthan wrote:
Hi
If you need different version for API part it should be set up as
separate project.
In the API module you probably don't need inherit from myproject-parent.
aggregate
\_myproject-api
\_myproject-impl
\_myproject-subsystem1
\_myproject-subsystem2
\_myproject-parent
You can release myproject-api and myproject-impl in the independent
way. myproject-api and myproject-impl modules don't inherit from
aggregate (rather from corporate pom).
Hi - thanks. Although I chose myproject-api and myproject-impl as an
example, we have many more bundles and the situation is (in general) not
as clean as just having one -impl depending on one -api, by the way the
project is Apache Aries - see dev@aries for more than you would ever
want to read on the subject:-)
I think what you are saying is that the only release process that we can
apply completely generally across all modules and sub-modules is one in
which each bundle (sub-module) is released independently. This seems to
be the conclusion that Felix and Sling have come to.
Zoe
----
Marcin
m4enterprise.googlecode.com
----
On 24 February 2011 12:37, zoe slattery<[email protected]> wrote:
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
