Talk:DSpace Release 1.5.0 Terminology

From DSpace Wiki

[edit] LarryStone questions

• Where does the dspace-api project go?
• One concern, how do you easily integrate a simple plug-in implementation for one of the dspace-api plugin interfaces, e.g. an authentication method, or crosswalk, or packager? Typically those depend on the dspace-api project, so perhaps there has to be a parent of dspace-api and all its plugins which the applications (jspui, xmlui, lni) can depend on.
  • The application-level projects really need a single project that encompasses dspace-api; would you want to have to modify N different dependency lists every time you add a core-level addon like an authentication method?
  • Perhaps we can turn dspace-api into the "parent" or "collector" project, and put the code that's now in dspace-api into dspace-core -- then the core-level project like an authentication method addon just depends on dspace-core, and the app-level addon depends on dspace-api.

[edit] Newbie question

I'm a real newbie, so this question may not be relevant: Would it be feasible to add an empty overlay module with an example pom.xml to the directory structure alongside jspui and xmlui as an example showing people how to incorporate their own plugins?