Simple patch to make it work.
Created attachment 90872 [details, diff] commons-el-1.0-jdk15.patch
This isn't necessary, because it is accomplished by the new Java system, by using -source 1.4.
But it is better to patch than using the source. This way we can work with upstream to fully solve the issues.
Just another comment... Why did you close the bug without making any modification... Patch or move into the new build system?
Yes, ideally upstream would update their build.xml to use <javac source="1.4" target="1.4">. But as it is, we don't to take any action to address the problem from our perspective. But by all means, please do file a bug upstream. I would do it myself, but I am currently overloaded working on porting everything to the new Java system.
I think that the idle solution is not to update the build.xml, but fix the source... But still... I don't understand why you close this bug without fixing the problem... Choose to apply the patch to the sources or fix the build.xml... But why you closed the bug?
Like, I said, using the new Java system to rewrite the build.xml is the preferred way of addressing the problem. Therefore, no change is changes are need, so it's not really a bug, so there's nothing to fix. Hence, I closed the bug.
I am truly sorry... But I don't get it... It does not work for me... From what I understood from you guys is that the ebuild should be modified in order to work with the new ebuild system... Currently it have: inherit java-pkg eutils So it uses the old build system, right? Am I missing something? Anyway, it does not work AS-IS...
It would work if you are using a 1.4 JDK as a generation-1 system VM. To use a 1.5 JDK is not supported as a generation-1 system VM because of you'd encounter problems like this, and others. Currently, it is a generation-1 ebuild. So, using a 1.4 JDK, the package works as is. When the package is migrated to generation-2, it will handle using >1.4, by using the mechanism of source="1.4" target="1.4" without any further hassle. I am working on migrating packages as fast as I can, but you will have to be patient because there are some 400+ Java packages, and I am the only developer doing the migration at this time.
OK, thanks... But we have discussed this in bug#138174. When I say not compile with jdk 1.5 I mean with ONLY jdk 1.5... I am willing to help to do the conversion... But I need a good example first... Please convert tomcat, which is a good test case... Then I will submit some more patches. But this bug isn't solved... I am reopening it until we have a proper fix.
Fixed in CVS to use new Java system. Happy now?
Sure! Thanks.
But you did not apply the patch, nor I saw that you tell the build system to apply source of 1.4.
I don't get it... You automatically compile all classes to meet 1.4 source level? So how do you compile a native 1.5 application? I thought that I will see somekind of variable specifying a source level. I see it is a function of the dependencies... But it should not be this way... Since you will not be able to compile 1.5 with 1.4 dependencies. Do you have any documentation regarding these new eclasses?
Chances are it hadn't propogated to your rsync mirror. It certainly should have by now. It is dev-java/commons-el-1.0-r1. Documentation is available at: http://www.gentoo.org/proj/en/java/java-devel.xml Please take further questions and discussion to the gentoo-java mailing list, as this is a bit beyond the scope of this bug, not to mention there are more people on the list than get bug notifications. Details should be on our project page: http://www.gentoo.org/proj/en/java/
