For the moment I set the corresponding flag locally to true in order to achieve what I’m after:
https://github.com/apache/camel/blob/master/parent/pom.xml#L5372 <https://github.com/apache/camel/blob/master/parent/pom.xml#L5372> Maybe we can also define another profile which would do strict source checking with the resulting build failure if the source check doesn’t pass. Babak > On 9 Oct 2019, at 16:54, Andrea Cosentino <anco...@gmail.com> wrote: > > This was deliberately done if I remember correctly. It is too strict to > break the build for checkstyle. I don't know what others think about it > > Il mer 9 ott 2019, 16:51 Babak Vahdat <babak.vah...@swissonline.ch> ha > scritto: > >> Hi >> >> AFAIR building Camel source using the sourcecheck Profile enabled used to >> break the build if there was any Checkstyle issue: >> >> mvn clean install -Psourcecheck >> >> However currently when there’s a Checkstyle issue the build doesn’t seem >> to break for me, instead I see >> >> [INFO] Starting audit... >> [ERROR] … >> [ERROR] … >> [ERROR] … >> [ERROR] … >> Audit done. >> >> And then the build continues. The result of Checkstyle are then available >> unter the target/checkstyle-result.xml folder of the given Maven module. >> >> Do you know how one can enforce the build to break as it was the case >> before? As otherwise you continuously need to watch the maven log on >> console or check target/checkstyle-result.xml for each given module. >> >> Babak
