DataNucleus JIRA is now in read-only mode. Raise any new issues in GitHub against the plugin that it applies to. DataNucleus JIRA will remain for the foreseeable future but will eventually be discontinued
Issue Details (XML | Word | Printable)

Key: NUCCORE-906
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andy Jefferson
Reporter: Max Ross (App Engine)
Votes: 0
Watchers: 1

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

Expose class and line number information for incorrect annotations in enhancer exceptions.

Created: 22/Aug/12 05:32 PM   Updated: 28/Aug/12 09:56 AM   Resolved: 25/Aug/12 03:15 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 3.1.1

 Description  « Hide
In order for IDEs to be able to highlight issues with annotations directly in the source, it would be useful for exceptions thrown by the enhancer to include class and line number information.

Sort Order: Ascending order - Click to sort in descending order
Andy Jefferson added a comment - 25/Aug/12 03:15 PM
SVN trunk now has
InvalidClassMetaDataException, InvalidMemberMetaDataException as subclasses of InvalidMetaDataException, and provide getters for the class/member name that has the problem with metadata. Try those and see if it gives what is needed.

Note that the metadata parse process always stops at the first exception (always has) rather than trying to process all of the metadata and throwing an exception with all of the actual problems nested under it; that would be much more work (e.g DN 3.2).

Note that the enhancer remains at 3.1.0 and it is datanucleus-core, datanucleus-api-jdo, datanucleus-api-jpa involved here.

Report any log message that is not formatted correctly since this involved changing the order of parameters into many messages