|Re: Control the way a feature's version is considered an update or a new feature [message #336962 is a reply to message #336957]
||Thu, 16 July 2009 13:46
Originally posted by: eclipse-news.rizzoweb.com|
Jawher Moussa wrote:
> Sorry if this question was asked (and answered ) before, but I juste
> can't come up with a reasonable search query. I've even had a hard time
> looking for a title :)
> I'm managing an eclipse RCP application (based on ganymede) and an
> update site using the old (non p2) site.xml format.
> Everything is working nicely, except for one minor problem : the update
> dialog doesn't show features where the minor version number changes.
> For example, if the version 1.0.0 of feature A is installed, a newer
> version 1.0.x shows up in the update dialog, whereas 1.x.y doesn't. The
> latter only shows up when you select the "install new features" option.
> Is there any way to tune this behavior ?
There was a Preferences setting to control what kinds of updates were
permitted: Preferences > Install/Update > Valid Updates. It allows the
user to choose between service-level increments only or service and
minor increments. The default, IIRC, was service-level only ("equivalent").
Hope this helps,
> Here is my plugin_customization.ini :
> org.eclipse.update.scheduler/enabled = true
> org.eclipse.update.scheduler/schedule = on-startup
> org.eclipse.update.scheduler/download = false
> org.eclipse.update.core/org.eclipse.update.core.checkSignatu re = false
> I guess there must be a property to configure.
Powered by FUDForum
. Page generated in 0.02768 seconds