jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-612) Restructure the Jackrabbit source tree
Date Sun, 03 Dec 2006 23:28:22 GMT
     [ http://issues.apache.org/jira/browse/JCR-612?page=all ]

Jukka Zitting resolved JCR-612.

    Resolution: Fixed

Restructuring done! See the "Subversion Commits" tab for the extensive list of changes. The
new structure is now:


Each of these directories (including trunk) contains a Maven 2 project and a README file with
a decent summary and basic build instructions.

The inter-component dependencies are:

    jackrabbit-core: jackrabbit-api jackrabbit-commons jackrabbit-jcr-tests
    jackrabbit-index-filters: jackrabbit-core
    jackrabbit-jca : jackrabbit-core
    jackrabbit-jcr-server: jackrabbit-commons jackrabbit-webdav
    jackrabbit-webapp: jackrabbit-core jackrabbit-server jackrabbit-jcr-rmi
    jackrabbit-webdav: jackrabbit-commons

I'll probably still be tweaking some details, but since all the main parts are now in place,
compile, and seem to work just fine, I'll resolve this issue as Fixed. Please file separate
bug reports for anything that doesn't work.

> 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: _restructurisationPath.zip, 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