Getting langtools into Maven Central

[Jesse Glick]

On 12/29/2011 12:07 PM, Joe Darcy wrote:
> javac in OpenJDK 6 has had a proper superset of the fixes in Oracle JDK 6 since OpenJDK 6 includes a large
> batch of fixes inherited from its JDK 7 lineage.

I stand corrected. Still, it may be missing some fixes made in 7, and offers no _advantage_ over OpenJDK 7's javac that I know of, so it would be simpler to just publish 
7.x artifacts.

>> Even if you want to build for JDK 6, you can use javac from OpenJDK 7 safely
>
> Don't forget to set the bootclasspath too!

Right, you can always do this, though it is unnecessary if the target API platform version matches that of the JRE you are actually running the tool on. For example, when 
calling JSR 199 via OpenJDK 7's langtools on a 1.5 JRE, the default bootcp would be that of Java 5 anyway.

> The proper way to use JSRs 199 and 269 on JDK 5 would be to compile those APIs into a separate jar file.

Agreed, and that is what my original message suggested - putting the 199/269 APIs (javax.**) into one artifact (they seem to form a dependency cycle so cannot be further 
divided), and the rest (com.sun.**) into one or more implementation artifacts.