Ivan Volosyuk wrote: > I have good idea. Let's move to eclipse compiler in classlib's build > process. :)
There are instructions in the build file for how to switch the default build compiler to use ECJ. > This will allow us to build classlib using number of available JREs1.4. The build needs a JDK that understands 1.5 syntax. Regards, Tim > -- > Ivan > > 2006/5/26, Vladimir Gorr <[EMAIL PROTECTED]>: >> On 5/26/06, Tim Ellison <[EMAIL PROTECTED]> wrote: >> > >> > Vladimir Gorr wrote: >> > > maybe does it make sense adding the RI rt.jar to CLASSPATH for the >> > > ECJ-based >> > > compiler? >> > > In this case all we didn't implemented will be taken from RI. Is >> this a >> > > stupid idea? >> > >> > You can add the RI's class libraries using a command-line option if you >> > so choose, but I don;t think we should build the Harmony javac to have >> > dependencies upon the RI. >> >> >> Ok, I see and absolutely agree with you. But I have one question :-). >> Suppose API developers will import some unimplemented (into Harmony) >> class >> for the development needs >> and build with Sun's compiler (He will see no any compiler's errors). >> Are there the dependencies upon the RI for Harmony javac in this case? >> >> >> Anyone want to get to work on j.u.Scanner ;-) ? >> >> > > --------------------------------------------------------------------- > Terms of use : http://incubator.apache.org/harmony/mailing.html > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Tim Ellison ([EMAIL PROTECTED]) IBM Java technology centre, UK. --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
