Pete. Was you you who suggested that we remove serialUID on entities?
because serialuid=1L; is technically invalid in a real environment.
Does anyone remember why we removed this feature again?
~Lincoln
---------- Forwarded message ----------
From: George Gastaldi (JIRA) <jira-events(a)lists.jboss.org>
Date: Thu, Mar 1, 2012 at 12:41 PM
Subject: [forge-issues] [JBoss JIRA] (FORGE-157) Create serialVersionUID
field on mapped classes
To: forge-issues(a)lists.jboss.org
[
https://issues.jboss.org/browse/FORGE-157?page=com.atlassian.jira.plugin....]
George Gastaldi updated FORGE-157:
----------------------------------
Status: Pull Request Sent (was: Reopened)
Git Pull Request:
https://github.com/forge/core/pull/120
Test case and fix included ;)
Create serialVersionUID field on mapped classes
-----------------------------------------------
Key: FORGE-157
URL:
https://issues.jboss.org/browse/FORGE-157
Project: Forge
Issue Type: Enhancement
Components: Builtin Plugins
Affects Versions: 1.0.0.Beta1
Reporter: George Gastaldi
Fix For: 1.0.0.Beta2
When creating a new entity, the class implements Serializable however
does not
specify a serialVersionUID field.
--
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
_______________________________________________
forge-issues mailing list
forge-issues(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-issues
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"