Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 313052

Summary:	capability feature contribution is ignored
Product:	[Technology] Subversive	Reporter:	David Williams <david_williams>
Component:	Update Site	Assignee:	Igor Burilo <igor.burilo>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description David Williams

2010-05-16 22:28:44 EDT

Its come to my attention you contribute a "capability feature" to helios aggregation. With the current builder and process, features that end with ".capabilities" are ignored. 

See bug 306315 for some history, and why this changed from last year. 

Even if we change builders, and the feature then picked up, I'd suggest you not use or count on a feature that ends with ".capabilities". One reason, is that does leave it "installable" from the Eclipse SDK install UI, and typically, these features/bundles are not the kind of thing that end-users should be installing. They are more for products to install. 

You can instead, just "document" your capability bundles or scheme. Also, if you just have a bundle or two to contribute to the common repo, you can use <bundle > tag in your .build file. 

For examples, see 
http://wiki.eclipse.org/WTP_Capabilities_Helios, or 
http://wiki.eclipse.org/DTP_Capabilities_Location

Comment 1 Igor Burilo

2010-05-17 04:24:29 EDT

David, thanks for noting for this. Just to be sure that I correctly understand what should be done:
1. Delete org.eclipse.team.svn.ui-feature.capabilities from SVN repository (as we don't need it any more)
2. Declare capabilities through 'bundles' instead of 'features' in .build file
3. Add notes/wiki about capabilities

Comment 2 David Williams

2010-05-17 08:51:49 EDT

(In reply to comment #1)
> David, thanks for noting for this. Just to be sure that I correctly understand
> what should be done:
> 1. Delete org.eclipse.team.svn.ui-feature.capabilities from SVN repository (as
> we don't need it any more)
> 2. Declare capabilities through 'bundles' instead of 'features' in .build file
> 3. Add notes/wiki about capabilities

Well, it depends. Certainly '3' is correct. 2 is maybe correct, depending on 1. And '1' ... You might actually need it in your own repository, depending on how you "get it in there" in the first place. In WTP, I have a special repo that I build just for capabilities, and some other things, that end-users or others normally don't know about, and that is what allows me to use 'bundles' in the helios webtools.build file, but that special repo does have some 'feature(s)' in it. I'm sure there's ways to create it without ... but, not exactly sure how to do that. The point is, before you can use 'bundle' tag in your helios svn.build file, that bundle has to get in the repository you say it is in. 

For WTP, I thought important to include in common repo since we do actually make use of those bundles in an EPP package. Do you know if anyone actually uses your bundle from the central repo? It hasn't been there, for months, so I sort of doubt it, or people would have said something. 

Perhaps the easiest way for you is just to document on a wiki page what capabilility definitions are in your bundle, and leave it at that? People can copy/paste this information in their .product definitions if/when they need it for a product.

Comment 3 Igor Burilo

2010-05-18 04:24:09 EDT

David, thanks for explanation. I added wiki page and removed capabilities from subversive build file.