How long will 1.4.2 be supported as IDEA's JVM
While moving to 1.5 certainly provides performance benefits worth the hassle, what I was really looking forward to in the 1.5 move was the improved programming model. As a plugin author, I'm assuming I can't use JDK1.5 annotations or enums, for instance, since they won't work under JDK1.4.2. What's the projected timeline for maintaining 1.4.2 support. Also, what's the build path for internally shipping plugins. Is it still degenerator+1.4 javac, or will you be moving to 1.5 javac?
--Dave Griffith
请先登录再写评论。
>As a plugin author, I'm assuming I can't use JDK1.5 annotations or enums, for instance, since they won't work under JDK1.4.2.
>
Isn't RetroWeaver the solution to this ailment?
http://retroweaver.sourceforge.net/documentation.html
Alain
Exactly. We've get rid of degenerator and using 1.5 compiler + retroweaver
currently.
As to final moving to 1.5 it wouldn't take a long most probably once we finally
have Tiger+Tiger on MacOS X.
-
Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"
>> As a plugin author, I'm assuming I can't use JDK1.5 annotations or
>> enums, for instance, since they won't work under JDK1.4.2.
>>
Get your hot Tiger-on-Tiger action here (no need for ADC membership)
http://www.apple.com/support/downloads/java2se50release1.html
Cool. Then with no small amount of trepidation, I'm updating the IG codebase to 1.5. Generify, for-to-for-each conversion, boxing/unboxing removal, removing all those casts on the now lusciously generic PsiTreeUtil methods, the works. No issues so far, except for what looks to be a known bug with the "Rendundant cast" inspection and auto-unboxing.
--Dave Griffith