History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: GRVY-584
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dmitry Krasilschikov
Reporter: John Stalker
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Groovy

Caching of Groovy2Java .java files leads to NullPointer exception

Created: 18 Oct 07 19:39   Updated: 30 Oct 07 19:12
Component/s: None
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Environment: OS X 10.4.10 (on 2x 3GHz Dual-Core Intel Xeon, 5GB ram) java 1.5.0_07-164, intellij idea 7.0 (build 7361), jetGroovy plugin 0.1.11638, Groovy 1.0

Build: 11,638


 Description  « Hide
I have a Java project configured with the groovy facet.
The sources have a script at the root and a package hierarchy with .groovy (class) files.

This is the wierdness:

So, I've started having to delete the generated java files from:
~/Library/Caches/IntelliJIDEA70/compiler/<projectsomething>/.generated/Groovy_to_java_source_code_generator/<projectsomthingelse>/
and the .class files from the project's compile output path almost every time I make a change.

The first time I run the script, everything goes smoothly.
The 2nd time (even without changing a line of code) I get NullPointerExceptions complaining I'm trying to operate on a null object.

What's happening when I step through the code leading up to this is that the method which returns a new object, creates it and populates it just fine, but when that object is returned, the variable that should reference this new object is null.

Then I delete the generated files and class files...everything is works fine...until the next run.

Hope this makes sense.



 All   Comments   Work Log   Change History      Sort Order:
John Stalker - 19 Oct 07 22:06
GRVY-581 details the behavior by which these null pointers are occurring.

John Stalker - 22 Oct 07 22:50
Upgraded both IntelliJ to 7.0.1 (build # 7364) and jetGroovy to 0.1.11732, but the same problem exists.