...
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Grouper API dev env
The API needs the client source and configs as linked source folders (e.g. for eclipse). This makes sure the current version of the configs and classes are in use when running tests or programs or compiling API source.
| Gliffy Diagram | |||||
|---|---|---|---|---|---|
|
Grouper-box dev env
This an example of a non-web plugin for Grouper. Pretty much all modules for Grouper look like this (except web modules like UI/WS/scim). It generally depends on the API (and transitively client).
| Gliffy Diagram | ||||||
|---|---|---|---|---|---|---|
|
Grouper UI dev env
This is an example of the UI dev env. Note other webapps (WS/scim) will look similar. There is no build script to run Tomee against the webapp, it will just work. When you edit Java classes you might need to restart Tomee (due to hotswap)
The example commands and screenshots are from MacOS and Eclipse, and may vary slightly for different environments. However, the overall process should be similar on any modern operating system and development tool chain. Developers can use whatever tools that let them work most efficiently.
...