Eclipse Community Forums: Equinox » Bundles not getting updated from 'dropins' directory

Help

Home

Home » Eclipse Projects » Equinox » Bundles not getting updated from 'dropins' directory

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

Bundles not getting updated from 'dropins' directory [message #651905]

Wed, 02 February 2011 02:57

Ryan

Messages: 4
Registered: February 2011

Junior Member

I have an installation that uses the 'dropins' directory to load additional plugins. If I first start with, say, version 1.0.100 of those plugins, all plugins are loaded fine. If, however, I add updates to those plugins, version 1.0.101 (so both 1.0.100 and 1.0.101 exist in the dropins directory), then not all of them are getting updated.

The curious (and frustrating) thing about this is that the behavior is very sporadic. Sometimes no plugins get updated, sometimes a few do, and sometimes all of them do. If I manually delete all of the old versions, then everything is loaded properly.

I'm starting with -clean, and can see that the new versions are getting added to the metedata repository in the content.xml file. For some reason the ProfileSynchronizer is deciding to not update some of the plugins in this directory.

Can anyone give me some pointers as to why this is occurring? I'm using Eclipse 3.4.2, but haven't tried recreating this with 3.5+.

Thanks!
-Ryan

Report message to a moderator

Re: Bundles not getting updated from 'dropins' directory [message #652026 is a reply to message #651905]

Wed, 02 February 2011 13:30

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

/dropins is a best effort, fail silently, just drop it here folder of
last resort.

I was able to find bugs [1] related to this which were fixed in 3.6. It
can still be related to too many optional bundles (SAT4J gets multiple
solutions) but for small numbers of dropins you need the fixes to the bugs.

The other option is to generate p2 metadata for your plugins [2] and
then you can use Help>Install New Software or the director [3] to
install it correctly.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=301446
https://bugs.eclipse.org/bugs/show_bug.cgi?id=302582

[2]
http://help.eclipse.org/helios/index.jsp?topic=/org.eclipse. platform.doc.isv/guide/p2_publisher.html

[3]
http://help.eclipse.org/helios/topic/org.eclipse.platform.do c.isv/guide/p2_director.html

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Re: Bundles not getting updated from 'dropins' directory [message #652053 is a reply to message #652026]

Wed, 02 February 2011 14:24

Ryan

Messages: 4
Registered: February 2011

Junior Member

Thanks Paul, this info is in line with the research that I have done as well, but does shed some additional light on why it is occurring.

I had experimented a little bit with generating p2 metadata, but didn't try to "properly" install via the p2 director. Are there any similar known issues with this approach in 3.4.2, or will this generation always find the "optimal" solution with the latest plugin versions?

Thanks again,
Ryan

Report message to a moderator

Re: Bundles not getting updated from 'dropins' directory [message #652064 is a reply to message #651905]

Wed, 02 February 2011 14:59

Ryan

Messages: 4
Registered: February 2011

Junior Member

I also see that a "timeout" property is referenced in some of the bugs, to allow the optimization process more time to find the optimal solution. What is this property, and where is it set? Although I understand that this is not a fix, it would be interesting to see whether it affects the result.

Thanks again,
Ryan

Report message to a moderator

Re: Bundles not getting updated from 'dropins' directory [message #652115 is a reply to message #652053]

Wed, 02 February 2011 17:40

Paul Webster

Messages: 6859
Registered: July 2009
Location: Ottawa

Senior Member

On 02/02/2011 09:24 AM, Ryan wrote:
> I had experimented a little bit with generating p2 metadata, but didn't
> try to "properly" install via the p2 director. Are there any similar
> known issues with this approach in 3.4.2, or will this generation always
> find the "optimal" solution with the latest plugin versions?

When generating p2 metadata and then installing via the director, it
works a bit differently. The director is tell the profile which
versions to use (deliberately upgrading these n plugins to 1.0.101), and
then SAT4J has to 1) validate the lineup and 2) work out any optionals.
But the plugins in question aren't optional anymore.

The trouble with /dropins is that the SAT4J solver needs to find a
solution with multiple inputs where they're all marked as optional ...
that's a lot of fiddling.

PW

--
Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Platform_Expression_Framework
http://wiki.eclipse.org/Menu_Contributions
http://wiki.eclipse.org/Menus_Extension_Mapping
http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse .platform.doc.isv/guide/workbench.htm

Paul Webster
http://wiki.eclipse.org/Platform_Command_Framework
http://wiki.eclipse.org/Command_Core_Expressions
http://wiki.eclipse.org/Menu_Contributions

Report message to a moderator

Re: Bundles not getting updated from 'dropins' directory [message #652161 is a reply to message #652115]

Wed, 02 February 2011 19:40

Ryan

Messages: 4
Registered: February 2011

Junior Member

Thanks again for your insights, Paul. Using the director does seem like a step in the right direction. Unfortunately, though, it seems that the -installIU option only allows me to specify 1 bundle to install in eclipse 3.4.2. I don't have a 'feature group' to use, so I would need to run this command once for every updated bundle to be sure everything is updated.

It appears that newer versions allow a comma separated list, which would be just what the doctor ordered (not sure if 3.5 allows it, but 3.6 does). For now, I guess my answer is either:

1) Delete the old plugins from the dropins directory when new ones are added
2) Update to 3.5 or 3.6, so that either the -installIU option can be used with a comma separated list, plus the aforementioned bugs are fixed.
3) Create a feature group and use feature patching to install bundle updates

Of course, 1) is the quickest for the short term. In the intermediate term, I can investigate 2) and/or 3).

Thanks again,
Ryan

Report message to a moderator

Previous Topic:	Helios & Update Manager question
Next Topic:	Problem while exporting my product

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 13:19:03 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter