[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: [geclipse-dev] Provider name for g-Eclipse plugins
|
Hi Markus
Is this a must from Eclipse.org?
I don't have a problem with it, but just to know!
Is there a way to "safe" the origin of g-Eclipse?
Harald
>>-----Ursprüngliche Nachricht-----
>>Von: geclipse-dev-bounces@xxxxxxxxxxx
>>[mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Markus Knauer
>>Gesendet: Mittwoch, 27. Juni 2007 18:33
>>An: Developer mailing list
>>Betreff: Re: [geclipse-dev] Provider name for g-Eclipse plugins
>>
>>
>>On Wednesday 27 June 2007 18:02, Ashish Thandavan wrote:
>>> Hi folks,
>>>
>>> (Not too sure how important this is, but ...) I just
>>noticed that the
>>> Provider and Plug-in Name entries of our g-Eclipse plugins
>>do not seem
>>> to conform to any rule. Some have Eclipse.org as the Provider and a
>>> meaningful Plug-in Name while others just say 'Bundle-Vendor' and
>>> 'Bundle-Name'. Perhaps this could be unified? I have used 'g-Eclipse
>>> Consortium (www.geclipse.eu)' as the Provider name for the Workflow
>>> Plugins. Perhaps we could use something like this?
>>>
>>> Regards,
>>> Ashish
>>
>>We should use 'Eclipse.org' as Provider Name... as long as
>>the plug-in is from
>>us.
>>
>>Bundle-Vendor, Bundle-Name is an error that happens when the
>>strings are
>>externalized and the plugin.properties file is not included
>>in the binary
>>build (look into build.properties)
>>
>>Regards
>>Markus
>>_______________________________________________
>>geclipse-dev mailing list
>>geclipse-dev@xxxxxxxxxxx
>>https://dev.eclipse.org/mailman/listinfo/geclipse-dev
>>
