Different versions of UML and JDK output these collections in different order, making consistent builds and version migration with comparison of results difficult. These results should be an ordered List instead of an unordered Collection.
Updated metafacade-uml common model 1/04/10 but there are still additional changes required to make the implementation consistent between UML metafacade versions.
Different versions of UML and JDK output these collections in different order, making consistent builds and version migration with comparison of results difficult. These results should be an ordered List instead of an unordered Collection.
Updated metafacade-uml common model 1/04/10 but there are still additional changes required to make the implementation consistent between UML metafacade versions.
This is a moot point now that we require JDK6 for compilation/runtime (due to several JDK6 APIs added to the code base), and since we added the capability to test multiple different models + configurations as part of the cartridge build. The UML14 and UML2 model inputs will never match up anyway because the UML2 migration causes all collection values to be marked as 'Unique', while in UML14 there is no equivalent so values are non-unique.
Bob Fields added a comment - 29/Jul/10 4:03 PM This is a moot point now that we require JDK6 for compilation/runtime (due to several JDK6 APIs added to the code base), and since we added the capability to test multiple different models + configurations as part of the cartridge build. The UML14 and UML2 model inputs will never match up anyway because the UML2 migration causes all collection values to be marked as 'Unique', while in UML14 there is no equivalent so values are non-unique.
Improvement
Resolved
Minor