[hibernate-commits] [hibernate/hibernate-validator] 14ed3f: HV-1550 Reduce the verbosity of the maven-javadoc-...

Branch: refs/heads/master Home: https://github.com/hibernate/hibernate-validator Commit: 14ed3fa776522aaaaeb2cdbdc601d7be79b3a8d2 https://github.com/hibernate/hibernate-validator/commit/14ed3fa776522aaaa... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2017-12-21 (Thu, 21 Dec 2017) Changed paths: M pom.xml Log Message: ----------- HV-1550 Reduce the verbosity of the maven-javadoc-plugin We don't need to list the files being generated in the console. Commit: f8817455916072262c7b40c9255b8843dce5722c https://github.com/hibernate/hibernate-validator/commit/f8817455916072262... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2017-12-21 (Thu, 21 Dec 2017) Changed paths: M .travis.yml Log Message: ----------- HV-1550 Move common build options to a variable in the Travis build Commit: 2821131a02b6cff117087d4ca4958781e07ab00f https://github.com/hibernate/hibernate-validator/commit/2821131a02b6cff11... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2017-12-21 (Thu, 21 Dec 2017) Changed paths: M .travis.yml Log Message: ----------- HV-1550 Clarify the build output when checkstyle fails When checkstyle failed, it used to fail in the initial, no-log build, and then we didn't have the checkstyle logs to tell us why it failed. By disabling checkstyle in this initial build we can make the build fail a little bit later, when the logs are enabled. Also, adding a separate checkstyle execution right before the actual build allows us to fail fast if checkstyle checks fail. Commit: c0da32dfdde22a8ecc50bfb7e0847a49381fb0de https://github.com/hibernate/hibernate-validator/commit/c0da32dfdde22a8ec... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2017-12-21 (Thu, 21 Dec 2017) Changed paths: M .travis.yml Log Message: ----------- HV-1549 Use mvn install instead of mvn verify in the Travis build 'mvn verify' is theoretically the way to go, but in practice it leads to some issues. In particular, Maven plugins that need to retrieve artifacts (such as those used to add our modules to the WildFly server) usually don't know about the artifacts packaged during the current build, and they end up looking for the required artifacts in the local Maven repository. If we use 'mvn verify', the artifacts used for testing will then be retrieved from a remote repository, and we'll end up executing WildFly ITs against a nightly build... Using 'mvn install' solves the issue by populating the local repository with the version currently being built. Also, this commit adds a 'before_cache' operation to avoid dirtying the cache with the artifacts currently being built. Compare: https://github.com/hibernate/hibernate-validator/compare/180568011285...c...