I no longer believe that this is a result of a switch. I removed my local repo and reran the build under 2.2.1 and got the same strange error which I sent into this list.
On Thu, Oct 21, 2010 at 9:06 AM, Jörg Schaible <[email protected]> wrote: > Hi, > > Benson Margulies wrote: > >> I ran a build with 3.0, and when I then retreated to 2.2.1, I got >> class-not-found errors in maven. Should I report this formally? > > that would be strange. I can switch forth and back as I like. Do you use an > M2_HOME environment setting and probably forget it to set it back? Best > practice is not to use it at all, because the variable is automatically set > executing the mvn batch/shell script. > > - Jörg > > > --------------------------------------------------------------------- > 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]
