jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcel Reutegger <marcel.reuteg...@gmx.net>
Subject Re: build problems
Date Mon, 11 Jul 2005 08:32:43 GMT
Hi all,

Jukka Zitting wrote:
> Roy is right in that the directory layout could do with some cleaning 
> up. A proposal:
> 
> jackrabbit/
>          ./api
>          ./commons
>          ./core
>          ./applications
>          ./xdocs
>          ./subprojects
>                  ./jcr-rmi
>                  ./jcr-server
>                  ./orm-persistence
>                  ...
>          ./contrib
>                  ./examples
>                  ./jcr-commands
>                  ./jcr-ext
>                  ./jcrtaglib
>                  ./phpcr
>                  ./tck-webapp
>                  ./textfilters
>                  ./vfs
>                  ...

I like the structure.

+1

> IDE and tool support
> --------------------
> 
> It would be nicer for IDEs and various tools if the current main modules 
> would _not_ extend the top level project.xml. For example at the moment 
> you cannot just grab jackrabbit/commons and build it. Instead you need 
> to get the whole Jackrabbit source tree to do this. As the top level 
> project.xml contains mostly just descriptive information not directly 
> used in building the sources, I'd propose removing this dependency. It 
> would remove the contributor and mailing list information from the 
> module projects, but I think we could manage with having that 
> information only at the top level.

also makes it easier to include one of the subprojects into another one 
with a svn:external.

+1

regards
  marcel

Mime
View raw message