Eclipse Community Forums: Eclipse Platform » minor plugin fixes and Versioning in features and plugins question

Home » Eclipse Projects » Eclipse Platform » minor plugin fixes and Versioning in features and plugins question

minor plugin fixes and Versioning in features and plugins question [message #200189]

Mon, 23 February 2004 16:21

Eclipse User

So were developing an update that looks like the following

MainFeature1.0.0
SubFeatureA1.0.0
pluginA1.0.0
SubFeatureB1.0.0
pluginB1.0.0

my question is. What happens when versioning changes inside this structure
so say we update pluginA1.00 to pluginA1.0.1 is the hierarchy now

MainFeature1.0.1
SubFeatureA1.0.1
pluginA1.0.1
SubFeatureB1.0.0
pluginB1.0.0

and then if we update pluginB later on does it then become

MainFeature1.0.2
SubFeatureA1.0.1
pluginA1.0.1
SubFeatureB1.0.1
pluginB1.0.1

So ultimately the user on there machine would have

MainFeature1.0.0
MainFeature1.0.1
MainFeature1.0.2
SubFeatureA1.0.0
SubFeatureA1.0.1
SubFeatureB1.0.0
SubFeatureA1.0.1

and in plugins they would have

pluginA1.0.0
pluginB1.0.0
pluginA1.0.1
pluginB1.0.1

correct?

is there a way to update features with minor "fixes to the plugin, without
having new plugins installed?

I assume you would do something like

MainFeature1.0.0
SubFeatureA1.0.0
pluginA1.0.1
SubFeatureB1.0.0
pluginB1.0.1

correct? but we would end up with

MainFeature1.0.0
SubFeatureA1.0.0
SubFeatureB1.0.0

and in plugins they would have

pluginA1.0.0
pluginB1.0.0
pluginA1.0.1
pluginB1.0.1

But the features would then reference the new fixed up plugins?

Thanks for any guidance here.

Re: minor plugin fixes and Versioning in features and plugins question [message #200326 is a reply to message #200189]

Mon, 23 February 2004 18:23

Eclipse User

Originally posted by: manahan.NOSPAM.ca.ibm.com

What version of eclipse is this for?
Injected some comments below assuming its 2.1.x the answers change for 3.0.

Mike wrote:

> So were developing an update that looks like the following
>
> MainFeature1.0.0
> SubFeatureA1.0.0
> pluginA1.0.0
> SubFeatureB1.0.0
> pluginB1.0.0
>
> my question is. What happens when versioning changes inside this structure
> so say we update pluginA1.00 to pluginA1.0.1 is the hierarchy now
>
> MainFeature1.0.1
> SubFeatureA1.0.1
> pluginA1.0.1
> SubFeatureB1.0.0
> pluginB1.0.0
>

If its an update not a patch then yes.

> and then if we update pluginB later on does it then become
>
>
> MainFeature1.0.2
> SubFeatureA1.0.1
> pluginA1.0.1
> SubFeatureB1.0.1
> pluginB1.0.1
>

If it is an update not a patch then yes.

> So ultimately the user on there machine would have
>
> MainFeature1.0.0
> MainFeature1.0.1
> MainFeature1.0.2
> SubFeatureA1.0.0
> SubFeatureA1.0.1
> SubFeatureB1.0.0
> SubFeatureA1.0.1
>
> and in plugins they would have
>
> pluginA1.0.0
> pluginB1.0.0
> pluginA1.0.1
> pluginB1.0.1
>
> correct?
>
yes.

> is there a way to update features with minor "fixes to the plugin, without
> having new plugins installed?
>

No. You need a new plugin.

> I assume you would do something like
>
> MainFeature1.0.0
> SubFeatureA1.0.0
> pluginA1.0.1
> SubFeatureB1.0.0
> pluginB1.0.1
>
> correct? but we would end up with
>
>
> MainFeature1.0.0
> SubFeatureA1.0.0
> SubFeatureB1.0.0
>
> and in plugins they would have
>
> pluginA1.0.0
> pluginB1.0.0
> pluginA1.0.1
> pluginB1.0.1
>
> But the features would then reference the new fixed up plugins?
>
> Thanks for any guidance here.

Features are the transport mechanism for plugins via update manager. In
2.1.2 you can use a patch feature to update a feature or set of features
in a tree. In 3.0 the patching story changes slightly to have a patch
feature that just brings in new plugins.

Previous Topic:	-> Import Platformsource [3.0M7]
Next Topic:	perforce changelist / VCS Group / task with multiple associated resources?

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 26 03:09:44 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter