jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-612) Restructure the Jackrabbit source tree
Date Fri, 17 Nov 2006 10:44:38 GMT
    [ http://issues.apache.org/jira/browse/JCR-612?page=comments#action_12450693 ] 
angela commented on JCR-612:

uuuuuuuuuuuuuuuh....... and i was waiting for an ok... since my suggestion would lead
to quite some move and restructuring of the jcr-server and i was not sure, if this
was ok for everybody.

the suggestion was:

----< copy from dev-list mail >-----------------------------------------------------------------------------------

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). 

----< copy from dev-list mail >-----------------------------------------------------------------------------------

kind regards

> Restructure the Jackrabbit source tree
> --------------------------------------
>                 Key: JCR-612
>                 URL: http://issues.apache.org/jira/browse/JCR-612
>             Project: Jackrabbit
>          Issue Type: Improvement
>            Reporter: Jukka Zitting
>         Assigned To: Jukka Zitting
>             Fix For: 1.2
>         Attachments: pomParent.zip
> Reintroduce some of the changes in JCR-157 as a more general restructuring to simplify
the Jackrabbit project structure. See http://thread.gmane.org/gmane.comp.apache.jackrabbit.devel/9170/
for the rationale and discussion. The main parts of this restructuring would be:
> 1. Create a Jackrabbit "super-project" (artifactId: jackrabbit) in trunk/
> 2. Use the super-project POM as the parent of all Jackrabbit component POMs
> 3. Move the contents of trunk/jackrabbit/src/site directly to trunk/src/site, and use
the super-project to generate the web site
> 4. Create independent subprojects for the the jackrabbit-api and jackrabbit-commons components,
moving the the corresponding parts of the source tree
> 5. Move the jcr-server subprojects on level up
> 6. Rename the subproject directories to match their artifactIds
> Note that this restructuring depends on JCR-611 and JCR-332, since the best way to implement
this by utilizing a snapshot repository for the component dependencies.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message