Test build failed in Java 7 about antisamy

[davewichers]

I've experienced issues with Java 7 vs. Java 8 where you can't download the artifacts required to run things with Java7 due to TLS problems. So you first have to download them with Java 8, then switch to Java 7, and then you can run/test everything no problem. Is that the problem you are having? That might at least solve your download from Central error.

If that fixes the 2nd problem, does it make the 1st error go away too? Or not?

The reason we are trying to maintain Java 7 support is the OWASP ESAPI project uses AntiSamy and they are trying to maintain Java 7 support. Once they move to Java 8, we plan to do so too. @kwwall - Any news on when ESAPI might move to Java 8 finally?

[LiuXing-R]

@davewichers I've tried this method

So you first have to download them with Java 8, then switch to Java 7,

It can solve the problem of downloading from Centre errors, but the org.owasp.validator .html.test.policyTest.testGithubIsue79 test case still fails.

I'm not sure if this use case uses Java8's API, at least the exception information is Unsupported major.minor version 52.0.

I have a solution to replace Class.forName with URLClassLoader, to get files under the 'jar:file' path, and I've verified it in Java7.
e.g:

            java.net.URLClassLoader child = new java.net.URLClassLoader(
                    new URL[] {Thread.currentThread().getContextClassLoader().getResource("policy-in-external-library.jar")},
                    this.getClass().getClassLoader()
            );

            policyUrl = child.getResource("policyInsideJar.xml");

Unfortunately, 'mvn package' still failed because 'javadocjar: Unsupported major.minor version 52'. Maybe java8 is the best choice.

[davewichers]

I have verified that everything compiles fine with Java 7, but you can't run the unit tests with Java 7, because of the above issue. However, I'm pretty confident that AntiSamy works on Java 7, just fine. And it's not worth fixing this as we are about to move to Java 8 in the 1.7.0 release which we intend to release in early 2022. As such, we aren't going to fix this.