Re: [rt-pmc] SDKs, Target Components and all that...

[Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>]

Hugues, 

The JUnit feature seems to be something that should just be in the Jetty Target Components feature.  Users should get the Target Components, add it to their target and then have the Junit feature availalbe to be added to launch configs and products.

If you are intending the junit feature to be used more widely then we should talk about generalizing it to remove the OSGi bits (they should be included in whatever product/configuration is being tested) and position it accordingly. In that case, simply "PDE JUnit Support" is fine.  

The discussion around "Target Components" was not that everything in the category should be called that rather that that term should be used instead of SDK.

Jeff

On 2010-05-19, at 1:18 PM, Hugues Malphettes wrote:

> I have updated the jetty sdk's feature name to "Jetty Target Components".
> The other feature that jetty publishes is the support for PDE's JUnit
> runner in a Target Platform.
> It is described in this bug:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=313202
> It was called "PDE's JUnit Runner Support"
> 
> What should we call it?
>    "PDE's JUnit Runner Target Components" ?
> 
> Thanks,
> Hugues
> 
> 
> On Wed, May 19, 2010 at 8:08 AM, Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx> wrote:
>> There has been discussion around the naming/positioning of the elements in the Helios repository intended to be added to people's target platforms.  In the past teams have contributed "SDKs" to the EclipseRT Target Platform Components category.  This has caused confusion as many people in the community think of SDKs as something that gets installed into the IDE. In an effort to clarify the situation for users the RT PMC decided that the elements of the EclipseRT Target Platform Components category in the Helios repo should appear as
>>        XXX Target Components
>> So, for example, "Equinox Target Components", "RAP Target Components" etc.
>> 
>> This gives clarity to the consumers and accurately positions the elements as something that is used to compose a target platform.
>> 
>> We ask that projects contributing to the Target Platform category in Helios change the *name* of their contributed features as soon as possible so that the RC repos can be tested for consistency.  NOTE that you do NOT have to change the feature ID or feature structure, just the human readable feature name (likely in the feature.properties files)
>> 
>> Thanks for your understanding and help on this.  Please post here if you have a situation that somehow does not fit with this approach.
>> 
>> The RT PMC
>> 
>> 
>> _______________________________________________
>> rt-pmc mailing list
>> rt-pmc@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>> 
> _______________________________________________
> rt-pmc mailing list
> rt-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/rt-pmc