<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/pmd-eclipse/feature-requests/</id><updated>2011-03-18T18:14:28Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>Fail On Custom Priority Level</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/16/" rel="alternate"/><published>2011-03-18T18:14:28Z</published><updated>2011-03-18T18:14:28Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net031b6a0977f0e6b0e5ed4ca6f1ab2b17481e5c78</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;From the command line and maven plugin you can specify a specific priority level to fail on. In Eclipse however, only priority levels 1 and 2 (Error High and Error) are shown as failures. We also fail Warning High (priority 3) but in Eclipse this is shown as just a warning. Please could you add the option to specify the priority level to fail on.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Use URL for retrieving rulesets</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/15/" rel="alternate"/><published>2011-02-17T19:04:42Z</published><updated>2011-02-17T19:04:42Z</updated><author><name>Kevin</name><uri>https://sourceforge.net/u/kmbulebu/</uri></author><id>https://sourceforge.netf5ff7f0c93a3f4f2bc28cf96ae96cd72465e00ea</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Keeping my development team (1000 users) on a current PMD ruleset is a challenge.  Pushing out new ruleset xmls and asking developers to import is prone to problems.  Here's one way I think we can make it simpler.&lt;/p&gt;
&lt;p&gt;Allow PMD to be configured with a ruleset URL.  PMD will download the ruleset from that URL and use it.  If the URL is inaccessible (dev is working from home, for example), than just use the one downloaded last time.&lt;/p&gt;
&lt;p&gt;Another idea would be to model how checkstyle works.  With checkstyle you can create a plugin that extends a checkstyle extension point, allowing the configuration to be hard coded.  That's easy to maintain as well, since we use an internal eclipse update site that includes our latest checkstyle extensions.&lt;/p&gt;
&lt;p&gt;Either would be great for me. Thanks for the great work.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Support maven-pmd-plugin exclude's configuration from pom</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/14/" rel="alternate"/><published>2010-09-08T08:44:15Z</published><updated>2010-09-08T08:44:15Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netcfdb4d729d9053df8d6687bac0821a3fe1a7fa42</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;For some reason, one may disable PMD checking on some files.&lt;br /&gt;
With the maven-pmd-plugin, he can do this by "excludes" or "excludeRoots" configuration (http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#excludes)&lt;br /&gt;
So this works well under maven, but in Eclipse, excluded files remains in red, which is annoying&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Group exceptions by exception type</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/13/" rel="alternate"/><published>2008-04-03T02:12:01Z</published><updated>2008-04-03T02:12:01Z</updated><author><name/><uri>https://sourceforge.net</uri></author><id>https://sourceforge.net31faff2db959e0d8d3af864b3398334f908d0b82</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently, exceptions can be grouped by package name, by file name, or by package name/file name.  Please provide the ability to group exceptions by exception type.  This would allow developers to concentrate on particular exceptions across a potentially large number of files.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>long operations to run with progress monitor</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/12/" rel="alternate"/><published>2005-04-15T19:27:53Z</published><updated>2005-04-15T19:27:53Z</updated><author><name>Miguel Griffa</name><uri>https://sourceforge.net/u/mikkey/</uri></author><id>https://sourceforge.net044114a2227eafb2fabaedaf8bf9780af8162f41</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;ideally, these would have also the button that sends&lt;br /&gt;
the job to background, but at least a detailed progress&lt;br /&gt;
report and cancellation should be available&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add check license action</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/11/" rel="alternate"/><published>2005-04-13T20:21:20Z</published><updated>2005-04-13T20:21:20Z</updated><author><name>Miguel Griffa</name><uri>https://sourceforge.net/u/mikkey/</uri></author><id>https://sourceforge.net3bcf4cfe519f265c4949649162f1d1ce8efbf35c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This action would verify that LICENSE.txt is present in&lt;br /&gt;
each source file header, and add it if required&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Smarter visitor</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/10/" rel="alternate"/><published>2005-04-11T20:34:06Z</published><updated>2005-04-11T20:34:06Z</updated><author><name>Miguel Griffa</name><uri>https://sourceforge.net/u/mikkey/</uri></author><id>https://sourceforge.net636e4b62c6c9a60ca90907a5fcd65bca3fe0261d</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The AST visitors should use a flag to indicate when a&lt;br /&gt;
file has been modified and thus, needs to be saved,&lt;br /&gt;
this would improve performance of many operations&lt;br /&gt;
singnificantly&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Add .pmd.xml editor</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/9/" rel="alternate"/><published>2005-04-07T15:52:06Z</published><updated>2005-04-07T15:52:06Z</updated><author><name>Miguel Griffa</name><uri>https://sourceforge.net/u/mikkey/</uri></author><id>https://sourceforge.netdb3e0a33c0d741e6c784885f5c8822e3465bb5ee</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This editor shuold be very graphical, and may replace&lt;br /&gt;
the ugly UI of the current customization wizard&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Use different builder name from official plugin</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/8/" rel="alternate"/><published>2005-04-04T13:38:20Z</published><updated>2005-04-04T13:38:20Z</updated><author><name>Miguel Griffa</name><uri>https://sourceforge.net/u/mikkey/</uri></author><id>https://sourceforge.net1a620e8302d59d7e41fb043ae0f0f2b46e6adfd5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This would enable both plugins to coexist happily&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>add nature from wizard</title><link href="https://sourceforge.net/p/pmd-eclipse/feature-requests/7/" rel="alternate"/><published>2005-03-31T20:52:04Z</published><updated>2005-03-31T20:52:04Z</updated><author><name>Miguel Griffa</name><uri>https://sourceforge.net/u/mikkey/</uri></author><id>https://sourceforge.net17a12f43e9d41f359ad520c165924026ef33a3ec</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When customizing with wizard, if project does not&lt;br /&gt;
contain pmd nature, prompt the user to add it&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>