On Sun, Jun 29, 2014 at 9:03 AM, Thomas Neidhart <thomas.neidh...@gmail.com> wrote:
> On 06/28/2014 02:43 PM, Gary Gregory wrote: > > The RN state: "Java 1.2 or later is required." > > > > I'm pretty sure this will only build with Java >= 1.4 even though the > > compile target is 1.2. So we have a different requirement for build and > > run-time. I had to set my Eclipse project to a 1.4 JDK because it would > not > > compile with a 1.3. I do not had a 1.2 laying about anymore. We should > have > > a note on the site or in the release notes. Not a blocker. > > > > Bonus points for not blowing up on Java 8 Javadoc errors (but there are > > still a lot of warnings). > > > > Build fails with "mvn clean site": > > > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 03:22 min > > [INFO] Finished at: 2014-06-28T08:37:56-04:00 > > [INFO] Final Memory: 54M/218M > > [INFO] > > ------------------------------------------------------------------------ > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on > > project commons-logging: Error during page generation: Error rendering > > Maven report: Could not find resource 'C:\temp\rc\commons-logging-1. > > 2-src/pmd.xml'. -> [Help 1] > > [ERROR] > > [ERROR] To see the full stack trace of the errors, re-run Maven with the > -e > > switch. > > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > [ERROR] > > [ERROR] For more information about the errors and possible solutions, > > please read the following articles: > > [ERROR] [Help 1] > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > > > With: > > > > Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; > > 2014-06-17T09:51:42-04:00) > > Maven home: C:\Java\apache-maven-3.2.2 > > Java version: 1.8.0_05, vendor: Oracle Corporation > > Java home: C:\Program Files\Java\jdk1.8.0_05\jre > > Default locale: en_US, platform encoding: Cp1252 > > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" > > > > Same with Maven 3.0.5. > > > > If I just run "mvn clean test", the tests do not run: > > > > [INFO] --- maven-surefire-plugin:2.12:test (default-test) @ > commons-logging > > --- > > [INFO] Tests are skipped. > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] BUILD SUCCESS > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Total time: 14.080 s > > [INFO] Finished at: 2014-06-28T08:42:11-04:00 > > [INFO] Final Memory: 23M/135M > > [INFO] > > ------------------------------------------------------------------------ > > > > ? > > the reason for that is that the tests are executed as part of the verify > phase using the failsafe plugin. > > So when you create the site you should also run it like this: > > mvn clean verify site > > The test setup is rather complex and uses a custom classloader to load > the jar files. There is a way to change the tests so that they can also > be executed from eclipse using junit but I have this change only in my > local environment. > Should this be documented in a BUILDING.txt file in the root of the project or in the RELEASE NOTES? Gary > > Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition <http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
