[ http://issues.apache.org/jira/browse/JCR-612?page=all ]
Jan Kuzniak updated JCR-612:
----------------------------
Attachment: _restructurisationPath.zip
As you wish: there you have a patch with all restructurisation and maven2 poms
in one unix script. Just put directory _restructurisationPath inside trunk and
run patch.sh inside this dir and in a short while you have everything done. I
hope that I didn't miss anything.
Regards,
Jan
> 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
