Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.