db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-635) tck2 does not compile with JDK 1.5
Date Fri, 07 Aug 2009 18:57:14 GMT

    [ https://issues.apache.org/jira/browse/JDO-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740678#action_12740678
] 

Michael Bouschen commented on JDO-635:
--------------------------------------

Running latest Windows JDK 1.5:
  java version "1.5.0_20"
  Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_20-b02)
  Java HotSpot(TM) Client VM (build 1.5.0_20-b02, mixed mode, sharing)

Same result as described by Craig. I see the problem unless I disable the setting -proc:none:
 

java:compile:
    [echo] Compiling to d:\projects\jdo\workspace\jdo\trunk\tck2/target/classes
    [javac] Compiling 841 source files to D:\projects\jdo\workspace\jdo\trunk\tck2\target\classes
    [javac] javac 1.5.0_20
    [javac] javac: invalid flag: -proc:none

> tck2 does not compile with JDK 1.5
> ----------------------------------
>
>                 Key: JDO-635
>                 URL: https://issues.apache.org/jira/browse/JDO-635
>             Project: JDO
>          Issue Type: Bug
>          Components: tck2
>    Affects Versions: JDO 2 maintenance release 2
>            Reporter: Michael Bouschen
>             Fix For: JDO 2 maintenance release 3
>
>
> Recently the file projects.properties in tck2 was changed in order to turn OFF any post-compile
enhancement with JDK1.6:
>  maven.compile.compilerargs= -proc:none
> This leads to a javac error when using JDK 1.5 (I'm using build 1.5.0_15-b04):
> java:compile:
>    [echo] Compiling to d:\projects\jdo\workspace\jdo\trunk\tck2/target/classes
>    [javac] Compiling 1 source file to D:\projects\jdo\workspace\jdo\trunk\tck2\target\classes
>    [javac] javac: invalid flag: -proc:none
>    [javac] Usage: javac <options> <source files>
> Unfortunately, maven1 does not support profiles (where maven 2 does support profiles)
which allows environment specific property settings. 
> Eric proposed: 
> "Another way of disabling the enhancement on compile time is removing the enhancer jar
from the compiler classpath."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message