Comment 65 for bug 427539

Revision history for this message
Brian Burch (brian-pingtoo) wrote :

I think I understand my problem, and also have a bypass.

When I created the clean karmic maven schroot system, I was surprised to find that it responded OK to "mvn --help", because this simple command would always crash on my "production" karmic system.

I went back to my production karmic system - the help worked fine (it had failed every time before), and I could build my sample project. What had changed?

Scratching around, I checked an backup copy of the ~/.m2/ directory.... it was full of stuff that maven had cached. However my mysteriously working production system and my schroot karmic and lucid systems all had almost-empty contents for this directory.

I guess that I had previously created a corrupt maven cache by copying .m2 onto my "production" karmic system. Something (probably running maven when not connected to the internet) had cleaned it out. With an almost-empty .m2, maven could respond to help. The next time I built my sample project while onlne, it automatically downloaded the correct support files and the build worked.

I suggest that anyone suffering from this bug tries the following bypass:

1. rename ~/.m2/ to something else.
2. mvn --help

... then, if the help runs OK...
3. cd myProject
4. mvn clean install

I hope that works for you as well as it does for me!