|Re: Update mechanism & feature versions [message #508194 is a reply to message #506820]
||Sun, 17 January 2010 14:26
| Wim Jongman
Registered: July 2009
Hi Justin, |
Isn't this a minimum flag? compatible meaning compatible AND major?
> I have an RCP app where the main feature version is 1.0.x. I'm moving to
1.x.0, ie from equivalent to compatible, which I can make the update
mechanism recognize by setting:
> org.eclipse.update.core/org.eclipse.update.core.updateVersio ns=compatible
> in my plugin_customization.ini
> However, when I make a major version upgrade, ie 1.x.0 to 2.0.0 then how do
I make the update mechanism recognize that?
> I've seen references on the
http://publib.boulder.ibm.com/infocenter/ledoc/v6r2/index.js p?topic=/com.ibm.rcp.tools.doc.admin/changingdeploymentprefe rences.html
to a major option but having checked out the update core plugin I can't see
any reference in the source (certainly not in UpdateCore.java).
> So, how do you deal with this scenario?!
Powered by FUDForum
. Page generated in 0.01991 seconds