[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155797#action_155797 ] Connor Barry commented on MECLIPSE-165: --- Any updates yet? This is really a crucial fix for anybody using filtered resources, which is a basic requirement of a lot of projects... My workaround is to have a shell script that calls the maven goal, and additionally an ant script that modifies the resulting .classpath file to exclude ALL filtered resources, not only the **/*.java files. There's two regexes to account for the two possible attribute orders, which are seemingly random; just a hack, I'm sure there's a better way. - eclipse-config.bat: @echo off setlocal set _REALPATH=%~dp0 cd %_REALPATH% cls call %M2_HOME%/bin/mvn eclipse:clean eclipse:eclipse call %ANT_HOME%/bin/ant fix-classpath pause - build.xml (add a bogus env target if necessary): ?xml version=1.0? project name=xxx default=env target name=fix-classpath echo message=Fixing the WTP settings... / replaceregexp file=.classpath byline=true regexp pattern='(.*)excluding=\*\*/\*\.java(.*)path=src/main/resources-filtered(.*)' / substitution expression='\1excluding=**/*\2path=src/main/resources-filtered\3' / /replaceregexp replaceregexp file=.classpath byline=true regexp pattern='(.*)path=src/main/resources-filtered(.*)excluding=\*\*/\*\.java(.*)' / substitution expression='\1excluding=**/*\2path=src/main/resources-filtered\3' / /replaceregexp /target /project 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 Assignee: Brian Fox 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
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=137978#action_137978 ] Sergio Aguado commented on MECLIPSE-165: Any update of the fix? I need it in my current project. If there is any workaround please let me know 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 Assignee: Brian Fox 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
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125907 ] Jan Rudert commented on MECLIPSE-165: - Hello ? Any ETA for the release of the fix? I need it as well pretty urgently... 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 Assignee: Brian Fox 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
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125914 ] Brian Fox commented on MECLIPSE-165: See my comment from July, the current patch is no longer valid and the tests fail. 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 Assignee: Brian Fox 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
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119168 ] Kyle Lebel commented on MECLIPSE-165: - Any news on this? I'm currently using a work around, which processes the resources as an eclipse builder but it gets very clunky after every file save to have maven run it's builder. 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 Assignee: Brian Fox 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
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106262 ] Daniel Rijkhof commented on MECLIPSE-165: - I would really like this issue to be resolved. - a way to have resources in maven which do not end up in the classpath within eclipse 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 Assignee: Brian Fox 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
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101619 ] Brian Fox commented on MECLIPSE-165: Applied the patch and updated so it applied cleanly. The resulting classpath doesn't match the expected one. Although the resulting one actually has the excludes, the format seems curious to me. It's excluding **/*.java from the binary resources. The code is applied to a branch here: https://svn.apache.org/repos/asf/maven/plugins/branches/maven-eclipse-plugin-MECLIPSE-165 If you can look and provide a patch from this branch, then we can get it applied to trunk. Thanks. 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
[jira] Commented: (MECLIPSE-165) Ability to exclude filtered resources from eclipse's source directories
[ http://jira.codehaus.org/browse/MECLIPSE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100364 ] Paul Spencer commented on MECLIPSE-165: --- I have mentioned this issue in a post on Maven's users mailing list. The post is titled I use resource filtering with the Eclipse plugin but, need filtered directories excluded. Basically I am asking for the ability to exclude filtered resources from the eclipse classpath. Paul Spencer 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
[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
