JSR014 implementation (generics-enabled compiler) setup not working?

I have never used the generics-enabled compiler (JSR014 early access) setup tool. I used it today, in build #3212, and it did not set up my paths correctly. I had to add gjc-rt.jar to my library path manually, for my Set to resolve without IDEA marking the ]]> as an error.

Am I doing something wrong, or should I file an issue about this?

11 comments
Comment actions Permalink

I guess the stuff is outdated and rarely needed this time 5.0 is out already.
I think we should just drop it.

-


Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

I have never used the generics-enabled compiler (JSR014 early access)
setup tool. I used it today, in build #3212, and it did not set up my
paths correctly. I had to add gjc-rt.jar to my library path manually,
for my Set<String> to resolve without IDEA marking the <String> as an
error.

Am I doing something wrong, or should I file an issue about this?




0
Comment actions Permalink

I'm using it to develop IDEA plugin. Is there another way to use generics for IDEA plugin?

0
Comment actions Permalink

... what makes me think: how about retroweaver integration in IDEA? A simple checkbox in the "compiler" configuration, and have all your class files retrofitted after compilation?

0
Comment actions Permalink

Hello Keith,

KL> I'm using it to develop IDEA plugin. Is there another way to use
KL> generics for IDEA plugin?

Sure, i'm develop my plugins for JDK 1.5 and compile into JDK 1.4 compatible
code.
Just add -target jsr14 into compiler args string.

Also this ANT script can make it automaticaly:
http://www.intellij.org/twiki/bin/view/Main/PluginANTScript

Thanks!
--
Alexey Efimov, Java Developer
Tops BI
http://www.topsbi.ru


0
Comment actions Permalink

I've tried Retroweaver multiple times and it worked never. Always I got
other errors, even with a very simple Generics example.

Tom

0
Comment actions Permalink

Just wondering, how do you deal with 1.5 specific APIs? I'm thinking
about simple things like 'String.contains()' that I would use without
thinking, being tricked by being in the "I'm writing 1.5 code" mode.

Thanks,

Vince.



0
Comment actions Permalink

RetroWeaver converts many 5.0 API's to their 1.4 counterparts during its
retro-weaving. I don't know if it handles String.contains. Anyway, RetroWeaver
checks all of your method calls and class references and makes sure your
code works on 1.4 VM.

-Keith

Just wondering, how do you deal with 1.5 specific APIs? I'm thinking
about simple things like 'String.contains()' that I would use without
thinking, being tricked by being in the "I'm writing 1.5 code" mode.

Thanks,

Vince.




0
Comment actions Permalink

Hi Tom,

If you're having problems with Retroweaver, just let me know. There are many projects using it successfully (Resin, MapInfo, FindBugs, ScheduleWorld, to name a few...) , so I get the feeling you're running into something simple, like a configuration problem.

There are discussion forums and bug trackers for Retroweaver at http://sf.net/projects/retroweaver. You can always just e-mail me directly, too.

God bless,
-Toby Reyelts

0
Comment actions Permalink

Retroweaver automatically handles compiler-generated uses of 1.5-only features like StringBuilder and the primitive valueOf() methods.

For all other 1.5-specific APIs not handled automatically, Retroweaver generates warnings (on fields, methods, and classes), so that you don't accidentally tie yourself to 1.5.

God bless,
-Toby Reyelts

0
Comment actions Permalink

Thanks for the follow-up. I will do so next time.

Tom

0

Please sign in to leave a comment.