jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Angela Schreiber <anch...@day.com>
Subject Re: [jira] Created: (JCR-612) Restructure the Jackrabbit source tree
Date Mon, 30 Oct 2006 10:59:28 GMT
hi jukka

> The main rationale is to simplify the project structure for setting up
> things like continuous builds and integration with Continuum. The most
> straightforward structure for such use is to have each component in a
> top-level subdirectory named after the artifactId.

ok... but in this case, i would prefer to combine JCR-417 and
your one-level approach.

without having a closer look at it, i could imagine the
following structure:

+ jackrabbit
   + webdav
   + webapp     (repository-access etc., no dav-servlets).
   + jcr-server (2 implementations; to be split later on; maybe rename)

this would mean:

- one top-level 'webdav'
- integrate 'client' classes into the 'webdav' project
- integrate that impl. independant part of 'server' into the webdav
- create 'webapp' project (but moving the implementation servlets
   out and into 'jcr-server'... i don't know if this is feasible...)
- 'jcr-server' would then only contain the implementations and
   the servlets and could be split in a separate step.
   (the original reason for JCR-417 was to clarify the difference
   between the 2 implementations).

what do you think?

> However, I'm not too attached to this requirement, so it's no problem
> if you want to keep the current jcr-server structure or go forward
> with JCR-417.
> BR,
> Jukka Zitting

View raw message