Skip to content

Changes

Page history
updated namespaces authored by Michael Renoth's avatar Michael Renoth
Show whitespace changes
Inline Side-by-side
development-guidelines.md
View page @ 8394b602
......@@ -9,7 +9,6 @@ See [Development Environment Setup](development-environment-setup) for further i
The project name should be a complete identifier for the project. For example, the EnOcean Sample Client is developed in the workspace project `org.enosar.showcase.io.enocean.sample.client`. For more details see: [Eclipse Workspace Naming Convetions](https://wiki.eclipse.org/Naming_Conventions#Eclipse_Workspace_Projects)
### Namespace
The default namespace for projects within the core is located under ```org.enosar```. If you create a new project, just use the namespace within core. For example the project is called *communication* then the code will be located within the namespace ```org.enosar.communication```
The default namespace for all ENOSAR projects is ```org.enosar```. Depending on what is being developed, a sub package is selected. For core functionality use the package ```org.enosar.core``` or ```org.enosar.mgmt```, for services use ```org.enosar.service```. All internally developed applications from the ENOSAR team will be set to the ```org.enosar.application``` package.
Examples for different packages:
......