Eclipse Community Forums: Eclipse Platform » Diff between deployable feature/plugin and fragment

Home » Eclipse Projects » Eclipse Platform » Diff between deployable feature/plugin and fragment

Diff between deployable feature/plugin and fragment [message #308514]

Tue, 26 September 2006 21:12

Eclipse User

Originally posted by: joneo_ytk81.hotmail.com

hi

can someone help me to explain the differences between deployable feature
and deployable plugin and fragment? actually what i'm trying to do is to
deploy my plugin to my customer through update site. along the way i'll
have some version update let say from 0.1.0 to 1.0.0 or a patch releases.
so i wonder how can i do it? is it everytime also have to setup a feature
project? please advice. thanks.

Re: Diff between deployable feature/plugin and fragment [message #308516 is a reply to message #308514]

Tue, 26 September 2006 21:37

Eclipse User

A plugin is the eclipse "unit of work" :-) An OSGi bundle that supplies
a classpath and can contribute to eclipse through extensions.

A fragment points to a host plugin, and anything it provides (classpath,
extensions, etc) are "sucked" into the host plugin. A fragment is also
a more specialized OSGi bundle.

A feature represents a versioned collection of plugins, and is used for
configuration management in eclipse. They can be deployed manually or
through the update manager. If you want to deploy through the update
manager, then you need to use features to represent your plugins.

Later,
PW

Re: Diff between deployable feature/plugin and fragment [message #308518 is a reply to message #308516]

Tue, 26 September 2006 21:51

Eclipse User

Originally posted by: joneo_ytk81.hotmail.com

Paul Webster wrote:

> A plugin is the eclipse "unit of work" :-) An OSGi bundle that supplies
> a classpath and can contribute to eclipse through extensions.

> A fragment points to a host plugin, and anything it provides (classpath,
> extensions, etc) are "sucked" into the host plugin. A fragment is also
> a more specialized OSGi bundle.

> A feature represents a versioned collection of plugins, and is used for
> configuration management in eclipse. They can be deployed manually or
> through the update manager. If you want to deploy through the update
> manager, then you need to use features to represent your plugins.

> Later,
> PW

i know my question will sound stupid but i wish to get a clear picture of
how you guys work on it.i was wondering how can eclipse plug-in developer
create so much of version updates? are they creating alot of eclipse
plug-in project or they just update the version info for their plug-in?

Re: Diff between deployable feature/plugin and fragment [message #308550 is a reply to message #308518]

Wed, 27 September 2006 20:51

Eclipse User

joneo wrote:
> i know my question will sound stupid but i wish to get a clear picture
> of how you guys work on it.i was wondering how can eclipse plug-in
> developer create so much of version updates? are they creating alot of
> eclipse plug-in project or they just update the version info for their
> plug-in?
>

We update the versions of our plugins when we change code. In the past
we kept up with eclipse versions, but we adopted these guidelines in 3.2:

http://wiki.eclipse.org/index.php/Version_Numbering

Later,
PW

Re: Diff between deployable feature/plugin and fragment [message #308555 is a reply to message #308550]

Wed, 27 September 2006 21:20

Eclipse User

Originally posted by: joneo_ytk81.hotmail.com

Paul Webster wrote:

> joneo wrote:
>> i know my question will sound stupid but i wish to get a clear picture
>> of how you guys work on it.i was wondering how can eclipse plug-in
>> developer create so much of version updates? are they creating alot of
>> eclipse plug-in project or they just update the version info for their
>> plug-in?
>>

> We update the versions of our plugins when we change code. In the past
> we kept up with eclipse versions, but we adopted these guidelines in 3.2:

> http://wiki.eclipse.org/index.php/Version_Numbering

> Later,
> PW

if like what you said you guys will just update the version of your
plug-in then what if you want to know the changes you made in version 1.0
against version 2.0, how you want to do it? are you guys using some kind
of version controlling system like CVS or SVN to check-in/out/diff the
plug-in project?

Re: Diff between deployable feature/plugin and fragment [message #308556 is a reply to message #308555]

Wed, 27 September 2006 21:29

Eclipse User

joneo wrote:
>
> if like what you said you guys will just update the version of your
> plug-in then what if you want to know the changes you made in version
> 1.0 against version 2.0, how you want to do it? are you guys using some
> kind of version controlling system like CVS or SVN to check-in/out/diff
> the plug-in project?

isn't all software in a version control system somewhere? :-)

Eclipse uses CVS, and tags each release.

Even now I can take one of my projects, like org.eclipse.ui.workbench,
and compare HEAD against R3_2 or R3_1_2. It'll give me all of the files
that have changed (which is sometimes not so useful if we had to update
copyright notices :-)

Later,
PW

Previous Topic:	Registering an editor to handle a given extension
Next Topic:	API to restart the platform

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Nov 09 04:19:45 EST 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter