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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Errors after upgrade to 2.2.1
We will drop the dependency reports for now. I'll just tell the developers on our teams to use the JDepend Eclipse plugin interactively on a regular basis until Maven gets fixed. Of course, now, the whole "site" shebang is broken anyway because of some 'missing skin' error, so until that gets fixed, we can't do squat. Tom -- View this message in context: http://n2.nabble.com/Errors-after-upgrade-to-2-2-1-tp4401158p4496342.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
