You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Geoffrey De Smet (JIRA)" <ji...@codehaus.org> on 2007/01/18 11:38:09 UTC
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered
resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=comments#action_85344 ]
Geoffrey De Smet commented on MECLIPSE-165:
-------------------------------------------
MECLIPSE-48 doesn't solve this: you don't want maven to exclude them, but you do want eclipse to exclude them.
Wouldn't it be a lot easier if by default the eclipse plugin just excludes all resources which are filtered by maven?
You never want eclipse to copy those for you... and most people create a separate "filtered-resources" directory anyway.
> Ability to exclude filtered resources from eclipse's source directories
> -----------------------------------------------------------------------
>
> Key: MECLIPSE-165
> URL: http://jira.codehaus.org/browse/MECLIPSE-165
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: PDE support
> Affects Versions: 2.3
> Reporter: Cédric Vidal
> Attachments: MECLIPSE-165.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
> 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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira