karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] Created: (KARAF-405) Force JDK 1.5 compiler
Date Thu, 20 Jan 2011 08:21:43 GMT
Force JDK 1.5 compiler

                 Key: KARAF-405
                 URL: https://issues.apache.org/jira/browse/KARAF-405
             Project: Karaf
          Issue Type: Improvement
            Reporter: Jean-Baptiste Onofré
             Fix For: 2.2.0

As agreed on the dev mailing list, we defined the following policy:
- Karaf 2.2.x == JDK 1.5
- Karaf 3.0.x == JDK 1.6

It means that we should be sure that we don't use JDK 1.6 specific methods on the current
trunk (corresponding to Karaf 2.2.x).

For instance, we got a Hudson build failure due to the usage of java.lang.String isEmpty()
method which is JDK 1.6 specific whereas Hudson still uses JDK 1.5.

To detect this kind of situation, I propose to define the <source/> and <target/>
on the maven-compiler-plugin.

These instructions will be removed after the 2.2.x branch cut off. The trunk will be Karaf
3.0.x and so JDK 1.6 compliant.

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

View raw message