Dominik Stadler
|
892e01b656
|
Sonar Maven: Revert previous changes as they also did not work, it seems there is no way to get a Sonar Maven build this way :(
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1698089 13f79535-47bb-0310-9956-ffa450edef68
|
2015-08-27 08:20:40 +00:00 |
|
Dominik Stadler
|
fd02230c1d
|
Next try for Sonar Maven build: Specify the src-pathes in the various pom.xml files
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1697758 13f79535-47bb-0310-9956-ffa450edef68
|
2015-08-25 19:04:11 +00:00 |
|
Andreas Beeker
|
7cbfc3d7e1
|
Update to 3.13-SNAPSHOT
git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1696045 13f79535-47bb-0310-9956-ffa450edef68
|
2015-08-15 12:23:51 +00:00 |
|
Dominik Stadler
|
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
|
2015-01-03 09:35:21 +00:00 |
|
Dominik Stadler
|
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
|
2014-02-27 14:03:27 +00:00 |
|
Dominik Stadler
|
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
|
2014-02-15 10:42:43 +00:00 |
|