Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368742 - Rename packages from *test* to *tests* in order to meet Eclipse naming conventions
Summary: Rename packages from *test* to *tests* in order to meet Eclipse naming conven...
Status: CLOSED WONTFIX
Alias: None
Product: EMFStore
Classification: Modeling
Component: Common (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-16 12:04 EST by Max Hohenegger CLA
Modified: 2018-06-08 05:58 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Max Hohenegger CLA 2012-01-16 12:04:36 EST
Naming conventions for Java Packages:
http://wiki.eclipse.org/Naming_Conventions#Java_Packages
Comment 1 Max Hohenegger CLA 2012-01-17 09:34:49 EST
According to the Naming Conventions the segment "tests" should be placed between subproject and component:
org.eclipse.<subproject>.tests.<component>[.*]

For example like this:
org.eclipse.emf.tests.emfstore
Comment 2 Eclipse Genie CLA 2016-06-16 12:55:43 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2018-06-07 11:57:41 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.