Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 319222 - Need a way to undo/disable validation
Summary: Need a way to undo/disable validation
Status: NEW
Alias: None
Product: WTP Common Tools
Classification: WebTools
Component: wst.validation (show other bugs)
Version: 3.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: wst.validation CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-08 03:30 EDT by Aaron Digulla CLA
Modified: 2010-07-12 10:49 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Digulla CLA 2010-07-08 03:30:12 EDT
Build Identifier: 3.6 Helios

I ran validation on a bunch of old JSPs. Now I have > 7600 warnings and 5 errors in my problem view. These hide the actual errors and warnings.

Therefore I need a way to "clean" all validations errors/warnings for a folder in my project.

If possible, add an option (like "Derived") to the folder to exclude it from validation forever.

Reproducible: Always
Comment 1 Nitin Dahyabhai CLA 2010-07-08 04:35:33 EDT
You can set up filtering rules from the project's Validation property page.  You should also be able to remove the messages by deleting them in the Problems view.  Otherwise I'm unsure of what''s being requested.
Comment 2 Aaron Digulla CLA 2010-07-12 06:15:43 EDT
I unchecked the two options "JSP Content Validator" and "JSP Syntax Validator" but the errors in the problem view don't go away. I had to manually delete them.

Also, I'm using the Tomcat plugin which copies all resources to a folder in the project, so I get every error twice. I'd like to specify for the "tomcat" folder "don't validate this - ever!" so I can get validation for the JSP source folder but not for any copies.

Lastly, I have a folder with JSPs compiled to Java code where I can't disable specific Java warnings (like unused imports, unused private fields, etc). For code generators, it would be great if validation could be specified on a per-folder basis.
Comment 3 Valentin Baciu CLA 2010-07-12 10:49:41 EDT
Aaron,

As Nitin said, you can specify fine grained rules for validation. Just go to the validation preferences, select the validator you want to configure and click the ... button in the settings column. In there you can add various rules - including file and folder exclusion rules.

As for derived resources, the should not be validated anymore since WTP 3.1. See bug 276181.

The framework will prompt you for a rebuild when you change the preferences and should delete old markers in the process. Do you have the validation builder configured for your project? The builder is added automatically for certain projects (Java EE, web) but not for others (simple, Java).

I the above instructions are not helping, please attach a sample project with detailed steps on how to reproduce the problem and we'll look into it.

Hope this helps, Valentin