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: | Groovy editor not using maven test scoped dependencies for hints; at least the for the test annotations | ||
---|---|---|---|
Product: | groovy | Reporter: | _ wadechandler <wadechandler> |
Component: | Editor | Assignee: | Martin Janicek <mjanicek> |
Status: | NEW --- | ||
Severity: | normal | CC: | wadechandler |
Priority: | P3 | ||
Version: | 7.3 | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Project showing the hint issue |
Description
_ wadechandler
2013-03-22 12:23:05 UTC
I have a project I am going to attach which demos this issue. Initially the build will fail because the import statements are not yet included in the GroovyEditorTestScopeUTest.groovy file, so if you add the right imports it will build, but before you do that, you can see the hint which is given. Created attachment 132945 [details]
Project showing the hint issue
So, if you grab the attachment I just put up, then you can open up the test file and see the issue. Now, I'm not sure yet if this only applies to the JUnit hint or not, or if it is something more pervasive where the groovy editor isn't using the test scope correctly in various places, but this is a specific example. I could see this being called a feature perhaps too, but the Java editor does it, so in reality it feels like a bug. Too, I bet if we click that hint, it will probably add a dependency other than the one we are using. When I say the Java editor does it...I mean it acts as expected. Gives the correct package name from our dep list. Thanks Wade. I remember I've been fixing something similar few months ago.. It's definitelly a defect, hint doesn't work correctly. Although the logic is almost certainly used only for the hint + maybe fix imports action, so it should not affect any other functionality. Decreasing priority to P3 issue as the workarround is pretty simple. Anyway, I agree this need to work.. I'll take a look at it during the next week.. |