Hi Tom,
Tom Huybrechts wrote:
On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
On 12/11/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
> In any Eclipse install, each Import-Package is provided by at least
> one bundle, and you can make a POM dependency on that bundle. It is
> quite easy to implement this by feeding all bundles in the install
> into the resolver and having it calculate the package wiring. This
> buys you one more thing: you can automatically validate if the install
> is consistent.
this is only true with the main eclipse platform distribution, it's
not so easy for anything that depends on other projects. Take WTP,
birt, emf, get or anything else... they could depend on anything in
the target platform or in other projects: you will be able to find a
matching bundle only by deploying the whole callisto or europa
coordinated build together (and it will not so easy neither in that
way, since there are still some duplicate jars with slightly different
versions)
It's true that you couldn't do a deploy of say WTP without having its
dependencies available. I have a target platform POM for this (which
only gathers dependencies to all Eclipse artifacts I have deployed
previously). The state is then calculated over the target platform and
the new dependencies. If there are duplicates, the resolving process
will pick one - the same one that would be used at runtime.
A quick comment: with Eclipse, version dependency requirements can be
specified at the level of individual bundles/plugins and at the level of
features (sets of plugins).
This is described in that document under these subsections
How to specify plug-in requirements:
http://wiki.eclipse.org/index.php/Version_Numbering#How_to_specify_plug-in_requirements
Versioning features:
http://wiki.eclipse.org/index.php/Version_Numbering#Versioning_features
I'm sure this conclusion is obvious to all, but for Maven to 'know'
about and resolve these inter-plugin and inter-feature version
dependencies, it's got to understand the version requirements info
located in manifest.mf (at plugin level) and feature.xml (at feature level).
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
