Hello again, I have tested the same builds on MacOS X with a Java 6 implementation and am seeing the same results. This seems to happen whenever a build fails (i.e. due to a compilation error or failed test).
Is there someway to determine which component (plugin) causes that effect ? - Is there someone else experiencing the problem ? Thanks and best regards Andreas On Oct 13, 2010, at 9:32 AM, Andreas Gies wrote: > Hello Maveners > > I have recently used maven-3.0-beta-3 to get familar with Maven 3. Now, after > the release of Maven 3 I have run a couple of builds that > were working with 3.0-beta-3 and now randomly see a strange behavior on > Windows 7 64bit, Java 1.6-20 (64bit): > > It seems that "something" in the build process reduces random pom files in my > local repository to zero length, so that the next time > maven tries to access the pom file it throws an exception saying that the > pomo file has no content. deleting the artifact from the local > repository and rerunning the build sometimes succeeds, sometimes fails with > other pom's being shrunk. > > Has anyone seen that kind of behavior with Maven 3 ? > > Thanks and best regards > Andreas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
