Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of mloenko@gmail.com designates
 66.249.92.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=CyEpv0IgoYzyr87XAPbAEKQllybYreqnxOvZVtI5azIPXo7exjWiL92L/BTx1tLItKoz1vNBHo9Y3QQMpVIFPFHrAKFjMLcrzHuspIXYRV4Qgo9+sk5Np82RBxiqhAWDvJCvluwEr6mhtVO+yce/u4B25Q9IF7gcNW5Q+FjK3Wg=
Message-ID: <906dd82e0606051940id5557a1ha050d6a72fa2ddc9@mail.gmail.com>
Date: Tue, 6 Jun 2006 09:40:27 +0700
From: "Mikhail Loenko" <mloenko@gmail.com>
To: harmony-dev@incubator.apache.org, geir@pobox.com
Subject: Re: [general] revisiting structure of SVN
In-Reply-To: <44846324.2040908@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44846324.2040908@pobox.com>

6) move kernel classes out of classlib

possibly create /j9 directory in a root, where j9 binaries and kernel
classes will live

Thanks,
Mikhail

2006/6/6, Geir Magnusson Jr <geir@pobox.com>:
> I'd like to discuss how we start to bring together the pieces of Harmony
> given our goal is Java SE with all the fixin's.
>
> We now have
>
>  /classlib
>  /jchevm
>  /drlvm
>
> DRLVM and classlib work together (as I think we all like to see jchevm
> do too...)
>
> But given that we are a Java SE project (and not a VM project or a
> classlibrary project) I think it behooves us to start thinking how to
> organize at a higher level.  We've been very focused on the classlib
> area, but that's only one part.
>
> So, I'd like to propose something like
>
> 1) a /deploy directory in root, as a peer to /classlib and /drlvm
>
>  /classlib
>  /deploy
>  /drlvm
>
> 2) Maybe move the launcher out from classlib to
>
>  /launcher
>
> 3) Maybe create
>
>  /tools
>
>  where the tool work can happen?
>
> 4) Have /drlvm and /classlib build-deploy into /deploy, rather than the
> local one
>
> 3) create a top level script such that
>
>     build drlvm-jdk
>  or
>     build jchevm-jdk
>
> does what you expect, namely build the classlib artifacts and put in
> /deploy, build the VM of choice and drop in /deploy, builds the
> toolset,etc and go from there.  We can create our HDK snapshots from it,
> and drop HDKs into it for use :
>
>  /deploy
>     /hdk/
>        /hdk1/
>        /hdk2/
>     /jdk
>        /jre
>
> etc
>
> Comments?
>
> geir
>
>
>
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org