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

Bug 368766

Summary:	Custom modules should appear under "Eclipse Projects" on the module configuration screen
Product:	Community	Reporter:	Wayne Beaton <wayne.beaton>
Component:	Project Management & Portal	Assignee:	Portal Bugzilla Dummy Inbox <portal-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	nathan
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:
Bug Blocks:	363868

Description Wayne Beaton

2012-01-16 15:06:13 EST

There is currently an "ECLIPSE.ORG - CUSTOM" grouping. This name should be "Eclipse Projects"

Eclipse features found under "FEATURES", should be moved under the "Eclipse Projects" grouping. This includes "Project Feature" and "Release Feature" (currently under "FEATURES"). 

Further, the fact that Projects and Releases are implemented using Features is irrelevant; the word "Feature" should not occur in the module name.

Comment 1 Nathan Gervais

2012-01-16 16:12:50 EST

Moving Feature based modules is not something that can easily be changed through the UI. I have a feeling that moving these features out of the "Features" group will be overriden every time the feature is recompiled.

Also i'll have to recreate the features from scratch in order to change the feature name to drop the _feature string.  As I can't change the machine name of the feature (easily).  I'll need to spend some time seeing if i can just change this string in the code.

I've updated the "Eclipse.Org - Custom" for those modules.

Comment 2 Wayne Beaton

2012-01-17 15:25:51 EST

I did a little experiment. Apparently, you can just change the values in the .info file and the Features module honours it. At least that's what I've observed.

Comment 3 Nathan Gervais

2012-01-18 14:31:25 EST

I've committed these changes to the repo.  Marking as FIXED