Java Source Code security Audit (ii)

This article covers the following: Fortify-sca audit tools, MAVEN, Java

After a long period of research on fortify, I decided to continue writing the Java Source Code security audit article, more to record the work in order to solve the problem to learn the process

Not much to say, first we look at the life cycle of the fortify Security audit, the MAVEN project as an example

Clean--build--analyze--report

Well, first, let's look at our project.

Maven Project

Well, first we need to do maven with it.

After installing MVN, try to do mvn install, in the SVN root directory (containing the Pom.xml level directory)

Failed and after Google I tried to add the box to the Pom.xml

Join this pom.xml and try it.

Try mvn install again after saving

It's a little bit longer, sure enough.

But it failed, but the mistake was gone.

Again Google check this paragraph

https://stackoverflow.com/questions/19655184/ No-compiler-is-provided-in-this-environment-perhaps-you-are-running-on-a-jre-ra

Be decisive again try to copy the SDK directory, put in the Pom.xml

Try the MVN install again

OK, long-lost success success!!!

Okay, now look at the SVN catalog.

Open it and look down.

9 o'clock in the evening, first write here, tomorrow to deal with the rest of the steps ....

Java Source Code security Audit (ii)