Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Rich Client Platform (RCP) » Best Update Strategy
Best Update Strategy [message #499465] Sun, 22 November 2009 20:25 Go to next message
Timothy Marc is currently offline Timothy Marc
Messages: 547
Registered: July 2009
Senior Member
Hi all,

i've question, for which i didn't know sufficient answer or process on
my own. How to update plugins, for which minor changes or little
bugfixes had been made, that doesn't justify a new version?!

Currently, i try to uninstall the applied plugins and reinstall the new
plugins via its update site?! But i thinks, that's not the best way.

Would it be sufficient to overwrite the exsisting plugins, start the
workbench with -clean argument, to apply the changes? As long as the
dependency of the plugins will not change, i think this could work?!

I will appreciate any hint on this topic. I have to spend so much time
for so little updates right now... there must be something more
efficient outside?!

Thanks a lot
Timothy
Re: Best Update Strategy [message #499614 is a reply to message #499465] Mon, 23 November 2009 14:39 Go to previous messageGo to next message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

There's 2 levels to this question ... development and release.

In release, that's what the micro segment of your version is for:
1.2.0.v20090101 - release
1.2.1.v20090201 - includes 5 bug fixes
1.2.2.v20090221 - includes 1 bug fix
1.2.3.v20090405 - includes 4 bug fixes.

In development, the qualifier will do:
1.2.1.v20090122
1.2.1.v20090125 <- eclipse knows that this version has new code.


But I can't emphasize this enough ... if you are releasing code, use the micro segment. most qualifiers are little more than a timestamp, and that's not usually enough to track which fixes are contained in what. It's also not enough to manage on most SCM systems.

Eclipse's policy is written down http://wiki.eclipse.org/Version_Numbering

PW


Re: Best Update Strategy [message #499702 is a reply to message #499614] Mon, 23 November 2009 19:13 Go to previous messageGo to next message
Timothy Marc is currently offline Timothy Marc
Messages: 547
Registered: July 2009
Senior Member
Hey Paul,
thanks for your response. It seems as i was not able to figure out, what
exactly i wanted to know. I'm not interested in versioning and releasing
a complete software. I'm working in a small project, where i have to
deliver each week a new iteration of my plugins. The point is how to
tell galileo, that the code inside the update site has changed?!

I've tried the following, wiht no success:

1. I rebuild the entire update site - Galileo's p2 states, that there is
no new software to install. When i select 'Check for Update' my feature
are not in the list of updateable software.

2. I've uninstalled the all feature of the software and than reinstalled
the rebuild plugins in the update site. Even when i start the eclispe
with -clean, the new plugins are not recognized. It seems to me, that a
kind of cache disallows the new code to execute - or something similar
to it. Sometimes p2 fails with an execution, that a jar could not be
found (which is definitly present in the update site).

3. I've just copied the rebuild plugin over the existing one, and
restart eclispe with -clean. No success...

The only workflow, that leads me to success, was to delete the entire
eclipse distribution and unzip a clear, new one. But this is waisting so
much time, that i'm blocked the whole day just for finishing one new
rebuild update site with sometimes just renamed strings in the ui.

Hope this clarifies my need better.

I appreciate any help.

Thanks in advance

Timothy

Paul Webster schrieb:
> There's 2 levels to this question ... development and release.
>
> In release, that's what the micro segment of your version is for:
> 1.2.0.v20090101 - release
> 1.2.1.v20090201 - includes 5 bug fixes
> 1.2.2.v20090221 - includes 1 bug fix
> 1.2.3.v20090405 - includes 4 bug fixes.
>
> In development, the qualifier will do:
> 1.2.1.v20090122
> 1.2.1.v20090125 <- eclipse knows that this version has new code.
>
>
> But I can't emphasize this enough ... if you are releasing code, use the
> micro segment. most qualifiers are little more than a timestamp, and
> that's not usually enough to track which fixes are contained in what.
> It's also not enough to manage on most SCM systems.
>
> Eclipse's policy is written down http://wiki.eclipse.org/Version_Numbering
>
> PW
>
Re: Best Update Strategy [message #499739 is a reply to message #499702] Mon, 23 November 2009 21:44 Go to previous messageGo to next message
Wim Jongman is currently offline Wim Jongman
Messages: 280
Registered: July 2009
Senior Member

> 1. I rebuild the entire update site - Galileo's p2 states, that there is
> no new software to install. When i select 'Check for Update' my feature
> are not in the list of updateable software.

Please note that for this to work, you have to update the version number of
the feature, not only the version number of the plugin. Follow the advice of
Paul to update the version numbers.


> 2. I've uninstalled the all feature of the software and than reinstalled
> the rebuild plugins in the update site. Even when i start the eclispe
> with -clean, the new plugins are not recognized. It seems to me, that a
> kind of cache disallows the new code to execute - or something similar
> to it. Sometimes p2 fails with an execution, that a jar could not be
> found (which is definitly present in the update site).

This could be possible. If P2 finds that the same software is already
available it will not download it again.

>
> 3. I've just copied the rebuild plugin over the existing one, and
> restart eclispe with -clean. No success...

...

>
> The only workflow, that leads me to success, was to delete the entire
> eclipse distribution and unzip a clear, new one. But this is waisting so
> much time, that i'm blocked the whole day just for finishing one new
> rebuild update site with sometimes just renamed strings in the ui.
>
> Hope this clarifies my need better.
>
> I appreciate any help.
>
> Thanks in advance
>
> Timothy
>
> Paul Webster schrieb:
>> There's 2 levels to this question ... development and release.
>>
>> In release, that's what the micro segment of your version is for:
>> 1.2.0.v20090101 - release
>> 1.2.1.v20090201 - includes 5 bug fixes
>> 1.2.2.v20090221 - includes 1 bug fix
>> 1.2.3.v20090405 - includes 4 bug fixes.
>>
>> In development, the qualifier will do:
>> 1.2.1.v20090122
>> 1.2.1.v20090125 <- eclipse knows that this version has new code.
>>
>>
>> But I can't emphasize this enough ... if you are releasing code, use the
>> micro segment. most qualifiers are little more than a timestamp, and
>> that's not usually enough to track which fixes are contained in what.
>> It's also not enough to manage on most SCM systems.
>>
>> Eclipse's policy is written down http://wiki.eclipse.org/Version_Numbering
>>
>> PW
>>
Re: Best Update Strategy [message #499915 is a reply to message #499702] Tue, 24 November 2009 14:14 Go to previous message
Paul Webster is currently offline Paul Webster
Messages: 6859
Registered: July 2009
Location: Ottawa
Senior Member

As Wim mentioned, you can only update if numbers change. For example:

I have a number of plugins, and their versions are all 3.6.0.qualifier. I have a couple of features, and their version is 3.6.0.qualifier.

My PDE build.properties contains generateFeatureVersionSuffix=true ... that way each time I build a new plugin (qualifier change) my feature suffix gets bumped up (guaranteed to be higher than the last build).

Then you can just merge your new features/plugins into an existing site, or create a composite repo to keep each build's features/plugins separate (but still use only one site URL).

Are you version qualifiers different between your initial install and the one you say doesn't work?

PW


Previous Topic:Overriding a command name in another plugin
Next Topic:Lost in a maze.
Goto Forum:
  


Current Time: Sat Oct 25 08:49:29 GMT 2014

Powered by FUDForum. Page generated in 0.01975 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software