And hopefully the mappedName bug is fixed in GPD 126.96.36.199, where in 3.0.9 it produced mappedName instead of mapped-name in the XML source...
Does the following line from the release notes imply that the database schema has changed and needs to be updated if you are upgrading from 3.1 to 3.1.1?
keep the processdefinition.xml in the database
Hm, I don't think the bug is fixed... Is there already a JIRA issue about this? If not, would you care to create one, otherwise we lose track of these things.
And no, database upgrades are not necessary for maintenance releases.
Actually, you yourself acknowledged the bug and said it would be fixed in this release http://jboss.org/index.html?module=bb&op=viewtopic&t=81735
I just tested it on 3.0.9 at home, and saw mappedName show up in a freshly created task. Then I installed 188.8.131.52 and created a new task again, and voila...all fixed. So somebody fixed it, and that's all that matters. :)
And no, I didn't find any JIRA issues when I searched for both "mappedName" and "mapped-name"
I remember that you brought up the issue... I must have fixed it rightaway indeed ;-)
But it illustrates that we tend to forget about it when there is no JIRA issue...