|
|
| Re: Updates and Libraries [message #1022012 is a reply to message #1021826] |
Thu, 21 March 2013 01:36   |
Eclipse User |
|
|
|
Fritz Schenk wrote :
> I imagine that nobody has answered you as you are repeating. Perhaps ask the
> question in a different way. I am unable to answer the question you posed. :(
Um, this is not a repeat post by me.
Ok, let's phrase it this way.
The updater installs new plugins. Because of dependencies on new
features, the installer deletes plugins which, if chosen, would cause
conflicts with the new plugin. (This is an assumption but I think it
fits what happened)
If an existing project includes those older plugins which have been
deleted, then the project cannot be built. The only way to change the
projects library list is to manually go to each plugin which is in
error (ie: missing), and choose the newer (newest) version. This takes
up time, especially as you must scroll through many plugin names to
find the on you are looking for. For each project.
Looking into the plugin directory I can see that almost every plugin
exists in at least two versions. I can also see that all plugins have a
root name followed by the version number.
It should be possible to create a tool on the library setting page
which will run through the existing project plugin names, extract the
root name, then display a list of newer plugins.
-----------------------------------------------------------------------
??? org.eclipse.wst.standard.schemas_1.0.400.v201111021744.jar
( ) org.eclipse.wst.standard.schemas_1.0.500.v201111021744.jar
(*) org.eclipse.wst.standard.schemas_1.0.501.v201301091615.jar
( ) org.eclipse.ui.ide_2.8.1.v20120828-165804.jar
( ) org.eclipse.ui.ide_3.8.1.v20120828-165804.jar
(*) org.eclipse.ui.ide_3.8.2.v20121106-165923.jar
<Cancel> <Select>
-----------------------------------------------------------------------
Hmmm, maybe I should open an enhancement request.
--
Wojtek :-)
|
|
|
| Re: Updates and Libraries [message #1022212 is a reply to message #1022012] |
Thu, 21 March 2013 09:46 |
| Eclipse User |
|
|
|
|
There are a couple of ways to deal with this. First, it is generally recommended that you use a Target Platform separate from you Eclipse installation to create a consistent set of plugins to develop against. Target Platforms allow you to upgrade your Eclipse installation without breaking your builds. Second, you can define version ranges in your plugin dependencies. This allows your plugin to run against a range of dependent plugin versions and a small point release won't break your builds.
|
|
|
Powered by
FUDForum. Page generated in 0.09226 seconds
Home
