[ http://jira.codehaus.org/browse/MNGECLIPSE-189?page=comments#action_77085 ] Eugene Kuleshov commented on MNGECLIPSE-189: --------------------------------------------
It this moment I am not convinced that it will be a good idea. This is not needed for the projects that are not using properties rewrting, but in general we can't tell that without scanning all the properties (which is sounds like a hack to me). More over, some other projects may want to tweak such builder and add some other goals, for example to generate sources. Also, running maven on the whole source tree on every change of the single resource seem an overkill, so we would need some additional hooks into Maven to have better control on what resources it should run. As well as allow to launch Maven in the same VM as Eclipse... So, once again, please raise an objective objections against closing this issue as "worksome". > JUnit runner does not process resource filters before running > ------------------------------------------------------------- > > Key: MNGECLIPSE-189 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-189 > Project: Maven 2.x Extension for Eclipse > Issue Type: Bug > Affects Versions: 0.0.9 > Environment: Eclipse 3.1.2 Linux > Reporter: Jonathan Share > Assigned To: Eugene Kuleshov > Priority: Trivial > Attachments: filter-test.zip > > > I have a project that uses a resource filter to set the path to some files > depending on what platform the developer is on. Using maven on the command > line this is processed correctly and the Unit tests pass. However, I wish to > use the JUnit runner within eclipse however as my resources do not get > filtered before the tests try to load them I get exceptions creating URL > objects with ${news.image.url} in them. > Desired behaviour > =============== > This plugin should provide a launcher for the junit runner that first runs > the process-resources (apologies if this is wrong, writing from memory here) > target and ensure the classpath is configured correctly so that the non > processed resources are not available to the JUnit runner before running the > JUnit tests. -- 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
