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] Commented: (JCR-612) Restructure the Jackrabbit source tree
Date Fri, 17 Nov 2006 14:04:38 GMT
    [ http://issues.apache.org/jira/browse/JCR-612?page=comments#action_12450744 ] 
            
Jukka Zitting commented on JCR-612:
-----------------------------------

> There was changelog turned on in maven1 so I made it avaiable for maven2 as well.
> It seems to be quite informative report so I would think about turning it on in core
or super project as well.

We'll probably limit the amount of reports that get generated for the public Jackrabbit web
site, but enable quite a few to be generated as a part of the nightly builds I'm going to
set up. See JCR-611 and INFRA-1008 for the progress.

> What do you think Jukka, should Angela make it real, or should I maven2 jcr-server as
it
> is at the moment?

I'm not too much of an expert on the webdav components, but Angela's plan looks good to me.
I think we should go with that.


> 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

        

Mime
View raw message