Unless careful precautions are made, Maven builds tend to rot over time. In this case, the site generation was not declared to occur during the packaging phase and specifying it on the command line caused it to run, but it was likely "cleaned" before the assembly was created. With the changes, "mvn package" which had been failing now completes. I think it is likely that mvn release:prepare would also pass too, but I want to look at Scott's right truncating field width patch before building a release candidate.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
