This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Created attachment 140381 [details] Debugging Screenshot of isCdiEnabled Method For CDI-enabled Project Method CdiUtil.isCdiEnabled is being called inside my project and returns FALSE instead of the expected TRUE on a CDI-enabled project, meaning a beans.xml file exists inside the project. This is a Jave EE 6 project for a Glassfish 3.1.2 deployment. A very traditional setup that used to work, but now doesn't. I've already done some preliminary debugging and have narrowed this down to a much deeper problem inside the following methods: * getBeansTargetFolder returns "null" * getDefaultBeansTargetFolder also returns "null" I am running following version: Product Version: NetBeans IDE 7.3.1 (Build 201306052037) Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01 Runtime: OpenJDK Runtime Environment 1.7.0_25-b30 System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb) (Debian GNU/Linux 7) The NetBeans source I used for debugging is located here: https://netbeans.org/downloads/zip.html javascript: download_file('zip/netbeans-7.3.1-201306052037-src.zip') This essentially breaks my module (I'm the maintainer of PrimeFaces CRUD Generator) for any CDI projects right now. Please advise.
Thanks, I suppose it's a duplicate for 230730 *** This bug has been marked as a duplicate of bug 230730 ***
I see that. Did you at least check out the screen shots? They may provide some valuable insight. Seems to be a deeper-rooted issue with how the routines find the target folders. This is really important to get fixed asap. To the others, this is merely a nuisance in the editor. To me, it breaks the code generators ability to detect CDI and generator the proper annotations in the xhtml code it generates because the result of that method is being passed on to the FreeMarker template engine. Thanks.
what do you mean by fixing asap? it's fixed but as 7.4 is already in 7.4 rc state , it not expected to work in 7.3.x
Sorry for my wording. You probably know better how it feels when people who depend on your work and something is broken get frustrated and want it fixed "asap". That's how I feel. I'm getting a few downvotes right now because of broken behavior in my "product" that I don't have control over because it's NetBeans functionality that's broken. So again, sorry for sounding pushy. So basically this is fixed in 7.4 and everybody should wait when it comes out. Right? Was there a reason this wasn't fixable as a patch in 7.3.1? (In reply to Sergey Petrov from comment #3) > what do you mean by fixing asap? > it's fixed but as 7.4 is already in 7.4 rc state , it not expected to work > in 7.3.x
the issue was introduced in 7.3.1( 7.3 patch2),you can also use 7.3/7.3 patch1