Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.help > #946

Re: Using javac 7 to compile java 6 code

From markspace <-@.>
Newsgroups comp.lang.java.help
Subject Re: Using javac 7 to compile java 6 code
Date 2011-08-16 12:52 -0700
Organization A noiseless patient Spider
Message-ID <j2ehpc$fbm$1@dont-email.me> (permalink)
References <j2efk6$us7$1@dont-email.me>

Show all headers | View raw


On 8/16/2011 12:15 PM, Knute Johnson wrote:
> I've got some currently running code that is using 1.6 runtimes and I
> won't be able to upgrade them right away. I want to use the new compiler
> for new work and I tried using the -target and -source options but I've
> run into a snag. JList is now JList<E> and the compiler issues a warning
> even with -source set to 1.6. Is that to be expected or what? I don't
> think using the type specification with JList would compile with a 1.6
> compiler. Do I just need to ignore the warning and press on? And
> JComboBox too I found.


I think you could probably just ignore the warning.  I'd have to see the 
source code to be sure.  Alternately, you can compile against an older 
version of the Java API if you have, for example, the 1.6 rt.jar still 
installed (or just available),  I think.

-bootclasspath bootclasspath

Cross-compile against the specified set of boot classes. As with the 
user class path, boot class path entries are separated by colons (:) and 
can be directories, JAR archives, or ZIP archives.

<http://download.oracle.com/javase/7/docs/technotes/tools/windows/javac.html>

Back to comp.lang.java.help | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Using javac 7 to compile java 6 code Knute Johnson <september@knutejohnson.com> - 2011-08-16 12:15 -0700
  Re: Using javac 7 to compile java 6 code markspace <-@.> - 2011-08-16 12:52 -0700
    Re: Using javac 7 to compile java 6 code Knute Johnson <september@knutejohnson.com> - 2011-08-16 13:20 -0700

csiph-web