Someone did fix this overnight, but they never sent any emails to the list regarding it. Guess they were embarrassed.
Well, scratch my last post. And thanks, whoever cleaned up the repository mess. Tom -----Original Message----- From: Thomas Harris Sent: Tuesday, February 02, 2010 10:08 AM To: [email protected] Subject: RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version So, will someone replace the broken maven-site-plugin version 2.1 that was put onto the public repositories over this last weekend so we can get back to work? Our team is stuck until this is fixed. Any chance the person who broke it could replace the jar with the last working version 2.1 jar? Why does anyone except the maven committers have the ability to replace core parts of maven for everyone? Tom Harris Tired of having to make excuses to the management -- View this message in context: http://n2.nabble.com/SiteToolException-ArtifactNotFoundException-The-skin-does-not-exist-Unable-to-determine-the-release-n-tp4496008p4501310.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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
