J2ME - based on classpath
hello, i'm the guy who will implement or build a micro edition based on gnu classpath, it will be my internship at tuwien, i'll work for the same group, which is working on cacao. the result of my work should conform the CLDC/MIDP specs, and CDC (what i learned today ;)) too. the question is if the gnu classpath community will support my plan and provide me a cvs repo or a branch in the repo. i could use the cacao or my own repository too. i.e. the CLDC specs describes some constrains for the VM, those will be implemented in cacao, the limited j2me (according to CLDC/MIDP) packages will be based on classpath and should be part of it. what is the best approach, this aim can be reached? michal
Re: J2ME - based on classpath
> "Michal" == Michal Revucky <[EMAIL PROTECTED]> writes: Michal> the result of my work should conform the CLDC/MIDP specs, and Michal> CDC (what i learned today ;)) too. the question is if the gnu Michal> classpath community will support my plan and provide me a cvs Michal> repo or a branch in the repo. i could use the cacao or my own Michal> repository too. I think working on a branch in the Classpath repository would be a great idea. We'll need to get through the paperwork hurdles -- but we'll need to do that no matter what, if you want to eventually merge this code in. Tom
Re: J2ME - based on classpath
On Fri, 2006-03-10 at 15:10 -0700, Tom Tromey wrote: > I think working on a branch in the Classpath repository would be a > great idea. > > We'll need to get through the paperwork hurdles -- but we'll need to > do that no matter what, if you want to eventually merge this code in. I think too the Classpath repository is the best location. The paperwork shouldn't be a problem, as Michal already did it for gforth. However, let's do that ASAP. Mark, can you send the form to Michal? TWISTI
Re: J2ME - based on classpath
Hi Christian, On Fri, 2006-03-10 at 23:44 +0100, Christian Thalinger wrote: > On Fri, 2006-03-10 at 15:10 -0700, Tom Tromey wrote: > > We'll need to get through the paperwork hurdles -- but we'll need to > > do that no matter what, if you want to eventually merge this code in. > > I think too the Classpath repository is the best location. The > paperwork shouldn't be a problem, as Michal already did it for gforth. > However, let's do that ASAP. Mark, can you send the form to Michal? Paperwork sent. Thanks for the reminder. Mark signature.asc Description: This is a digitally signed message part
