Thanks friend for taking the time... I do use a local repo.
Ok, I use to pre-populate tools.jar but I commented that out from my batch script months ago... because things built fine without it. I only use JAVA_HOME and never needed to create JRE_HOME. Why complicate things. #tools #call mvn install:install-file -DgroupId=com.sun -DartifactId=tools -Dversion=1.5.0 -Dpackaging=jar -Dfile=%JAVA_HOME%/lib/tools.jar Everything comes apart now and I do not understand why I have to reconfigure tools.jar into my local repo? Maybe because it was picked up in another repo? Something changed on the repo's overnight. To be safe your saying I need to pre-populate my own local repo... I will give that a shot. Any more solutions are welcome. It seems wagon-webdav, during local repo population at build time, results in a populated pom to my local repo that has java stack trace stuff in it... causing maven to choke. Why would my JAVA_HOME have anything to do with causing that? Still wondering who is to blame. tx ----- Best regards Ken in nashua -- View this message in context: http://www.nabble.com/Maven-broke-my-build-next-day---out-of-the-blue-remote-dependencies--tp15760163s177p15761124.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
