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.
Grails 3 introduced changes in the folder structure: [gradle folder] The gradle folder is incorrectly seen as a source folder, it contains the gradle wrapper. ['build' folder] The 'build' folder contains compiled sources, which shouldn't be visible (unless this interferes somehow with autocomplete?), this problem also exists in grails2 with the 'target' directory. [build.gradle] The build.gradle file is the build descriptor (akin to the pom.xml in a maven structure) and should be visible in the project tree. [gradle.properties] The gradle.properties is less important but still a configuration file that should appear in the project. The grails 2 application.properties file has the same issue.
The grails upgrading page contains useful information to determine what changed from the previous version: https://grails.github.io/grails-doc/latest/guide/upgrading.html
Hi Bruno, any update on this?
I'm producing a patch to make the build.gradle and gradle.properties visible on the project tree, so that the user doesn't need to switch from the Projects to the Files view to edit them. It should also fix the same problem with application.properties on grails2.
Removing waiver request keyword as P3 tasks don't need this. At the same time updating the blocked issue accordingly.
Created attachment 156136 [details] Proposed patch: creates a ProjectFiles category and hides the target folder. The proposed patch has the following changes: 1. Registers a new handler for the "Project Files" so that the application.properties in grails 2 and the build.gradle + gradle.properties in grails 3 exist in the project tree. 2. Hides the 'target' and 'gradle' folders from the project tree: these folders don't contain sources and as such should not appear as source folders. 3. Updates the grails icon to the one users currently expect. The previous icon stoped being used somewhere in 2009 and is now almost impossible to associate with grails ( http://web.archive.org/web/20090501000000*/http://www.grails.org ). Regarding the third change, the original image comes from the grails project source code ( https://github.com/grails/grails-core/tree/master/media/icons ), under the apache v2 license. From what I've read ( http://www.apache.org/licenses/GPL-compatibility.html ) this should be compatible. Anyway, if this is not OK please just ignore the changes to both 'GrailsIcon16x16.png' files in the patch.
Bruno, do you rather want to integrate this change yourself? The patch has still not been applied.
I've applied the patch in revision 4ce422512967: http://hg.netbeans.org/core-main/rev/4ce422512967
Integrated into 'main-silver', will be available in build *201511150002* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/4ce422512967 User: Bruno Fl
Ahmad, could you please verify this bug so that it can be included in the 8.1 Patch 1? Thanks!
(In reply to Jiri Kovalsky from comment #9) > Ahmad, could you please verify this bug so that it can be included in the > 8.1 Patch 1? Thanks! Grails 3 project structure is OK now. Application is now recognized as a Grails project and create-app, create-domain-class, generate-all and run-app commands are working and tested. Tested on dev build 201512140002.
Thanks Ahmad. Updating fields accordingly.
Regarding to grails 3 support in Netbeans I did some tests on Dev 201512260002 . I created new empty grails 3.0.11 project with following results : 1. Cannot create integration and unit test - see Report 221846 2. In the project window I don't see src folder 3. I cannot run / debug particular integration or unit test... (option in context menu is grey) 4. If I want to create new Groovy Junit test then I cannot choose correct location -there is no location for src... 5. Some Imports and some annotaions (for example @Integration) are marked as unresloved in code editor for files in src folder although project can be correctly builded using gradle... 6. Run Debug grails command results in window with message <There is no command matching the current filter> although no filter is set 7. Grails shell results : Error The Grails shell must be run from Gradle using 'gradle shell -q'
Pavle, please don't change resolutions arbitrarily. If I am not mistaken, you didn't contribute any source code nor you were given authority to decide what to do with this issue. Moreover complaining about 7 diverse issues in 1 task report is not helpful at all. If you feel something is wrong, please submit a separate bug report for each individual defect you see. Otherwise we end up with a total mess. Thank you for your understanding and cooperation.
Bruno, can you please integrate this fix to release81 branch by 1/31? Thanks!
The fix has been applied to the release81 branch.
Thanks Bruno. Do you have changeset number?
Sorry, here it is: Fix: http://hg.netbeans.org/releases/rev/dcab484a1df0 Spec version and message update: http://hg.netbeans.org/releases/rev/e6a78d0b0996