[ http://jira.magnolia.info/browse/MAGNOLIA-1342?page=comments#action_13371 ] Jörg Schaible commented on MAGNOLIA-1342: -----------------------------------------
Because the transitive dependency resolution of Maven often relies on the processed sequence if two deps are equal in term of "near". Since the sequence seems to rely somehow on an iterator returned from a hash map, it may change by adding a new dep, by changing the version of an existing, or by changing the dependency sequence in the declaration. In case of junit we observed this often in our own builds when any transitive artifact declare junit in compile scope and it was therefore excluded (e.g. globally in a master POM). Why does this affect JDK 6? Since the internal algorithm used in the HashMap has changed and elements are returned in a different sequence (which should not affect anything though - it simply marks a brittle implementation). Should be gone with M2.0.5 though. Can hardly await that. > magnolia-gui does not compile under JVM 1.6 and 1.7 > --------------------------------------------------- > > Key: MAGNOLIA-1342 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1342 > Project: Magnolia > Issue Type: Bug > Affects Versions: 3.0.x > Reporter: Nicolas Modrzyk > Assigned To: Nicolas Modrzyk > Priority: Trivial > Fix For: 3.0.x > > Original Estimate: 1 minute > Remaining Estimate: 1 minute > > build failing with: > /magnolia-gui/src/test/java/info/magnolia/cms/gui/dialog/DialogFckEditTest.java:[15,22] > package junit.framework does not exist -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
