I would like to clarify couple things.
Forst of all, in my understanding it is not necessary to declare
dependencies in <dependencyManagement> if they all came from the same
reactor build (i.e. when build is self-contained)
You can use features to aggregate several plugins into one unit, so
such features and plugins included in it would be installed to Maven
repository by a separate build
Igor, is that correct?
regards,
Eugene
Igor Fedorenko wrote:
First, this is more or less how dependencyManagement works for regular
maven projects, i.e. the same dependency is listed both in
<dependencyManagement/> and <dependencies/> sections.
Second, from what I saw, most of the projects have one or very few
top-level features that include all bundles/features produced by the
build. It is enough to only include such top-level feature into
<dependencyManagement/> and this will implicitly add everything
included in the feature to the build target platform.
And lastly, I assumed that target platform specification is going to
be useful by itself, especially because it is now possible to import
<dependencyManagement/> section from one pom to another using
scope=import.
Does this make any sense or you still think this problem absolutely
has to be addressed for target platform management to be useful?
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
