Re: [ecf-dev] ECF 3.5 top-level features...for target platform usage

[Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>]

FWIW, the convention for the Target Component features has been to include the source in the feature.  The idea being that someone wanting to use say "ECF" would add the ECF Target Components to their target.  This would come with the bundles, source and perhaps a set of features.  The features in there are used to slice and dice your function in ways that people commonly use to deploy in their applications/systems.  So you could have a Remote Services features in there that points just to the binary bundles need for remote services. Then consumers could use that directly in their product definitions etc.

One of the main goals of this structure has been to make it easier for people to get started with a project.  From the beginning they do not necessarily know what they want other than wanting ECF.  Using this approach they can just add the ECF Target Components to their target and explore.  Having a small number (e.g., one per project) of these makes if very easy for people to put together the relevant target.

As a point of interest, what does the "for Eclipse" part of these names mean?  For example, "Source for ECF Target Components *for Eclipse*"? 

Jeff

On 2011-03-04, at 10:20 AM, Scott Lewis wrote:

> Hi Folks,
> 
> I've created this bug to track this short-term effort [1].
> 
> I've made several changes, and now the top-level (categorized) list of features looks like this:
> 
> Eclipse Communication Framework (ECF)
>    ECF 3.5 Patch for Eclipse
>    ECF Remote Services Target Components <-- NEW
>    ECF Target Components for Eclipse
>    Source for ECF 3.5 Patch for Eclipse
>    Source for ECF Target Components for Eclipse
> 
> 
> The new one is the 'ECF Remote Services Target Components'.   This is *just* the org.eclipse.ecf.remoteservices.sdk.feature feature.  Note that this feature is *included* in the ECF Target Components for Eclipse (formerly the whole ECF SDK)
> 
> Install into Eclipse of this new feature works fine, but install into the target platform (i.e. new Software Site), does not work with the 'Include required software' checked...I *think* because of the problem in the PDE target platform loader with versions as mentioned by Markus previously on this thread.  What I see when I try to do this (install ECF Remote Services Target Components with 'Include required software' checked) is p2 dependency errors...unfortunately I can't copy/paste them from the dialog, but they look like this (this is the first one...there are others that are 'downstream'):
> 
> Cannot satisfy dependency:
>    From: ECF OSGi Console Provider <version>
>    To: package org.eclipse.ecf.core 0.0.0
> <more cannot satisfy dependencies>
> 
> I've attached the screenshot to the bug [1].
> 
> The upshot is that unless someone has ideas about a fix/workaround for this, I think we're going to have to ask people to uncheck the 'Include required software' button on the Target platform add.
> 
> One other (relatively minor) thing...I tried to add the 'Source for ECF Remote Services Target Components' feature to the top-level category above and it doesn't seem to want to appear.  The source is generated, and it does appear in the list if the 'Categorize' is removed, but I can't get it to appear in the categorized list as above.  If anyone knows why this is not happening, then we can fix it on bug [1].
> 
> Scott
> 
> 
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=338574
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev