I thought the idea was that each contribution started working directly
in the sandbox? Isn't that what Dan and Archie are doing?
Once things are pulled out from the sandbox I propose that the
repository is laid out to represent a few (non-trivial) sub-projects
that have well-defined interaction, to allow some development autonomy,
but build together into a single system, something like:
enhanced
/classlib
/trunk
/branches
/tags
/vm
/trunk
/branches
/tags
/jit
/trunk
/branches
/tags
/build
/trunk
/branches
/tags
and so on, with further subdivision within the sub-projects are required
(e.g. ACL areas within the classlib as defined by the ACQ).
Is this the sort of thing you mean?
Regards,
Tim
Geir Magnusson Jr. wrote:
> Now that the code from IBMs contrib (HARMONY-14) is in the sandbox
> (well - it's uploading now...), we'll need to shift things around a bit.
>
> do we do something as obvious as
>
> enhanced/trunk/classlib/
>
> ?
>
> Or do we get ahead of things and do :
>
> enhanced/trunk /* for general stuff, including project build scripts
> and such */
>
> enhanced/classlib/trunk /* for HARMONY-14 and then the security code
> layered on *?
>
> ?
>
> geir
>
--
Tim Ellison ([EMAIL PROTECTED])
IBM Java technology centre, UK.
