we will eventually want to reorganize things to work better with the build
system.

for example, right now we have a mostly flat namespace in the server, with
the exception of 'build'.  I suggest that each project have its own
highlevel repository, with child modules living beneith it (like how it is
checked out).

This will serve two main purposes:

 1) simplifiy the inclusing of a projects direct child modules.
    CVSROOT/modules will only have to list external modules (those from
    other highlevel projects)

 2) allowing better organization due to namespace seperation.

For example, the jboss-all project should probably be layed out like this:

 CVSROOT/

 jboss/
     build/
     server/
     naming/
     ...

The website like this:

 website/
     build/
     docroot/
     survey/
     forum/
     petstore/
     ...

The jboss-docs module is currently only a sub-set of jboss-all, so I
currently does not need any repo changes.

I am not suggesting that this be done now, or even in the near future.  I
just want to let those interested know that we should make this change
eventually, when it is most conveient.

The net effect of these changes on users will be having to pull down a fresh
copy of the project they are working on.

To make this changes is fairly simple, though it is complicated
slightly by us not having direct control over the repository files.

--jason


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to