------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.6:site (default-site) on
project commons-lang3: Error generating
maven-checkstyle-plugin:2.17:checkstyle: Failed during checkstyle
execution: *Unable to find suppressions file at location:
C:\temp\rc\commons-lang3-3.6-src/checkstyle-suppressions.xml*: Could not
find resource
'C:\temp\rc\commons-lang3-3.6-src/checkstyle-suppressions.xml'. ->
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
<http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException>

Gary

If you think a failing site build is blocking the release you’re free to
vote -1 (which I’d like to ask you to do explicitly).
I don’t think that a failing site build should block a release (although
we should fix this for 3.6.1). So if the majority of the voters is okay
with this, I think I’m going to release the code anyway.

Hi Benedikt,

Strictly speaking this should not block the release BUT... the way I got
started here, is by making small fixes and additions and THEN running a
full build with reports to make sure I did not make things worse. So to me,
being able to build a full site is the best way to validate changes. This
is what makes the component approachable to new contributors. If we deliver
a broken build, this creates an impedance for contributors, again, IMO.

we have fixed quite a few bugs and added some nice new features since
Commons Lang 3.5 was released, so I would like to release Commons Lang
3.6
based on RC2.
The reason we had to cut a second release is, that there were some
discussions around the annotations for documenting concurrency
properties
in the o.a.c.l.concurrent.annotation package. I’ve removed those
annotations, so that we can fix them after the release.