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 123159 - Groovy class structure in navigator
Summary: Groovy class structure in navigator
Status: VERIFIED FIXED
Alias: None
Product: groovy
Classification: Unclassified
Component: Editor (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker with 1 vote (vote)
Assignee: martin_adamek
URL: http://wiki.netbeans.org/wiki/view/Gr...
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-30 16:55 UTC by schmidtm
Modified: 2016-01-29 10:56 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description schmidtm 2007-11-30 16:55:09 UTC
Navigator Support for Groovy sourcecode.
Comment 1 martin_adamek 2008-03-06 08:27:03 UTC
Done.
Comment 2 Lukas Jungmann 2008-10-13 14:12:04 UTC
v.
Comment 3 hefest 2016-01-28 16:03:52 UTC
Broken again: Navigator shows an outline of the last open Java class, instead of the currently open Groovy class.

Using Maven 3 and Java 8 on Ubuntu 14.04.

Should I open a new bug report or should it be handled under this issue?
Comment 4 bruno.flavio 2016-01-28 23:31:59 UTC
(In reply to hefest from comment #3)
> Broken again: Navigator shows an outline of the last open Java class,
> instead of the currently open Groovy class.
> 
> Using Maven 3 and Java 8 on Ubuntu 14.04.
> 
> Should I open a new bug report or should it be handled under this issue?

Hi, thank you for the heads-up.
Could you create a new issue? Please include the NetBeans version and a reproducible test case.

Thank you!
Comment 5 hefest 2016-01-29 10:56:51 UTC
(In reply to bruno.flavio from comment #4)
> (In reply to hefest from comment #3)
> > Broken again: Navigator shows an outline of the last open Java class,
> > instead of the currently open Groovy class.
> > 
> > Using Maven 3 and Java 8 on Ubuntu 14.04.
> > 
> > Should I open a new bug report or should it be handled under this issue?
> 
> Hi, thank you for the heads-up.
> Could you create a new issue? Please include the NetBeans version and a
> reproducible test case.
> 
> Thank you!

Hm, tried it again and now it works. Go figure. :\

I have a number of maven projects open, 1 groovy-only and others predominantly Java: I've had some problems with false dependency errors so I've been clearing caches, building 3rd party deps. locally etc to make these false dependency errors disappear and I succeeded. I guess that might have something to do with it, but it would take too much experimenting to investigate what actually happened.

I'll leave it as it is for now and revisit the issue if it reappears. Thanks for the quick response!