Re: [orbit-dev] Q: What should we use as Provider Name?

[David M Williams <david_williams@xxxxxxxxxx>]

Yes. Those provider names stay to what
ever they provided. I covered that in the FAQ section of 
See http://wiki.eclipse.org/Adding_Bundles_to_Orbit#What_to_use_as_Provider_Name.3F
 
:) 


Maybe having their name in lights will
serve as some motivation to get more "prebuilt bundles" ? :)

From:	DJ Houghton <DJ_Houghton@xxxxxxxxxx>
To:	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Date:	04/19/2010 01:25 PM
Subject:	Re: [orbit-dev] Q: What should we use as Provider Name?
Sent by:	orbit-dev-bounces@xxxxxxxxxxx

---

What about bundles that are produced by a third-party
and we just redistribute them as-is? (e.g. ICU) I assume we would leave
the provider name as the producing company?

David
M Williams ---04/19/2010 11:49:01 AM---A: Eclipse Orbit (not Eclipse.org)
We (or I?) have been remiss.

From:	David M Williams <david_williams@xxxxxxxxxx>
To:	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
Date:	04/19/2010 11:49 AM
Subject:	[orbit-dev] Q: What should we use as Provider Name?
Sent by:	orbit-dev-bounces@xxxxxxxxxxx

---

A: Eclipse Orbit (not Eclipse.org) 

We (or I?) have been remiss. 

The Simultaneous Release requirements call for "Provider Name"
to be 'Eclipse' followed by the project name. And this isn't a new requirement
.... its been since Galileo!. I've written a full account at 

http://wiki.eclipse.org/Adding_Bundles_to_Orbit#What_to_use_as_Provider_Name.3F

This value doesn't show up too many places, but does in the "Installation
Details" pages. 

Q. Should we change now? at this point in the release? 

A. Yes, if feasible, and if can safely be done before our first RC (preferably
before our milestone delivery this Friday). 

I have opened bug 309696 to track. 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=309696

Radical, eh? Normally, I'd be the first person to be against "UI Changes"
this late .... but ... that's what we said last year, about this same time,
and since no changes occurred all year long, I think this is an area that
we need to "push" on a little. 

So, don't do anything you feel is risky but if you do have time to change
"Eclipse.org" to "Eclipse Orbit" this is one time I
would not complain. And by "... have the time ... " I mean have
the time to make the change and then also follow up a few hours later,
to make sure you didn't break the build, that your bundle builds as expected,
is the same as before except for the one change, etc. 

We won't be "perfect" this year, but hope to at least get a good
start for this Helios Release, and then finish up early next cycle. 

BTW, I was reminded of this over the weekend, while examining some problematic
JUnit tests in another project ... I saw a third party bundle that didn't
look very well formed, not following our usual high standards ... and then
realized that particular third party bundle did not come from Orbit. This
made me think that we can take pride in providing our "built by Orbit"
stamp of approval on third party bundles, by identifying our bundles as
provided by "Eclispe Orbit". 

Thank you, 





_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev

_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev