You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 5, 2019. It is now read-only.
As things are, generated classes use simple naming scheme, which works ok with one notable exception: when properties are included/excluded with annotations, resulting accessor classes will differ.
But since it is not possible re-load classes, the initial definition remains, and may cause exception (or worse, potentially wrong output or binding).
One simple thing to do is to calculate checksum on bytecode and attach that as part of classname. This should result in different class name if actual contents change.
If even this fails we may need to consider use of randomized id instead; but let's try this first.
The text was updated successfully, but these errors were encountered:
(see #51 for background)
As things are, generated classes use simple naming scheme, which works ok with one notable exception: when properties are included/excluded with annotations, resulting accessor classes will differ.
But since it is not possible re-load classes, the initial definition remains, and may cause exception (or worse, potentially wrong output or binding).
One simple thing to do is to calculate checksum on bytecode and attach that as part of classname. This should result in different class name if actual contents change.
If even this fails we may need to consider use of randomized id instead; but let's try this first.
The text was updated successfully, but these errors were encountered: