Hi all,
By implementing SLING-268 [1] the launchpad-servlets module is broken up
into the sling/servlets-default and sling/ujax modules, leaving just the
launchpad-content and launchpad-webapp modules in launchpad. In
addition, there are the launcher modules app and webapp.
The next then will be to merge the launcher modules into the launchpad
folder. Doing this I imagine, there will be the following modules in the
launchpad folder:
app - Standalone launchpad application
webapp - Launchpad Web Application
(renamed from launchpad-webapp)
content - Initial Launchpad content
The app and webapp modules will have three build profiles:
bare - (default) Launcher only (OSGi framework; Log,
HttpService and Sling Console bundles)
full - Same as "bare" plus all bundles required for
a productive Sling system
launchpad - Same as "full" plus launchpad/content,
samples and documentation
The difference between "full" and "launchpad" is, that full may be used
as the basis for any productive system without the payload of
demonstration, educational and documentation bundles. The "launchpad"
build is targeted at the "getting-to-know" audience and will include
these
demonstration, educational and documentation bundles.
Talking about "demonstration, educational and documentation" bundles,
what will these be ? These are the (current) sling/sample and
launchpad/content bundles. In addition we could also define a bundle,
which contains the sling site as well as JavaDoc and Code XRef
accessible through sling - sort of like a default Apache Httpd
installation also containing documentation.
WDYT ?
Regards
Felix
[1] http://issues.apache.org/jira/browse/SLING-268
