Another workaround I found is to modify one of the resource files. It calls "process-resources resources:testResources" and all my resources are copied in target/classes ...
On Sun, Jul 27, 2008 at 5:22 PM, nicolas de loof <[EMAIL PROTECTED]> wrote: > I also got this issue one more time, but have no idea what to do to > reproduce. > > I had to force a project clean + update project configuration to get it > working. > > 2008/7/27 Bouiaw <[EMAIL PROTECTED]> >> >> I confirm that this issue is always here. >> >> I currently work on a testCase project that could show this blocking >> issue outside of my company project. >> >> On Wed, Jul 23, 2008 at 6:11 PM, Igor Fedorenko <[EMAIL PROTECTED]> >> wrote: >> > Also, there were reports that somehow resources get deleted after being >> > copied to the target folder by Maven, but we were never able to >> > reproduce >> > and debug the problem. If you can provide sample project and steps to >> > reproduce the problem, I'd be happy to have a look. >> > >> > [1] http://docs.codehaus.org/display/M2ECLIPSE/Maven+build+lifecycle >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
