Details
-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.5.1Release
-
Fix Version/s: 2.5.2.Release
-
Component/s: Editor
-
Labels:None
-
Number of attachments :
Description
Currently, we explicitly disable much of the editing support for Groovy files that are not on the build path. This means that editing scripts, gradle files, or anything else not on the build path will not be too easy. Since we are trying to provide better gradle support, we should be doing something about this.
It would be nice to enable standard editor features like navigation, outline view, content assist, type inferencing, and dsl support.
I don't remember exactly why we disabled this in the past, but I do know that there were many exceptions being added to the log when editing files not on the build path.
I have been playing around with this in my local workspace and this is working quite well. By simply removing the guards on GroovyCompilationUnit.buildStructure and elsewhere, I now have navigation, content assist, type inferencing, and mark occurrences working. The caveats are that files outside of the build path cannot be referenced by any other files, search doesn't work inside of these files, and refactoring does not work. These are restrictions that is similar to those for Java files in JDT.