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 130334 [details] test case The attached file is displayed with a red exclamation mark icon in the project tree. The tooltip is "Error parsing file". When I open the file in editor I've no error message. Project charset is set to win-1252. System info : Product Version: NetBeans IDE 7.3 Beta 2 (Build 201211062253) Updates: NetBeans IDE is updated to version , NetBeans 7.3 Beta 2 Java: 1.6.0_38; Java HotSpot(TM) Client VM 20.13-b02 Runtime: Java(TM) SE Runtime Environment 1.6.0_38-b05 System: Windows XP version 5.1 running on x86; Cp1252; fr_FR (nb)
It's JS problem...html comment inside a <script> tag...
Works for me now. Might be related to #225442.
The project with the same files was not flagged in v.7.1.2 An attempt to open it in 7.4 Beta resulted in multiple flags. This is not practical to modify all the flagged files because many of them belong the framework(s) that are used in the project. So there should be some workaround for the problem.
It should work in 7.4 (dev build). *** This bug has been marked as a duplicate of bug 233066 ***
Created attachment 140514 [details] Sample php file that is flagged in Project tree
Comment on attachment 140514 [details] Sample php file that is flagged in Project tree The problem is still not resolved. This file is flagged in project tree. The file (as many others) belongs to the framework that I use so to modify it to get rid of the flag is not an option
This is a different problem not related to JS/PHP but CSS. The issue is name of css class "only" used on line 51. I think this will be handled with fixing issue 231249 *** This bug has been marked as a duplicate of bug 233066 ***
@Vladimir Riha This is a different problem not related to JS/PHP but CSS. The issue is name of css class "only" used on line 51. I think this will be handled with fixing issue 231249. ======================= As I mentioned I have a bunch of files in the project that are flagged. It is not clear how to report those problems without knowing in advance which type of parsing error, keyword or whatever causes it. It would make sense to open an "umbrella" case where all the reports and sample files would be collected and not to close this case until everything is resolved. Otherwise it will be shooting at the moving target. Also I am having these problems in RC1 (!) and this is not a minor issue. It practically will prevent me from using 7.4 at all when release candidate becomes an official release.
(In reply to luiz_bonfa from comment #8) > > As I mentioned I have a bunch of files in the project that are flagged. It > is not clear how to report those problems without knowing in advance which > type of parsing error, keyword or whatever causes it. I understand it might not always be clear. In such case, please report issue against product "ide", component "code" and we will reassign it to proper component.
(In reply to luiz_bonfa from comment #8) > @Vladimir Riha > This is a different problem not related to JS/PHP but CSS. The issue is name > of css class "only" used on line 51. I think this will be handled with > fixing issue 231249. > ======================= > > As I mentioned I have a bunch of files in the project that are flagged. It > is not clear how to report those problems without knowing in advance which > type of parsing error, keyword or whatever causes it. I think Vlada explained it. > It would make sense to > open an "umbrella" case where all the reports and sample files would be > collected and not to close this case until everything is resolved. Otherwise > it will be shooting at the moving target. Ok feel free to open such issue if you think the the issue 231249 is not the right one. But do not abuse existing unrelated issue - the component of this issue is _javascript_ and the case where editor is ok. In your case it is not javascript and the file is not ok in the editor. > Also I am having these problems in RC1 (!) and this is not a minor issue. It > practically will prevent me from using 7.4 at all when release candidate > becomes an official release. *** This bug has been marked as a duplicate of bug 233066 ***
@Petr Hejl "Ok feel free to open such issue if you think the the issue 231249 is not the right one. But do not abuse existing unrelated issue - the component of this issue is _javascript_ and the case where editor is ok. In your case it is not javascript and the file is not ok in the editor" =============================================== But this is exactly my point, that we do not know how to qualify these flags. The error flags appear only in project tree, next to the particular file. The file in the editor does not have any indication of the syntax or any other error. So we do not know which issue is the "right" one. I would rather do what Vlad Riha suggested. I will open some generic issue with product "ide", component "code" and with the title "The files have error flags in the project tree". I will attach a bunch of files from my project that have this problem. And then you guys analyze them, triage them and assign to the appropriate specific component and case. Will this work for you?
(In reply to luiz_bonfa from comment #11) > @Petr Hejl > > "Ok feel free to open such issue if you think the the issue 231249 is not > the right one. But do not abuse existing unrelated issue - the component of > this issue is _javascript_ and the case where editor is ok. In your case it > is not javascript and the file is not ok in the editor" > > =============================================== > But this is exactly my point, that we do not know how to qualify these > flags. The error flags appear only in project tree, next to the particular > file. The file in the editor does not have any indication of the syntax or > any other error. So we do not know which issue is the "right" one. At least in your sample I do get error in the editor. You don't have search for the right issue just create a new one. > > I would rather do what Vlad Riha suggested. I will open some generic issue > with product "ide", component "code" and with the title "The files have > error flags in the project tree". I will attach a bunch of files from my > project that have this problem. And then you guys analyze them, triage them > and assign to the appropriate specific component and case. > > Will this work for you? Yes. Reopening unrelated issue does not make any sense. *** This bug has been marked as a duplicate of bug 233066 ***
Created attachment 160052 [details] error
Created attachment 160053 [details] error