On Tue, Jan 3, 2012 at 9:39 PM, Rob Weir <[email protected]> wrote: > On Tue, Jan 3, 2012 at 7:27 PM, Dennis E. Hamilton > <[email protected]> wrote: >> The tools.jar is in the usual JDK location and the packages are there. >> >> There is a way to run Maven where it shows the commands it executes and I >> may do that to see what the compile command looks like. Since Maven is >> synthesizing class-path parameters, it would be interesting to see what the >> compile command is and whether there is a command-line change in Java 7. >> >> I'm out of time on this for now, but I will take another crack at it >> eventually. >> > > I think I got it. In taglets/pom.xml, look for tools.jar. The vendor > changed in the Java 7 version from "Sun Microsystems Inc." to "Oracle > Corporation". That vendor name switch causes Maven not to see that > dependency. Ouch. > > I changed the vendor name and it is not building under Java 7, or at > least it has got past that error. We'll see in another 20 minutes or > so if it completes. >
Confirmed. It works fine on Java 7 after that change. But that said, I didn't think Java 7 was among our supported platforms, at least not yet. Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) Maven home: C:\apache-maven-3.0.3\bin\.. Java version: 1.7.0_02, vendor: Oracle Corporation Java home: C:\Program Files\Java\jdk1.7.0_02\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp", version: "5.1", arch: "x86", family: "windows" [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] Apache ODF Toolkit ................................ SUCCESS [3.656s] [INFO] ODF Custom Javadoc Taglets ........................ SUCCESS [7:29.485s] [INFO] XML Schema to Template Mapping Tool: Parent POM ... SUCCESS [0.140s] [INFO] XML Schema to Template Mapping Tool: Library ...... SUCCESS [36.391s] [INFO] XML Schema to Template Mapping Tool: Maven2 Plugin SUCCESS [19.875s] [INFO] ODFDOM ............................................ SUCCESS [22:59.875s] [INFO] ODF XSLT-Runner ................................... SUCCESS [15.953s] [INFO] ODF XSLT-Runner Ant Task .......................... SUCCESS [15.719s] [INFO] ODF Validator ..................................... SUCCESS [1:27.078s] [INFO] Simple Java API for ODF (Simple ODF) .............. SUCCESS [6:22.047s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 39:51.156s [INFO] Finished at: Tue Jan 03 22:10:15 EST 2012 [INFO] Final Memory: 63M/237M [INFO] ------------------------------------------------------------------------ > I wonder if we can simply list the JAR twice, once with each vendor? > Maven seems to ignore the one it can't find. > > I wonder how this worked at all with OpenJDK? Do they just list > themselves as coming from Sun for compatibility? > > > -Rob > >> - Dennis >> >> -----Original Message----- >> From: Rob Weir [mailto:[email protected]] >> Sent: Tuesday, January 03, 2012 13:17 >> To: [email protected] >> Subject: Re: JDK 7 Results (was RE: [VOTE] Release Apache ODF Toolkit >> 0.5-incubating(RC7)) >> >> On Mon, Jan 2, 2012 at 1:35 AM, Dennis E. Hamilton >> <[email protected]> wrote: >>> Just for fun, I also attempted to build (rc7) with JDK 7u2, since JDK 6u30 >>> seemed to work so well. >>> >>> No joy. The Maven clean install failed with compiler errors in the very >>> first >>> compiles. >>> >>> - Dennis >>> >>> SOME DETAILS >>> >>> I don't think this is an ODF Toolkit problem. It appears to be somewhere >>> between Maven and JDK 7. The basic situation is that com.sun.javadoc and >>> other packages in the %JAVA_HOME%\lib\tools.jar are not found. I tried >>> several variations (but I did not restrict Maven to not use any parallel >>> builds). >>> >> >> Does Java 7 give you a tools.jar at all? If so, what happens if you >> just add it to the classpath? >> >> -Rob >> >> [ ... ] >>
