jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edgar Poce (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-227) move core module to a subdirectory
Date Fri, 07 Oct 2005 14:47:04 GMT
    [ http://issues.apache.org/jira/browse/JCR-227?page=comments#action_12331599 ] 

Edgar Poce commented on JCR-227:
--------------------------------

> furthermore, the stuff in contrib is not just 'playground' stuff, but subproject people
use (rmi, jdbcpm, etc). 
> so renaming this to sandbox feels a bit awkward. 

In many apache projects the sandbox is not just a 'playground', it's a place for preparing
projects for inclusion in a release, either in the main project or as an independent library.
 Then I think it's a good idea to rename contrib to sandbox and move out those projects that
are candidates to be included in the first release. Creating a sandbox will give users a better
idea of the current state of each subproject.

> The contrib projects should be graduated into independent projects if they start having
their own 
> release cycles with the associated tags and brances. 

Well, I'm not sure whether each subproject should have its own release cycle. It might lead
to fiefdoms and lack of support in some subprojects. I mean that if each subproject has its
own release cycle the maintainer of project A wouldn't care about fixing bugs of project B.
I prefer a relasease that include the core and subprojects, see option A) below. 
Note that it doesn't mean that it will be distributed as a single jar, a distribution layout
may include many libraries.

A binary distribution 
/bin
  start-rmiserver.bat
  start-webdavserver.bat
  stop-rmiserver.bat
  stop-webdavserver.bat
 ....sh
/ext
  textfilters.jar
/doc
 ...
/lib
  jackrabbit-1.0.jar
  jcr-rmi-1.0.jar
  jcr-server-1.0.jar
  dependency-....jar
  ....


regarding svn layout I prefer to keep it as standard as possible 
see http://svnbook.red-bean.com/en/1.1/ch05s04.html#svn-ch-5-sect-6.1
With unified release cycle
A)
/jackrabbit
    /branches
    /tags
    /trunk
      /core
      /jcr-rmi
      /jcr-server
      /sandbox
        /...

And if there's consensus for independent relase cycles, I think we should keep it standard
too
B)
/jackrabbit
  /core
    /branches
    /tags
    /trunk
  /jcr-rmi
    /branches
    /tags
    /trunk
  /sandbox
    /branches
    /tags
    /trunk
  /...


> move core module to a subdirectory
> ----------------------------------
>
>          Key: JCR-227
>          URL: http://issues.apache.org/jira/browse/JCR-227
>      Project: Jackrabbit
>         Type: Wish
>   Components: maven
>     Reporter: fabrizio giustina
>     Assignee: Jukka Zitting
>     Priority: Minor
>      Fix For: 1.0

>
> Actually the jackrabbit svn holds the code for the main module in the top level dir
> http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/
> and all the subprojects in subdirectories
> http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/contrib/
> given this layout is not possible to checkout from svn only the main module (if you get
trunk, you get all), and you can't work to different modules using any IDE which doesn't support
nested projects (namely Eclipse).
> I would like to request moving the main module (that means moving all the files and directories
in trunk except "contrib") from 
> http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/
> to 
> http://svn.apache.org/repos/asf/incubator/jackrabbit/trunk/jackrabbit
> following the usual organization of maven-based projects and solving these problems...

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