It turns out that standalone "mvn clean" fails if "mvn install" wasn't called before.
Checkout trunk on a machine with empty local repo. Try "mvn clean" and it will fails. Now run "mvn install". The ODFToolkit jars are now in the local repo. Try "mvn clean" and it works. Delete the generated artifacts from local repo. "mvn clean" doesn't work any longer. Yegor On Thu, Dec 22, 2011 at 12:58 PM, Devin Han <[email protected]> wrote: > 2011/12/22 Yegor Kozlov <[email protected]> > >> I can reproduce it with Sun JDK 1.6.26 and Maven 3.0.3 on Win7 and Linux. >> >> My use case is to make a change, run "mvn test" and then check status >> with "svn status". >> Since the Validator module downloads .rng schemas from internet I see >> many not versioned files and this is annoying. >> > > I use Oracle JDK 1.6.0_29, still can reproduce it... > > I am preparing RC6 and want to know whether this issue is a blocker for the > first release? > > I'd rather not release with failing "mvn clean". Do you have anything special in Maven settings ? The behavior was the same on both WIn7 and Ubuntu: - checkout trunk - mvn install -Ppedantic Do you have Yegor
