Eclipse Community Forums: Newcomers » Updates and Libraries

Help

Home

Home » Newcomers » Newcomers » Updates and Libraries

Show: Today's Messages :: Show Polls :: Message Navigator

Updates and Libraries [message #1019128]

Fri, 15 March 2013 04:59

Wojtek

Messages: 47
Registered: August 2011

Member

I just did an update to my Juno installation. Now I have several
"missing" libraries.

If I edit the last error entry in the image
(org.eclipse.ui.workbench_3.103.0.v20120530-1824.jar) I find that there
are two "org.eclipse.ui.workbench" libraries:

org.eclipse.ui.workbench_3.103.1.v20120906-120042.jar
org.eclipse.ui.workbench_3.104.0.v20130204-164612.jar

As a guess the updater deleted the oldest library or else deleted the
incompatible library. My project linked to the old library and now it
is missing.

I probably need to link to the newest version for each library.

Changing all the links is not difficult, just time consuming, plus it
must be done for every project.

Since the root name of the library is the same
(org.eclipse.ui.workbench), would it be possible to have a tool which
automatically chooses the highest version number for all the libraries
included in the project?

--
Wojtek :-)

Attachment: libs.jpg
(Size: 205.56KB, Downloaded 167 times)

Report message to a moderator

Re: Updates and Libraries [message #1021826 is a reply to message #1019128]

Wed, 20 March 2013 18:43

Fritz Schenk

Messages: 9
Registered: February 2012

Junior Member

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. Sad

Report message to a moderator

Re: Updates and Libraries [message #1022012 is a reply to message #1021826]

Thu, 21 March 2013 05:36

Wojtek

Messages: 47
Registered: August 2011

Member

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 :-)

Report message to a moderator

Re: Updates and Libraries [message #1022212 is a reply to message #1022012]

Thu, 21 March 2013 13:46

David Wegener

Messages: 1445
Registered: July 2009

Senior Member

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.

Report message to a moderator

Previous Topic:	eclipse no java virtual machine was found
Next Topic:	Many warnings in SWT while doing HelloWorldSWT cheat sheet

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 16 20:17:08 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter