Note that there are some explanatory texts on larger screens.

plurals
  1. POHow can I stop Eclipse warning about target folder's contents?
    primarykey
    data
    text
    <p>I'm getting loads of warnings from generated files in my <code>target</code> folder (e.g. Java code generated from XSDs or surefire reports) that I can't fix, and it's hiding proper warnings in my source code.</p> <p>Does anyone know of a way to tell Eclipse not to display warnings in certain folders, or just the "Derived" or target folders?</p> <p>I've only been able to find the following two "almost" solutions:</p> <ol> <li>The filter in the "Problems" view allows you to hide warnings containing (or not containing) a specific String in their description, but not part of their path or resource (file). Even if you could, this wouldn't be an ideal solution as the warnings would still be displayed on the project in the package explorer, hiding potential real warnings.</li> <li>With the latest Eclipse version (Juno / 4.2) in the "Java Build Path" settings under the "Source" tab, you can "ignore optional compile problems" from each <code>source</code> folder. But this obviously doesn't work for cases where the folders aren't source folders (like the surefire reports). It <em>does</em> however fix one specific problem with warnings about generated sources, but might not in others, where the sources aren't (can't be) included as source.</li> </ol> <p>It would just be nice if there was a way to tell eclipse not to display warnings about things in the target folder altogether, as it's often not very useful and might hide actual problems.</p> <p>Cheers,<br> &nbsp;&nbsp;&nbsp;&nbsp;Svend. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload