Hi,
we recently discussed the new structure for our source tree. To finalize
this, I'll start this vote (lazy consensus applies).
The following is the initial setup - we can of course move a bundle to
one or the other location after the initial restructuring. But as we are
heading for a release real soon now, we should do this asap!
The outline above splits up the integration tests for the bundles and
the contrib area (both tests are in the corresponding launchpad
directories). This is in order to be able to build and test Sling
without the contrib stuff. The contrib stuff will be buildable by a
profile - as well as the example.
So please cast your votes.
trunk/
+-- maven (Maven Plugins)
+-- parent/ (Parent Project)
+-- launchpad (Launchpad Application)
+-- app
+-- webapp
+-- base
+-- bundles
+-- content
+-- tests
+-- bundles/
+-- api (The Sling API)
+-- engine (The Sling Core Engine)
+-- scripting (ScriptEngines)
+-- api
+-- core
+-- javascript
+-- jsp
+-- jsp-taglib
+-- commons (Helper libraries)
+-- log
+-- json
+-- osgi
+-- mime
+-- testing
+-- scheduler
+-- threads
+-- jcr (JCR related modules)
+-- api
+-- base
+-- classloader
+-- contentloader
+-- jackrabbit-api
+-- jackrabbit-server
+-- ocm
+-- resource
+-- webdav
+-- servlets (Servlet Support)
+-- get
+-- post
+-- resolver
+-- extensions (Extension bundles)
+-- adapter
+-- bundleresource
+-- httpauth
+-- event
+-- openidauth
+-- threaddump
+-- contrib (Contributions etc.)
+-- commons
+-- scripting (ScriptEngines)
+-- freemarker
+-- java
+-- jst
+-- python
+-- ruby
+-- scala
+-- velocity
+-- jcr (JCR related modules)
+-- jackrabbit-client
+-- launchpad (Launchpad Application)
+-- jcrapp
+-- testing (contrib stuff)
+-- extensions (Extension bundles)
+-- apt
+-- dojo
+-- dojo-sling
+-- i18n
+-- gwt
+-- jcrinstall
+-- obr (OBR Server, was osgi/obr)
+-- runmode
+-- samples
+-- ... existing samples ...
Thanks
Carsten
--
Carsten Ziegeler
cziege...@apache.org
