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 257961 - Grails3 project view does not show tests
Summary: Grails3 project view does not show tests
Status: STARTED
Alias: None
Product: groovy
Classification: Unclassified
Component: Grails (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: bruno.flavio
URL:
Keywords:
Depends on: 257835
Blocks: 254336
  Show dependency tree
 
Reported: 2016-02-12 12:30 UTC by ejaz_ahmed
Modified: 2016-09-20 10:20 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Behaviour when Java and Groovy classes are kept in the same folder (14.67 KB, image/png)
2016-09-11 16:41 UTC, bruno.flavio
Details
Patch that fixes the location of unit/integrations tests,and java/groovy sources. (2.30 KB, patch)
2016-09-11 16:50 UTC, bruno.flavio
Details | Diff
Groovy and Java sources in a maven project. (6.06 KB, image/png)
2016-09-19 17:04 UTC, bruno.flavio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ejaz_ahmed 2016-02-12 12:30:49 UTC
Tests have been moved to src folder in grails3 as a result, current view does not show them. To access to tests, yuo have to change to files view. Tests are now located in:

<project>/src/test
<project>/src/integration-test

Java and groovy sources are in
<project>/src/main
Comment 1 bruno.flavio 2016-09-11 16:41:05 UTC
Created attachment 161998 [details]
Behaviour when Java and Groovy classes are kept in the same folder

Thank you for reporting this issue.

Regarding the Java and Groovy sources, according to the migration manual [1] it seems they should be kept together in '<project>/src/main/groovy'? This causes a duplication on the project tree, as it can be seen in the attached screenshot.

[1]: http://docs.grails.org/3.0.x/guide/upgrading.html
Comment 2 bruno.flavio 2016-09-11 16:44:41 UTC
Marking this issue as dependent on #257835 (pending verification) as it requires the definition of source categories per Grails version.
Comment 3 bruno.flavio 2016-09-11 16:50:50 UTC
Created attachment 161999 [details]
Patch that fixes the location of unit/integrations tests,and java/groovy sources.
Comment 4 zoladkow 2016-09-19 08:50:23 UTC
Hi Bruno,

Your patch works miracles, however it is not integrated in sources (not in 8.2 RC, not in nightly), what can be done to change this?
Comment 5 bruno.flavio 2016-09-19 17:03:17 UTC
(In reply to zoladkow from comment #4)
> Hi Bruno,
> 
> Your patch works miracles, however it is not integrated in sources (not in
> 8.2 RC, not in nightly), what can be done to change this?

Hello and thank you for your interest.

There are two things that should be done in order to get this into the dev build:

1. This fix depends on issue #257835 which is still pending verification (and has a large patch). It would be great to have someone verify it before we proceed with this one.

If you have the opportunity please head to https://netbeans.org/bugzilla/show_bug.cgi?id=257835 and verify that the issue described has been fixed.

2. Please see the screenshot attached, I'm thinking that the best way to solve this could be the unification of the Java and Groovy sources under the same source category? I was hoping to get some feedback on this.
Comment 6 bruno.flavio 2016-09-19 17:04:33 UTC
Created attachment 162118 [details]
Groovy and Java sources in a maven project.
Comment 7 zoladkow 2016-09-20 10:20:02 UTC
Hi Bruno,

1) I voted on that blocker, hope this helps.

2) I'm all for having Java and Groovy src files shown together on Projects tab.
Having those classes under one project node makes them easier to browse. More logical.
But - I've also seen Grails 3 projects which still keep Java files separately and grails is not complaining about it. Can such case also be supported? Logically unified on project tree, but separated in file system?