[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5916) Wrong Compiler Compliance Level set when creating new ESB Project

[ https://jira.jboss.org/jira/browse/JBIDE-5916?page=com.atlassian.jira.plu... ] Rob Stryker updated JBIDE-5916: ------------------------------- Attachment: JBIDE-5916.patch The attached patch refuses EAP 5.0 the ability to accept jst.java facet versions under 6.0. This automatically pushes compiler compliance up and removes the error. I cannot verify for certain that this *actually* removes the error, though, for reasons I will state below, however bfitz states that if compliance is 6.0, then the override should not cause an error. I will say trying to test this is absolutely infuriating, the most difficult part being trying to figure out how to get my project to actually get an ESB classpath container onto it, even with the presence of an EAP. When I am in the first page of the esb project wizard, automatically selected is my JBoss EAP 5.0 Server Runtime. Below it is also automatically selected "ESB Version: 4.7". Yet when I push forward two pages, it tells me my server does Not have esb 4.7 in it, I then have to go back two pages and change the facet version, then forward two pages to see if the error has disappeared. I finally gave up, as it one by one informed me that I do not have a satisfactory version in my EAP 5.0 runtime at all, which I find as extremely unlikely. At at least one attempt told me I did not even have a runtime selected, when the UI clearly did. (I eventually got confused enough that I did a du -a | grep -i "esb" command to see if the eap server had any jars or anything that mentioned "esb" anywhere in the file name. None did. So now I'm wondering if my install is just odd, but I don't suspect it is. I decide to switch to not using the "Server supplied runtime" and instead creating a new one on the third page, and I again pointed to my jboss-eap-5.0 folder. At no point did *this* dialog inform me that none of the versions were found. Instead I, once again, had to select each of the 6 versions to find out none were valid for this folder. I finally pointed directly to an actual esb server (jbossesb-server-4.4.GA) and hte dialog did auto-fill itself in, though I also remember *I* was hte one who made that fix about 2 months ago after a similarly infuriating attempt at this. However even after I do this, I notice in my Package Explorer that there is *NO* classpath container containing any ESB jars on hte project. So I check the .classpath file ot see if ANYTHING was added at all, and I see this: <classpathentry kind="con" path="server.supplied/SomeName"/> Aside from the ridiculously short and uninformative name "server.supplied", the adept user will note that this entry was not, actually, server supplied at all, but rather the *other* option, as I outlined abouve and pointed directly to an esb installation. Aside from that, this "server.supplied" is directly visible in the Java Build Path property page, under the Libraries tab. Which means this constant is exposed to users to see. Anyway, I've just continued testing and magically got a configuration that "just worked" (still not sure how). I can verify the @Override is still there, and there is no error. The end. Use the patch. And for god sakes please fix this wizard -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira