...
The trick is to manage dependencies correctly. Your local project will depend explicitly on the
...
dspace-api
...
project so it can import DSpace API interfaces and classes. Thus, the
...
dspace-api
...
project cannot depend on it. You have to add a dependency on your local project to every POM that generates an executable build product (i.e. the webapps, and the command-line apps). Those projects also depend on
...
dspace-api
...
so the API classes will be available.
...
*. This project contains several plugin implementations, and it has its own dependencies on some other projects which support that code. All of the classes in
...
dash-api
...
are in packages under the
...
edu.harvard...
...
hierarchy, so they do not conflict with DSpace.
...