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

Bug 484694

Summary:	Naming Convention should not refer to subproject
Product:	Community	Reporter:	Etienne Juliot <etienne.juliot>
Component:	Process	Assignee:	Eclipse Management Organization <emo>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows NT
Whiteboard:

Description Etienne Juliot

2015-12-18 09:50:21 EST

This page https://wiki.eclipse.org/Naming_Conventions refers to "subproject" principle which don't really exist anymore, as the EDP has been modified several years ago to just deal with "projects".


eg : 
The first package name segment after org.eclipse is generally the subproject name,
->
The first package name segment after org.eclipse is generally the project name,


Another minor update: "Sun's package naming guidelines;" -> "Oracle's package naming guidelines;" or "Java's package naming guidelines;"

Comment 1 Wayne Beaton

2015-12-18 11:35:39 EST

You know that it's a wiki, right?

:-)

Comment 2 Wayne Beaton

2015-12-18 11:39:21 EST

Search and replace for the win!

FWIW, the EDP does define subproject as equivalent to project. However, I tend to agree with you anyway and prefer to use "project".

Comment 3 Etienne Juliot

2015-12-21 03:46:07 EST

I know it is a wiki, but as it is something similar to best practices or guidelines, and as it is relative to naming used in EDP, I was not confident to modify it without your review.
Thanks.