Works for me on Windows XP x84.

C:\jdevrt\trinidad\trunk_test>which mvn
/cygdrive/c/program files/apache/maven/maven-2.0.7/bin/mvn

C:\jdevrt\trinidad\trunk_test>echo %JAVA_HOME%
C:\java\jdk\jdk1.5.0_17

C:\jdevrt\trinidad\trunk_test>mvn clean install
builds successfully

-Cale

Andrew Robinson said the following" "On 3/11/2009 9:11 AM PT:
Works fine on Linux amd64 under the official Sun 1.5 JDK

Maven version: 2.0.9
Java version: 1.5.0_16
OS name: "linux" version: "2.6.27-13-generic" arch: "amd64" Family: "unix"

built the trunk fine with the above settings.

-Andrew

On Tue, Mar 10, 2009 at 5:42 PM, Matt Cooper <[email protected] <mailto:[email protected]>> wrote:

    Hi all,

    I've noticed lately that in order to build Trinidad, I have to use
    jdk6 on the command line (though the settings.xml uses jdk5).

    My ~/.m2/settings.xml has the following:

      <profiles>
        <profile>
          <id>java5.home</id>
          <activation>
            <activeByDefault>true</activeByDefault>
          </activation>
          <properties>
<jdk5.home>/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home</jdk5.home>
          </properties>
        </profile>
      </profiles>

    If I try to build using a jdk5 JAVA_HOME on the command line, I
    get these test errors:

    Tests in error:
initializationError0(org.apache.myfaces.trinidadinternal.renderkit.CoreRenderKitTest) testEscapeInQuoteJS(org.apache.myfaces.trinidadinternal.ui.laf.base.xhtml.XhtmlLafUtilsTest) testDoubleEscapeInQuoteJS(org.apache.myfaces.trinidadinternal.ui.laf.base.xhtml.XhtmlLafUtilsTest)

JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home

    However, if I build using a jdk6 JAVA_HOME (and keep the jdk5
    setting in the settings.xml file), it builds fine.

JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home

    Has anyone else noticed that Trinidad requires this strange build
    quirk (if so what OS are you using)?

    It might be a Mac-specific issue or perhaps something else strange
    on my machine.

    Thank you,
    Matt


Reply via email to