> First, let me explain how 0.9.4 and previous versions deal with resources. > > Resources *source* folders is and has always been a pure "eye candy". > They made resources folders easier to spot in Package Explorer view, but > they always had "Excluded: **" regardless of separate/same output folder.
Yes, I know, but when I changed my build directory, I also changed this comportment to remove the "Excluded: **" for resources. > Before 0.9.4, m2eclipse sometimes added resources folders to classpath > and sometimes tried to copy/filter resources to appropriate output > folder. Unfortunately, this never worked reliably and was actually the > main reasons we decided to get rid of separate output folders (I tried > to explain this in better details here > http://markmail.org/message/733lqtw5moa4cim4). I do understand that filtered resources is quite hard to get with separate build folders, but I really still that for us that can do without resources filtering in eclipse, having the possibility (even with big warnings) to have a separate build directory would be a plus. > In 0.9.4, m2eclipse is always uses maven-resource-plugin to copy/filter > resources to maven output folder. This is supposed to happen both on > full eclipse builds and incrementally on resource changes. Actual > resource copy/filter logic did not change in 0.9.4, but we call this > code more often now. That can explain my problem. I did a project reconfiguration, but I did not trigger a clean of my projects. Unfortunately I cannot test it anymore as I reverted my installation of m2eclipse to 0.9.3. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
