Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353424 - package names for eclipselink.utils.sigcompare are non-conformant
Summary: package names for eclipselink.utils.sigcompare are non-conformant
Status: RESOLVED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-29 11:00 EDT by Eric Gwin CLA
Modified: 2022-06-09 10:19 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Gwin CLA 2011-07-29 11:00:51 EDT 
The other utils use a package format of "org.eclipse.persistence.util...", while the eclipselink.utils.sigcompare utility uses "eclipselink.utils.sigcompare"

This is non-conformant on both a project and "java standards" level: packages typically start with org, com, or company/organization name, not a product name. I'm not certain of the Eclipse Foundation specific rules, but I believe that all code for a project should begin with the "project package name" in our case "org.eclipse.persistence"

The question at this point is: Was it done on purpose? If so why?
Comment 1 Martin Grebac CLA 2015-03-06 08:34:32 EST 
Not correct, but I don't think we should be changing this now without other needs to touch this.
Comment 2 Eclipse Webmaster CLA 2022-06-09 10:19:04 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink