You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by Jeremy Daggett <no...@github.com> on 2015/01/10 02:42:09 UTC

[jclouds] Backport Chef Map ordering to 1.8.x (#639)

In attempting to backport the `AutoService` changes to the **1.8.x** branch today, I consistently ran into test failures because of this ordering issue. Apparently, commit [cd4ce6](https://github.com/jclouds/jclouds/commit/cd4ce6b1923b37c30a98f3ff5c54947c68ecf292) had not been backported. :cry: cc @nacx 
You can merge this Pull Request by running:

  git pull https://github.com/rackspace/jclouds backport-JCLOUDS-428-1.8.x

Or you can view, comment on it, or merge it online at:

  https://github.com/jclouds/jclouds/pull/639

-- Commit Summary --

  * JCLOUDS-428: Use Maps with a consistent iteration order

-- File Changes --

    M apis/chef/src/main/java/org/jclouds/chef/internal/BaseChefService.java (2)
    M apis/chef/src/main/java/org/jclouds/ohai/functions/NestSlashKeys.java (4)
    M apis/chef/src/test/java/org/jclouds/chef/internal/BaseChefServiceTest.java (4)
    M apis/chef/src/test/java/org/jclouds/ohai/config/OhaiModuleTest.java (2)
    M apis/chef/src/test/java/org/jclouds/ohai/functions/NestSlashKeysTest.java (26)

-- Patch Links --

https://github.com/jclouds/jclouds/pull/639.patch
https://github.com/jclouds/jclouds/pull/639.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/639

Re: [jclouds] Backport Chef Map ordering to 1.8.x (#639)

Posted by Jeremy Daggett <no...@github.com>.

Closed #639.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/639#event-217479324

Re: [jclouds] Backport Chef Map ordering to 1.8.x (#639)

Posted by Ignasi Barrera <no...@github.com>.

The build seems to have failed due to unrelated checkstyle failures. Mind fixing the 4 unused imports in another commit in this PR? Those violations may potentially cause any PR to 1.8.x to fail.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/639#issuecomment-69447709