Imported From: https://issues.scala-lang.org/browse/SI-5836?orig=1
Reporter: @magarciaEPFL

@magarciaEPFL said:
And the javac.args can also target 1.6

@magarciaEPFL said:
@lrytz, your comments are welcome!

@jsuereth said:
Working on a patch for javac.target options. Not as easy as you would hope....

Also, I kinda think perhaps scalac.args for JVM target should only be for scalac.args.quickonly, so we don't run into STARR vs. locker feature issues (those are my favorite).

I should have something by the end of the week.

@magarciaEPFL said:
An idea that might prove useful:

• Use Migration Manager to keep GenASM and GenJVM mutually honest ( by comparing the output of -target:jvm-1.5-asm and -target:jvm-1.5 ).
• Actually, for API compatibility purposes, 1.6 classfiles can also be compared with 1.5 classfiles.
• Any other JAR diffing tool should also do, especially if available as ANT task

A discussion was started at scala-internals to gather feedback on this approach.

@magarciaEPFL said:
This build would be a good place to test stability. As far as GenASM is concerned the following will do:

ant quick.clean -Dscalac.args.quickonly="-target:jvm-1.5-asm" test.stability

ant quick.clean -Dscalac.args.quickonly="-target:jvm-1.6"     test.stability

@magarciaEPFL said (edited on Jul 9, 2012 9:21:45 AM UTC):
scala/scala#841 activates GenASM as default backend,
and also adds "jvm-1.6" and "jvm-1.7" as PermissibleValue in

src/compiler/scala/tools/ant/Scalac.scala 

@magarciaEPFL said (edited on Aug 3, 2012 9:19:37 AM UTC):
Now that GenASM is the default backend for 1.6 classfiles (see below) this ticket should be repurposed to 1.7 classfiles.

• commit 5a722aa57384618d9f6b8a5e288ef4763b8d8f99
• commit ee0d01785ebc7b72164ad4e0d6a952d99a5f21f2

obsolete, 2.12 has the new back end