Eclipse Community Forums: Eclipse Platform » Feature branding requires plugin?

Home » Eclipse Projects » Eclipse Platform » Feature branding requires plugin?

Feature branding requires plugin? [message #312049]

Mon, 29 January 2007 18:36

Eclipse User

Originally posted by: askme.fake.net

I have a plugin project that does not have a Plugin class. I can export
the feature as normal. However, if I do not have a 'branding plugin'
class, the feature does not show up in the about dialog.

Is a branding plugin required for a feature it to show in the
about dialog list of features?

Thanks,

dnoyeB

Re: Feature branding requires plugin? [message #312050 is a reply to message #312049]

Mon, 29 January 2007 18:53

Eclipse User

Originally posted by: richkulp.us.NO_SPAM.ibm.com

Yes, for branding the feature requires a plugin of the same id.

Look up in the Help "Product Configuration Editor". That tells you how
to use the editor to create a branding plugin.

--
Thanks,
Rich Kulp

Re: Feature branding requires plugin? [message #312051 is a reply to message #312050]

Mon, 29 January 2007 20:16

Eclipse User

Originally posted by: askme.fake.net

On Mon, 29 Jan 2007 18:53:29 -0500, Rich Kulp wrote:

> Yes, for branding the feature requires a plugin of the same id.
>
> Look up in the Help "Product Configuration Editor". That tells you how
> to use the editor to create a branding plugin.

Unfortunately what I have is a 'fragment' and not a plugin. I used
the fragmentfeature to add on some new functionality. I wanted to share
the classpath of the plugin I was extending so fragmentfeature made this
work well. But now this fragment can not work as branding for its
associated feature.

If this wont work, then Im gonna have to start some trickery to get me
into the classpath of the plugin in question. Hibernate is none too
friendly about that. I did it before, but this way was much simpler...

Re: Feature branding requires plugin? [message #312053 is a reply to message #312051]

Mon, 29 January 2007 21:30

Eclipse User

You can make a separate plugin which will serve only for branding the
feature.

Snjeza

dnoyeB wrote:
> On Mon, 29 Jan 2007 18:53:29 -0500, Rich Kulp wrote:
>
>> Yes, for branding the feature requires a plugin of the same id.
>>
>> Look up in the Help "Product Configuration Editor". That tells you how
>> to use the editor to create a branding plugin.
>
> Unfortunately what I have is a 'fragment' and not a plugin. I used
> the fragmentfeature to add on some new functionality. I wanted to share
> the classpath of the plugin I was extending so fragmentfeature made this
> work well. But now this fragment can not work as branding for its
> associated feature.
>
> If this wont work, then Im gonna have to start some trickery to get me
> into the classpath of the plugin in question. Hibernate is none too
> friendly about that. I did it before, but this way was much simpler...

Re: Feature branding requires plugin? [message #312054 is a reply to message #312053]

Mon, 29 January 2007 22:46

Eclipse User

Originally posted by: askme.fake.net

On Tue, 30 Jan 2007 03:30:09 +0100, Snjezana Peco wrote:

> You can make a separate plugin which will serve only for branding the
> feature.
>

There is an idea that might just work!

Previous Topic:	Feature Info in About menu
Next Topic:	moveDeleteHook

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Jul 17 13:37:15 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter