[
https://issues.jboss.org/browse/FORGE-495?page=com.atlassian.jira.plugin....
]
Lincoln Baxter III closed FORGE-495.
------------------------------------
Resolution: Won't Fix
Hey Burr, good find, but as we recently discussed on the dev list, it is incorrect to
generate a serialVersionUID for a class unless a user asks for it. As it stands, omitting
the field simply causes the JVM to generate the UID at runtime based on the hash of the
class file, which is a more correct solution than generating a version for all classes
automatically, where users may forget about them or assume that the generated ID should
remain for the future.
This is something which can be completed using the refactoring tools in JBDS already
(press CTRL-1 on the warning, select "Generate SerialVersionUID") so it
doesn't really make sense for Forge to duplicate this behavior at the moment.
Forge generated entity: The serializable class ProductOrder does not
declare a static final serialVersionUID field of type long
---------------------------------------------------------------------------------------------------------------------------------
Key: FORGE-495
URL:
https://issues.jboss.org/browse/FORGE-495
Project: Forge
Issue Type: Enhancement
Environment: Inside of JBDS5
Reporter: Burr Sutter
Forge generated entities result in the following Warning when inside of JBDS.
Note: using Forge at the command line and then Maven Import into JBDS
The serializable class ProductOrder does not declare a static final serialVersionUID
field of type long
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira