You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Carsten Ziegeler <cz...@apache.org> on 2009/02/17 20:58:35 UTC

[VOTE] Source Tree Restructuring

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
cziegeler@apache.org

Re: [VOTE] Source Tree Restructuring

Posted by Carsten Ziegeler <cz...@apache.org>.
I'll do the restructuring over the weekend (probably sunday), so expect
some problems during the move.


Thanks
Carsten
-- 
Carsten Ziegeler
cziegeler@apache.org

Re: [VOTE] Source Tree Restructuring

Posted by Jukka Zitting <ju...@gmail.com>.
Hi,

+1 Looks good to me.

BR,

Jukka Zitting

Re: [VOTE] Source Tree Restructuring

Posted by Tobias Bocanegra <tr...@day.com>.
On 2/18/09, Carsten Ziegeler <cz...@apache.org> wrote:
> Tobias Bocanegra wrote:
>  > just out of curiosity: why is jcrinstall not in "jcr" ? i find it
>  > awkward, that a JCR based framework keeps a JCR based bundle/config
>  > loading in "contrib" :-)
>
> :)
>
>  Actually I agree that jcrinstall should be moved into jcr but into
>  contrib/jcr :) We're moving all stuff which is not ready to be released
>  into the contrib folder and jcrinstall is one of them.
why not "promote" certain extensions ?

>
>
>  Carsten
>  --
>  Carsten Ziegeler
>  cziegeler@apache.org
>

Re: [VOTE] Source Tree Restructuring

Posted by Carsten Ziegeler <cz...@apache.org>.
Tobias Bocanegra wrote:
> just out of curiosity: why is jcrinstall not in "jcr" ? i find it
> awkward, that a JCR based framework keeps a JCR based bundle/config
> loading in "contrib" :-)
:)

Actually I agree that jcrinstall should be moved into jcr but into
contrib/jcr :) We're moving all stuff which is not ready to be released
into the contrib folder and jcrinstall is one of them.

Carsten
-- 
Carsten Ziegeler
cziegeler@apache.org

Re: [VOTE] Source Tree Restructuring

Posted by Tobias Bocanegra <tr...@day.com>.
just out of curiosity: why is jcrinstall not in "jcr" ? i find it
awkward, that a JCR based framework keeps a JCR based bundle/config
loading in "contrib" :-)

regards, toby

On 2/17/09, Carsten Ziegeler <cz...@apache.org> wrote:
> 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
>  cziegeler@apache.org
>

Re: [VOTE] Source Tree Restructuring

Posted by Carsten Ziegeler <cz...@apache.org>.
+1

Carsten

-- 
Carsten Ziegeler
cziegeler@apache.org

Re: [VOTE] Source Tree Restructuring

Posted by Juan José Vázquez Delgado <ju...@gmail.com>.
> we recently discussed the new structure for our source tree. To finalize
> this, I'll start this vote (lazy consensus applies).

+1

BR;

Juanjo.