In order to use the checkstyle.ml config from the classpath, the
maven-checkstyle-plugin must declare the jclouds-resources dependency
in its configuration. The problem is that the plugin is configured in
the jclouds-project, which is the parent pom, and that means the
jclouds-project needs to have the jclouds-resources.jar in the maven
repo *before* it can be actually built, and this is where the build
breaks.
What we did when we still used a remote resource for the license
files, which caused the same problem, is to have a jclouds-project
profile [1] which *disabled* the remote-resources execution for
jclouds-project only.
Checkstyle could still work for jclouds-project, it would simply have
to refer to the files by path (since they're in the same repo) rather
than use a dependency.
Let me know if I can help any more with this!
ap
[1]
https://github.com/jclouds/jclouds/blob/ddfb8e58a5a729cabb5edf954a113ee8127cd7cb/project/pom.xml#L912
