The example is great, but it only activates the profile for the jclouds-project module, and we'll need it for every module in the jclouds repo. I've added a new profile and tried to configure its activation to be enabled for all projects, but:
Wait...the idea behind the profile is to *deactivate* remote-resources! So it's indeed intentional that the profile is *only* active in jclouds-project.
There's a *default* invocation (not in a profile) that runs for *all* projects. The profile is only intended to override that default invocation to stop remote-resources being run in jclouds-project, which causes the missing dependency problem you saw.
Does this make more sense? ap
