[MECLIPSE-165] Ability to exclude filtered resources from eclipse's source directories

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.3
• Component/s: PDE support
• Flags: Patch
• Assignee: Brian E Fox
• Reporter: Cédric Vidal
• Created: 03/Oct/06 12:22
• Updated: 10/Mar/16 13:51
• Resolved: 25/Nov/14 15:38

Description

Resources should be in the classpath from Eclipse's point of view because they end up being in the classpath from Maven 2's point of view, but whenever resources are marked as being filtered by M2, Eclipse puts them unfiltered in the classpath thus introducing an inconsistency between Maven 2 and Eclipse.

Whether or not to include filtered resource directories in eclipse's sources directories is therefore a real dilemna. While I'm sure a consistent solution to this dilemna will eventually be found, it would be great to let the user choose what to do in the meantime.

The attached patch adresses this issue by adding a parameter, 'excludeFilteredResourcesFromSourceDirs', which when set to true prevents filtered resource directories from being added to eclipse's source directories. The parameter defaults to false to avoid changing current projects' behavior.

Regards,

Cédric Vidal
http://www.B-Process.com

PS: This parameter could be overriden on a per resource directory basis as mentionned in MECLIPSE-162. This is not adressed by the attached patch though

Issue Links

• relates to: MECLIPSE-621 mvn eclipse:eclipse fails or doesn't generate proper .classpath when specifying the same resource directory with different filtering rules
• relates to: MECLIPSE-48 eclipse:eclipse goal should handle includes and excludes of the maven-compiler-plugin
• relates to: MECLIPSE-162 Ability to exclude a resource / source path from being added to the classpath file