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.

Bug 148862 - [65cat] Select in Projects/Ctrl-Shift-1 broken for webflow pages
Summary: [65cat] Select in Projects/Ctrl-Shift-1 broken for webflow pages
Status: RESOLVED DUPLICATE of bug 174814
Alias: None
Product: groovy
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-01 15:12 UTC by goeh
Modified: 2009-10-21 15:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description goeh 2008-10-01 15:12:38 UTC 
[ BUILD # : 200810010242 ]
[ JDK VERSION : 1.6.0_07 ]

When editing a .GSP file under a normal view folder. If I press
Ctrl-Shift-1 (Select in Projects) the correct file is highlighted in
the Projects view.

But if I do the same for a Grails Webflow file, which is located one
more folder down, the correct file is not highlighted.
Ctrl-Shift-2 (Select in Files) works as expected on both file types.

Normal pages are located like this:
views
  editAgreement
    edit.gsp

Grails web flow pages are located under a folder for each flow, like
this:
views
  newAgreement
    newAgreementWizard
      step1.gsp
      step2.gsp
      ...
    selectCustomer
      select.gsp
      ...

Ctrl-Shift-2 works, but Ctrl-Shift-1 doesn't.
Comment 1 Petr Hejl 2008-11-19 15:17:34 UTC 
This seems to be working on trunk for me? Can you retest the issue with the trunk build?
Comment 2 goeh 2009-06-22 09:54:21 UTC 
Tested with 6.7RC3
Problem still exists.
Ctrl-Shift-1 does not select webflow pages.
Comment 3 Petr Hejl 2009-09-25 13:45:29 UTC 
Can't reproduce with daily :( Is it reproducible for you?
Comment 4 Petr Hejl 2009-10-21 15:45:09 UTC 
I believe this issue was a duplicate of issue 174814. It is resolved now. Please verify.

*** This issue has been marked as a duplicate of 174814 ***