Improve our Maven modules layout to make Sling easier to understand
-------------------------------------------------------------------
Key: SLING-83
URL: https://issues.apache.org/jira/browse/SLING-83
Project: Sling
Issue Type: Improvement
Reporter: Bertrand Delacretaz
As discussed on sling-dev [1], we'd like to restructure our source code, to
split Sling in smaller pieces and make it easier to understand what is what.
The suggested Maven modules are as follows. That's the general idea, details
will have to be filled in.
sling-api (used by both microsling and sling)
microsling
- microsling-webapp (uses sling-api)
- microsling-cargo-testing (I'm planning to write some integration tests)
sling
- sling-osgi (osgi-related modules, console, ...)
- sling-jcr (JCR utility modules, wrappers, ...)
- sling-jsp (jasper compiler, JSP script engine, ...)
- sling-core
- sling-commons (was not on the mailing list proposal, but probably useful)
- ...
sling-maven-plugins
- ... existing plugins
[1] http://thread.gmane.org/gmane.comp.apache.sling.devel/555/focus=57
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
