Difference between revisions of "Project Structure and Naming"

Latest revision as of 16:31, 25 April 2011

All project names in the component must follow Eclipse guidelines for naming
There should be as few projects in a component as possible. The preference would be to have one core project plus one unit test project. The decision to add additional projects is based on architectural considerations (e.g. the need for separable plugins).
JAR (and WAR, etc.) files should be named "higgins-<component>-<subcomponent>.major.minor.service.qualifier.jar (see Version Numbering for details)
- test JARs include -test before .major.minor.service.qualifier
- example: "higgins-idas-test.0.7.103.jar" - see special instructions below

@@ Line 1: / Line 1: @@
+{{#eclipseproject:technology.higgins|eclipse_custom_style.css}}
 *All project names in the component must follow Eclipse guidelines for naming
 *There should be as few projects in a component as possible. The preference would be to have one core project plus one unit test project. The decision to add additional projects is based on architectural considerations (e.g. the need for separable plugins).
@@ Line 5: / Line 6: @@
 **example: "higgins-idas-test.0.7.103.jar" - see special instructions below
-====While Higgins is in the Incubation phase ====
+[[Category:Higgins 1.x Developer Info]]
-* All downloadable zip files for builds and milestones must include the word "incubation" in the filename. For example, DSF-SDK-incubation-N20070413-0200.zip
-* The jar files in the download zip file are not required to contain the word "incubation" in the filename. (See bug 178944 for the explanation.)
-* All "Bundle-Name"s must include the world "incubation". Note that "Bundle-SymbolicName"s should not include "incubation" because the Bundle-SymbolicName is a technical namespace, not a user namespace. For example, Bundle-Name: Foo Plug-in (Incubation)
-* Similarly, the names for update manager features must include the word "incubation". For example, Eclipse Platform (Incubation)