maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Kirchmeir (JIRA)" <>
Subject [jira] Updated: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
Date Fri, 27 Nov 2009 14:46:56 GMT


Florian Kirchmeir updated MECLIPSE-165:

    Attachment: ResourceExcludes.patch

I've implemented a "resourceExcludes" parameter, similar to the "sourceEcludes" added in version
This way, you can at least manually configure stuff you want to have excluded.

> Ability to exclude filtered resources from eclipse's source directories
> -----------------------------------------------------------------------
>                 Key: MECLIPSE-165
>                 URL:
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: New Feature
>          Components: PDE support
>    Affects Versions: 2.3
>            Reporter: Cédric Vidal
>            Assignee: Brian Fox
>         Attachments: MECLIPSE-165.patch, ResourceExcludes.patch
> 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
> 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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message