[ http://jira.codehaus.org/browse/MNGECLIPSE-92?page=comments#action_61822 ]
Brad Davis commented on MNGECLIPSE-92: -------------------------------------- While you can manually add a folder as a class path item for an individual debug or run configuration, I don't know of any way to do so at the project level, short of adding an item to the build path. If you know of some way to get folders to to appear on the default classpath of a projects debug config, other than what I'm doing, then that would be a solution. Of course my solution doesn't address a few other potential issues. For instance, the resource folders can have include / exclude settings in the pom, which can't be reflected in debugging (all files in the resources path will be included instead of just the ones specified by the pom). Another issue I'm hitting is that there's no way to order the test and non test resources to suit all circumstances. For instance, if I have an identically named file in both places, one with a DB connection used for the junit test, another with another DB setting, then one of them will always come first in debug and run configurations, regardless of whether I want to test or do debugging against the production DB. I don't know how to address this stuff at all right now. > Build path for resource directories should be 'exclude all' > ----------------------------------------------------------- > > Key: MNGECLIPSE-92 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-92 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Reporter: Brad Davis > Assignee: Eugene Kuleshov > Priority: Minor > Attachments: mvn2ide.patch > > > when you update the source folders in eclipse, resource folders are placed on > the build path in a naive manner. While they should be on the build path so > that running and debugging in eclipse places them in the class path, they > should have an exclude pattern of exclude all, so that any java files within > them will not be compiled and so that directories within the resources > folders will not appear as packages. > Attached is a patch that corrects this. -- 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
