Issue Details (XML | Word | Printable)

Key: MGROOVY-167
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Critical Critical
Assignee: Jason Dillon
Reporter: Matthew J. Montgomery
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
GMaven (OLD)

transient modifier is not handled correctly when generating stubs

Created: 29/Oct/08 11:21 AM   Updated: 12/Jan/09 04:38 AM
Component/s: stub generation
Affects Version/s: 1.0-rc-3
Fix Version/s: 1.0-rc-4

Time Tracking:
Not Specified

File Attachments: 1. GZip Archive gmavenProbSample.tar.gz (3 kB)

Environment: Suse linux, Maven 2.0.8, Groovy Version: 1.5.4 JVM: 10.0-b19, Java(TM) SE Runtime Environment (build 1.6.0_04-b12)


 Description  « Hide
Working on a project that has both java and groovy classes.
The groovy classes utilize serialization extensively for permanence and have a significant number of transient properties to reduce the serialized footprint of the classes.

The gmaven-plugin 1.0-rc-3 is producing invalid getter and setter stubs for the transient properties. I have attached one of the Groovy classes and the generated java stub for that class in a gzipped tar file.

The errors returned are all similar to:

target/generated-sources/groovy-stubs/main/org/oclc/dataload/frequency/SimpleCount.java:[41,29] modifier transient not allowed here

Where the generated class contains code like:

transient private boolean hasFixupSimpleCountDummy = false;
transient public boolean getHasFixupSimpleCountDummy() { throw new InternalError("Stubbed method"); }
transient public boolean isHasFixupSimpleCountDummy() { throw new InternalError("Stubbed method"); } }
transient public void setHasFixupSimpleCountDummy(boolean value) { throw new InternalError("Stubbed method"); }



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jason Dillon added a comment - 12/Jan/09 04:00 AM
looks like volatile has the same problem too.