[
https://issues.apache.org/jira/browse/JCLOUDS-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158447#comment-14158447
]
Andrew Gaul commented on JCLOUDS-736:
-------------------------------------
This actually does not relate to the modernizer work, just coincidence.
Reverting the checkstyle-on-compile commit
9384575d1ee4c2e68ff503b237dfedf8ab6b14bb addresses the symptoms for me. Note
that these symptoms are require some setup to reproduce, I needed to run
$ find ~/.m2/repository/org/apache/jclouds -name 2.0.0-SNAPSHOT | xargs rm -r
$ mvn clean install -DskipTests
to get consistent results.
> snapshot repo mildly screwed
> ----------------------------
>
> Key: JCLOUDS-736
> URL: https://issues.apache.org/jira/browse/JCLOUDS-736
> Project: jclouds
> Issue Type: Task
> Reporter: Adrian Cole
> Assignee: Andrew Gaul
>
> If you don't run mvn install on jclouds/resources, then you will get
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.12.1:check (checkstyle) on
> project jclouds-core: Failed during checkstyle execution: Unable to process
> configuration file at location: resources/checkstyle.xml: Cannot create
> file-based resource:invalid distance too far back -> [Help 1]
> probably the snapshot repo needs a publish
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
