Build failed in Jenkins: Struts-site-javadocs #10

See Changes: [github] Mention Maven and maven-archetypes on donwload page [github] gs - using properties for maven version is best practice [github] llink to maven-artifacts.html [github] gs - show full web.

Re: @PMC, a few INFRA request?

On 12/4/2017 10:31 PM, Lukasz Lenart wrote: > I'm not sure if JDepend would be the same You're right that it's not same and as popular as. However it's listed in `External Analysers` of official documentation [1] so I hope it should work. I mentioned it because it seems with GitHub plugin can

Build failed in Jenkins: Struts-site-javadocs #11

See -- [...truncated 908.81 KB...] [INFO] Finished Dependency Bundling Analyzer (0 seconds) [INFO] Analysis Complete (1 seconds) [INFO] Generating "Dependency Updates Report" report ---

Build failed in Jenkins: Struts-site-javadocs #12

See -- [...truncated 1.06 MB...] [INFO] Finished Dependency Bundling Analyzer (0 seconds) [INFO] Analysis Complete (2 seconds) [INFO] Generating "Dependency Updates Report" report ---

Build failed in Jenkins: Struts-site #169

See Changes: [github] README - mention that changes are published automatically -- Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely o

Re: Fixing Sonar issues?

On 12/4/2017 8:58 PM, Stefaan Dutry wrote: > Talking from my personal experience, you should not just blindly > eliminate all Issues reported by a code analyzer. > (I've done that for a single project at our work and i've regretted it > ever since) > > My advise would be to start with the things

Jenkins build is back to normal : Struts-site #170

See - To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org