Thomas Hallgren wrote:
> Using features and "required" plugins, we can a more lax dependency
> requirement policy and document that certain features have
> prerequisites on other features from other vendors.
Thomas
Expressing feature level dependencies is often a bad choice, unless you
created the feature yourself.
There are explicit guidelines from the Eclipse platform team to avoid
that, and all project that used to have such dependency are
porgressively replacing that by a plugin level dependency.
The reason is that your plugins are dependent no matter what on third
party plugins.
When you had another dependency from features to features, you end
creating a double whammy.
You get dependent on the third plugins, their versions AND the certain
way they are packaged in a feature, and the version of that feature.
And you can find situations where you plugins level dependencies are
satisfied, yet your feature level dependencies will be not.
It has been the sourec of quite a few bugs in the update area.
The versioning guidelines from the platform team may help you in your
decision:
http://wiki.eclipse.org/index.php/Version_Numbering#Versioning_features
Note that WTP and a few other projects which used to have such deps are
removing them.
So my 2 cents would be to avoid being dependent on Subclipse features,
and instead create your own for your own needs, maintained on your own
site.
--
Cheers
Philippe
http://easyeclipse.org - http://phpeclipse.net - http://eclipse.org/atf
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Sun Jan 28 02:35:02 2007