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

Bug 340050

Summary: Need to improve "web tools" category in common repository
Product: [WebTools] WTP Releng Reporter: David Williams <david_williams>
Component: relengAssignee: webtools.releng <webtools.releng-inbox>
Status: NEW --- QA Contact: Carl Anderson <ccc>
Severity: normal    
Priority: P3 CC: kaloyan, neil.hauge, thatnitind
Version: 3.10   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Indigo M6 version of category none

Description David Williams CLA 2011-03-15 12:17:50 EDT
Created attachment 191225 [details]
Indigo M6 version of category

It has always been too long and confusing, and for Indigo its getting even longer with additional features.
Comment 1 David Williams CLA 2011-03-15 12:22:16 EDT
There's a couple of issues with naming ... a) we shouldn't really use "(Optional)" at end of feature names ... they are all optional, from an end-users point of view. (Some of this is left over from old update manager, which had the concept of optional vs. required). 

b) some of the names are meaningless or ambiguous. Any that meantion WST or JST should provide a more end-user understandable name. There are two with same name "JST Server Adapters" ... but, there is a difference, and we should name them appropriate, so an end-user would understand.
Comment 2 David Williams CLA 2011-03-15 12:30:30 EDT
The biggest issue has to do with overall length. In theory, it is possible to have subcategories, but I do not know of any easy way to implement that (in any context, and especially for b3 aggregator context). 

Another possible option is to add more top-level categories, such as breakup the "Web, XML, Java EE, and OSGI Enterprise Tools" into 4 categories. 

Another possible option is to use names to effectively convey subcategories, such as anything that would be in some subcategory such as "Java EE Tools" could just start off with the words "Java EE Tool: ... " in its name. 

Another possible option (which we've always said we should do anyway) is to create some "collecting features" that would be, essentially, only for the site repository ... one for Java EE Tools, XML Tools, Web Development Tools, etc. 

Many of these options would still leave "RAP Tooling" and "PHP Development" as their own features ... I guess in a "Web Development" type category (not, Java EE).
Comment 3 Nitin Dahyabhai CLA 2011-03-16 11:23:58 EDT
(In reply to comment #1)
> There are two with same
> name "JST Server Adapters" ... but, there is a difference, and we should name
> them appropriate, so an end-user would understand.

Aren't those different versions of the same feature?  Should there be different versions present?
Comment 4 David Williams CLA 2011-05-25 22:28:35 EDT
(In reply to comment #3)
> (In reply to comment #1)
> > There are two with same
> > name "JST Server Adapters" ... but, there is a difference, and we should name
> > them appropriate, so an end-user would understand.
> 
> Aren't those different versions of the same feature?  Should there be different
> versions present?

no, one is jst.server.adapters ... contains base infrafrastucture ... the other is jst.server.adapters.ext that contains the _old_ server adapters we "ship". Well .. also contains the new tomcat server adapters ... not all old.