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.
Summary: | Navigation in js code doesn't work in j2seproject | ||
---|---|---|---|
Product: | javascript | Reporter: | Milan Kubec <mkubec> |
Component: | Editor | Assignee: | Petr Pisl <ppisl> |
Status: | NEW --- | ||
Severity: | blocker | CC: | pjiricka |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
Milan Kubec
2008-03-25 13:55:15 UTC
More details please... what exact symbol are you clicking on, and where is it defined? Is it a function or a variable? Can you attach your source? I was editing file http://java.com/js/deployJava.js and I was clicking on usage of any function or variable defined inside deployJava. I can not reproduce this. I copied deployJava.js into my Rails project (a Web Project would also work). I then tried clicking on function calls, like deployJava.compareVersionToPattern( (I clicked on compareVersionToPattern - and it jumped to the right place. I clicked on the global var reference (deployJava) and it worked. I also clicked on the "jnlp" local variable in the launch method and it correctly jumped to the parameter list. Can you list more specifically what you did -- how did you edit deployJava.js (project type etc) - you cannot edit http resources directly. Which specific symbols did you click on? Also, can you try a more recent build? (If I read this correctly, you have a build that is nearly a month old). Perhaps try with a cleanuser dir also in case there is stale indexing data in there. It does not work at Java Project, at Web project works well. Yes, I can verify that navigation in JavaScript file inside web project works OK. I used j2seproject. Features based on the index, such as code completion and go to declaration, only work in projects enabled for JavaScript (such as Ruby on Rails and Web Project (e.g. see issue 131831). OK, then we can close the issue? Or do you plan to enable it also for other project types? I suggest leaving it open and treating it as a P4 defect. Milan agrees (as the submitter). Changing the summary. *** Issue 131831 has been marked as a duplicate of this issue. *** |