Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.1Release
-
Fix Version/s: 2.1.2Release
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Grails application typically have plugin dependencies. The code for these plugins may have warnings - the JDT compiler produces many more kinds of warning than typical javac so the plugin developer may not be aware of them. These plugin warnings make a mess when the grails app developer was just trying to consume the plugin and doesn't care about any issues within it.
If we can, we should ignore these warnings.
The easiest way to do this is to let the problems we created but then not add them to the resource if the resource is:
a) in a grails project
b) in a linked source folder in a grails project
and I'm only doing this for warnings right now. Errors will still come through.
The change can be made in ProblemHandler.handle(). We have a bit flag to identify a grails project.
This will mean warnings are hidden for 'other' linked source folders in the grails project, but that seems a very unusual setup. If that becomes an issue we will need to make our linked ones more identifiable. Yes, they have attributes but those attributes cannot be seen from where the decision is being made.