Eclipse Community Forums: Eclipse Platform » Curiosity about need for a seperate feature branding plugin

Help

Home

Home » Eclipse Projects » Eclipse Platform » Curiosity about need for a seperate feature branding plugin

Show: Today's Messages :: Show Polls :: Message Navigator

Curiosity about need for a seperate feature branding plugin [message #319798]

Fri, 31 August 2007 18:18

Pete Ellis

Messages: 85
Registered: July 2009

Member

Hello everyone,

While evolving my Eclipse plug-ins into a product via a feature-based
product configuration, I find myself stumped as to why a feature's branding
information must be specified *outside* the feature plug-in (i.e., what was
the design thinking that resulted in this choice). Some thoughts:

1) Given that a feature requires its own plug-in to define, there is a
ready-made location for such information (about.ini, about.properties, etc.,
etc.)

2) Creating a plug-in that is dedicated to nothing other than providing
branding info to a feature seems quite heavy-weight to me

3) "Piggy-backing" branding information on some other plug-in that is
included in the feature seems, well, a bit kludgy (and could introduce
inconvenient problems down the road if said plug-in was moved from feature A
to feature B).

Any insights as to what the advantages are in the current feature branding
scheme? I'm willing to play by the current rules, but I sure don't
understand where they came from...

-Pete

Report message to a moderator

Re: Curiosity about need for a seperate feature branding plugin [message #319800 is a reply to message #319798]

Fri, 31 August 2007 21:27

Eclipse User

Originally posted by: automatic.javalobby.org

I think that's just the way it worked. Quite possibly, some of the feature.xml stuff needs to be downloaded when a site.xml is hit, but before any other stuff gets downloaded.

In any case, the new provisioning (http://wiki.eclipse.org/index.php/Category:Provisioning) stuff will ditch the old update manager and provide a new mechanism, although it's yet to be seen whether features will still make an entrance or if they'll be handled by something else.

Alex.

Report message to a moderator

Re: Curiosity about need for a seperate feature branding plugin [message #319848 is a reply to message #319800]

Tue, 04 September 2007 11:20

Pete Ellis

Messages: 85
Registered: July 2009

Member

Alex -
Thanks for the pointer... I had not encountered any material about
provisioning, although it appears from the dates in this wiki that it is in
its formative stages.

-Pete

"Alex Blewitt" wrote:
>I think that's just the way it worked. Quite possibly, some of the
>feature.xml stuff needs to be downloaded when a site.xml is hit, but before
>any other stuff gets downloaded.
>
> In any case, the new provisioning
> (http://wiki.eclipse.org/index.php/Category:Provisioning) stuff will ditch
> the old update manager and provide a new mechanism, although it's yet to
> be seen whether features will still make an entrance or if they'll be
> handled by something else.
>
> Alex.

Report message to a moderator

Previous Topic:	Where can I find a list of the cheat sheet commands?
Next Topic:	Extension to custom extension point won't register

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Jun 30 00:31:29 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter