Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Project Structure and Naming"
| Line 1: | Line 1: | ||
| − | {{#eclipseproject:technology.higgins}} | + | {{#eclipseproject:technology.higgins|eclipse_custom_style.css}} |
*All project names in the component must follow Eclipse guidelines for naming | *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). | *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). | ||
Revision as of 10:09, 16 December 2008
{{#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).
- 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