<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 10: Exclude resources at method level</title><link href="https://sourceforge.net/p/eclipse-metrics/feature-requests/10/" rel="alternate"/><link href="https://sourceforge.net/p/eclipse-metrics/feature-requests/10/feed.atom" rel="self"/><id>https://sourceforge.net/p/eclipse-metrics/feature-requests/10/</id><updated>2012-08-30T13:50:30Z</updated><subtitle>Recent changes to 10: Exclude resources at method level</subtitle><entry><title>Exclude resources at method level</title><link href="https://sourceforge.net/p/eclipse-metrics/feature-requests/10/" rel="alternate"/><published>2012-08-30T13:50:30Z</published><updated>2012-08-30T13:50:30Z</updated><author><name>Alex Oliveira</name><uri>https://sourceforge.net/u/alexro1986/</uri></author><id>https://sourceforge.nete16ebe46d9133ad8babdf0537c509c16764099ff</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;It would be really usefull to be able to exclude resources at the method level, not only at the file level.&lt;br /&gt;
The easiest example are the methods hashCode and equals. They are often generated automatically and we don't care about their cyclomatic complexity.&lt;/p&gt;
&lt;p&gt;Suggested solutions (one or many of):&lt;br /&gt;
- Expand the tree in the Resource Selection window until the method level (like in the Package Explorer View)&lt;br /&gt;
- Use regular expressions to exclude methods (like .*#equals)&lt;br /&gt;
- Put a comment on each methods to be excluded&lt;br /&gt;
(Using annotations may not be a good idea, since many code target SDK's lower than 1.5)&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>