Bug 813352
Summary: | ecj in Fedora should be updated to latest version that supports Java 7 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Deepak Bhole <dbhole> |
Component: | ecj | Assignee: | Jon VanAlten <jon.vanalten> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | akurtako, andreasg123, dbhole, patrickm |
Target Milestone: | --- | Flags: | akurtako:
needinfo+
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-01-24 21:50:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 886013 |
Description
Deepak Bhole
2012-04-17 14:46:55 UTC
3.4 is quite old indeed. Even 3.7 is fairly old. I notice that Eclipse itself is at 4.2 for F17; should ecj align with that? I see no issues with jumping to 4.2. Alex, any problems you forsee? Well, 4.2 and 3.8 should be exactly the same with ecj keeping the 3.8 version and it's not yet released but should be fairly stable now so jumping on 3.8/4.2 seems like the right call to me. Hi, I did most of the necessary work to update this months ago, but it slipped through a crack somehow! Since 4.2.1 is now available, I've updated to that and committed (but not pushed a build) to rawhide branch. Before I push a build, or apply to F18/F17 branches, is there any particular use case that I should make sure is working? I've smoke tested this by successfully compiling code containing Java7 features (diamond operator, etc). It requires -source argument, but resulting compilation seems ok. Here's a scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=4576092 Verify that tomcat successfully compiles a hello workd jsp. If someone cares about gcj still you might want to verify it can still compile things. ecj-4.2.1-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ecj-4.2.1-2.fc18 Seems that everything is working as expected. Rawhide is set, f18 has update pending (test and add karma as you wish). Unfortunately. for f17 this does not seem to fall under an existing exception class for a major update. https://fedoraproject.org/wiki/Updates_Policy#Exceptions Although, I believe that with good backwards compatibility and the fact that other java tools are updated to support new language standard, this should be allowed. So I've put in FESCO ticket. https://fedorahosted.org/fesco/ticket/958 ecj-4.2.1-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ecj-4.2.1-1.fc17 Package ecj-4.2.1-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ecj-4.2.1-1.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16497/ecj-4.2.1-1.fc17 then log in and leave karma (feedback). ecj-4.2.1-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. tomcat-7.0.34-1.fc17 (http://koji.fedoraproject.org/koji/taskinfo?taskID=4817874) doesn't seem to build because this package hasn't been pushed to stable. That prevents the resolution of bug 889395 for Fedora 17. I noticed that ecj-4.2.1-1.fc17 has been in testing for more than two months. How would I test ecj to leave karma? Just install it with the existing Tomcat 7 and create a new JSP? h(In reply to comment #11) > tomcat-7.0.34-1.fc17 > (http://koji.fedoraproject.org/koji/taskinfo?taskID=4817874) doesn't seem to > build because this package hasn't been pushed to stable. That prevents the > resolution of bug 889395 for Fedora 17. I noticed that ecj-4.2.1-1.fc17 has > been in testing for more than two months. > > How would I test ecj to leave karma? Just install it with the existing > Tomcat 7 and create a new JSP? Hi, The build in testing has a known and really annoying bug, I've just unpushed it. There is fix, I just didn't get to building that before holidays... honestly, so little seems to care about ecj anymore that it kept getting pushed down my list. Sorry! Now that it actually blocks something, I will prioritize it. Expect new update (karma please!) when I return Jan 8. I'm not exactly familiar with tomcat internals but that seems a reasonable way to test for karma purposes. Anything to confirm that it Just Works as far as you can tell. I'm wondering if there is any news on ecj for Fedora 17. The version from 2012-10-18 is still the most recent one in testing. ecj-4.2.1-2.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ecj-4.2.1-2.fc17 (In reply to comment #13) > I'm wondering if there is any news on ecj for Fedora 17. The version from > 2012-10-18 is still the most recent one in testing. Thanks for timely reminder, and for your patience! See previous comment, new update has been sent. Please do test and apply karma as appropriate. If you're wondering, it was bug 869578 that had shown up in first update, so I had elected not to push the initial build, and even preferred to let the fix soak in rawhide a bit before backporting. Thanks for the update. It works for me with tomcat-7.0.33-2.fc17. Before restarting Tomcat, it produced a stack trace when attempting to compile something. I should have realized that that would be required. ecj-4.2.1-2.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |