spring-loaded icon indicating copy to clipboard operation
spring-loaded copied to clipboard

Update for jdk1.7.0 >= u25: use CallerSensitive annotation

Open oleastre opened this issue 12 years ago • 7 comments

I had like many others problem running grails applications using the latest jdk version.

As I still have problems with the fedora openjdk (based on and early icedtea 2.3.10), I tried to replace the getCallerClass(depth) calls with the new CallerSensitive annotation (see http://openjdk.java.net/jeps/176).

This pull request is a proof of concept that breaks compatibility with older jdk releases, but can be useful for future jdk updates.

Tests seems to pass and grails applications are running correctly.

oleastre avatar Jun 28 '13 22:06 oleastre

Please can you explain better what I have to do? Sorry for my ignorance, I'm really disappointed for this bug.

ghost avatar Jul 18 '13 12:07 ghost

I suppose you are coming from the grails bug report.

You can either try to clone my branch of spring-loaded, compile and package it yourself. Or use the jar file I putted there: http://www.oleastre.be/export/springloaded-1.1.3.jar (without any warranty it works)

Then replace the grails 2.2.3 springloaded jar with the new one (as explaine in grails jira.)

oleastre avatar Jul 18 '13 22:07 oleastre

On 19 July 2013 00:03, Olivier Samyn [email protected] wrote:

I suppose you are coming from the grails bug report.

You can either try to clone my branch of spring-loaded, compile and package it yourself. Or use the jar file I putted there: http://www.oleastre.be/export/springloaded-1.1.3.jar (without any warranty it works)

Then replace the grails 2.2.3 springloaded jar with the new one (as explaine in grails jira.)

I don't find springloaded-1.1.3.jar but

./lib/org.springsource.springloaded/springloaded-core/jars/springloaded-core-1.1.3.jar

ghost avatar Jul 18 '13 22:07 ghost

yesssssssssssssss, I've copied and renamed to springloaded-core-1.1.3.jar your file and all seems to work. Really thank you soooooooooo much :)

ghost avatar Jul 18 '13 22:07 ghost

I'd rather not break the behaviour on the older JDKs at the moment, so we need a fix that doesn't cause that problem. But I guess I could put this into a branch of the main repo as I'm not sure when I'll have time to do a proper solution that supports old and new jdk levels.

aclement avatar Jul 22 '13 17:07 aclement

Hi, Is there any news/update for this problem?

rascio avatar Dec 10 '13 12:12 rascio

So the this solution is above written by oleastre ? :-D

arthinking avatar Mar 09 '15 08:03 arthinking