With the new Java system, we are able to do some magic to get around packages which don't deal well with Java 1.5. There are two primary cases where this will happen. The first is the introduction of the enum keyword. Instead of patching to rename the variables named enum, it is better to use -source 1.4, to use 1.4 source. This usually involves patching the build.xml to add add source="1.4" and target="1.4" to javac tasks. Alternatively, and easier, is to inherit java-ant-2, and in depend, depend on: >=virtual/jdk-1.4. java-ant-2 will then rewrite build.xml to have target="1.4" ans source="1.4". If there's a src_unpack function, it needs to be renamed to ant_src_unpack. The other is cases where the package uses XML APIs that changed between 1.4 and 1.5. Most of the time, there are new abstract methods in 1.5 that need to be implemented. To work around this, it can DEPEND on: =virtual/jdk-1.4* The result is that the package will switch to a 1.4 JDK, which shouldn't have any problems. This is really a short-term solution. Ideally, the source will be patched to implement these methods. The quickest way to do this is to just throw UnsupportedOperationExcpetion in the method. The issue should be reported upstream so that we don't have to continually patch the source.
For future reference, please do not file bugs / patches for packages where you either: patch build.xml to have source="1.4" target="1.4" patch source to rename variables from enum to something else. java-ant-2.eclass will handle rewriting build.xml files in this case.
A quick grep shows there's still quite a number of ebuilds requiring JDK 1.4. You're aware that Sun drops security support for 1.4.2 end of October this year?!
(In reply to comment #2) > A quick grep shows there's still quite a number of ebuilds requiring JDK 1.4. > You're aware that Sun drops security support for 1.4.2 end of October this > year?! > Well we can always change JDKs so that they can only be used to build things and not run.
(In reply to comment #2) > A quick grep shows there's still quite a number of ebuilds requiring JDK 1.4. > You're aware that Sun drops security support for 1.4.2 end of October this > year?! Yes, I'm working on deprecating 1.4.
Last package fixed.
