Óscar González Fernández 787916b50d Bug #1592: Save Order before showing it ... Otherwise the MutableTreeModel associated is initialized with a Order that is not saved yet. When it's used, e.g., when adding a subtask, it fails. The MutableTreeModel#nodesByDomainObject map wouldn't find the node associated to the Order, because the hashCode is different. At first the Order is a new object so it returns a different hashCode, once saved another. With these changes, when initializing the MutableTreeModel it has already been saved.		2012-12-11 20:04:33 +01:00
..
src	Bug #1592: Save Order before showing it	2012-12-11 20:04:33 +01:00
pom.xml	Bump version number to 1.3.2	2012-11-30 07:41:11 +01:00