ff2dece3ce
Update to junit-4.12, the jar file is downloaded, so not required on classpath anymore. Also adjust version in pom.xml for Sonar.
Conflicts:
.classpath
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1649178 13f79535-47bb-0310-9956-ffa450edef68
9 年前
d30236c873
Try one more way of excluding generated sources in the Maven pom.xml files for Sonar analysis
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1576063 13f79535-47bb-0310-9956-ffa450edef68
10 年前
d54e65c94e
Try to set the Sonar-Exclusion property differently to see if that makes the exclusions work
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1573741 13f79535-47bb-0310-9956-ffa450edef68
10 年前
95bf999782
Sonar-pom: Add some metadata, try to add Sonar exclusions for generated sources
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1572979 13f79535-47bb-0310-9956-ffa450edef68
10 年前
a926d50986
Try to improve Maven files for Sonar: Copy in (test)sources instead of linking to sources outside the sonar-directory which confuses Sonar, remove source-dir setting for ooxml-schema and ooxml-schema-encryption as both have generate sources and not actual ones, scratchpad is not needed for ooxml
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1572580 13f79535-47bb-0310-9956-ffa450edef68
10 年前
8d6b1f1f35
Add a set of maven pom.xml files for Sonar, a few workaround are
necessary, but overall this now allows to compile and run test for
all Apache POI components using Maven, which is a pre-requisite to
be analyzed at http://nemo.sonarqube.org/
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1568613 13f79535-47bb-0310-9956-ffa450edef68
10 年前
Dominik Stadler