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: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
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: users@maven.apache.org 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
Friday, I was able to run the 'site' build on our project. This morning, I get the following error: [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE We've changed nothing, so something bad has occurred to something out on the public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on all platforms here when attempting to call mvn site on our project. I've updated this closed ticket. The ticket should be re-opened, as the same old problem is now occurring every 'site' build for us. Can someone please fix this soon? We cannot move forward on our project at this point. http://jira.codehaus.org/browse/MNG-3139 Tom
RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
I attempted the workaround listed in the ticket (http://jira.codehaus.org/browse/MNG-3139), namely: 1. Create a /src/site/site.xml file in the top-level maven project, containing: [Code] project skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-default-skin/artifactId version1.0/version /skin /project [/Code] Now the mvn site site-deploy works, however, there is no longer any links on the left-side menu, contrary to what I'd expect from a workaround. So, that's a bunk workaround. So, at this stage, our project is dead in the water until someone fixes the site plugin to get around this 'missing skin' defect. Every Hudson build fails with this error. Have users experienced similar issues in the past? How long does it usually take for a critical fix to get deployed to the central maven repos? Should I start writing the ant scripts for our projects? ;) Tom -Original Message- From: Thomas Harris Sent: Monday, February 01, 2010 1:26 PM To: users@maven.apache.org Subject: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Friday, I was able to run the 'site' build on our project. This morning, I get the following error: [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE We've changed nothing, so something bad has occurred to something out on the public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on all platforms here when attempting to call mvn site on our project. I've updated this closed ticket. The ticket should be re-opened, as the same old problem is now occurring every 'site' build for us. Can someone please fix this soon? We cannot move forward on our project at this point. http://jira.codehaus.org/browse/MNG-3139 Tom - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
On 2010-02-01 21:24, Thomas Harris wrote: I attempted the workaround listed in the ticket (http://jira.codehaus.org/browse/MNG-3139), namely: 1. Create a /src/site/site.xml file in the top-level maven project, containing: [Code] project skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-default-skin/artifactId version1.0/version /skin /project [/Code] Now the mvn site site-deploy works, however, there is no longer any links on the left-side menu, contrary to what I'd expect from a workaround. So, that's a bunk workaround. Which version of the Site Plugin are you using? There is a bug in version 2.1 about missing menu links. So, at this stage, our project is dead in the water until someone fixes the site plugin to get around this 'missing skin' defect. Every Hudson build fails with this error. Have users experienced similar issues in the past? How long does it usually take for a critical fix to get deployed to the central maven repos? Should I start writing the ant scripts for our projects? ;) Tom -Original Message- From: Thomas Harris Sent: Monday, February 01, 2010 1:26 PM To: users@maven.apache.org Subject: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Friday, I was able to run the 'site' build on our project. This morning, I get the following error: [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE We've changed nothing, so something bad has occurred to something out on the public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on all platforms here when attempting to call mvn site on our project. I've updated this closed ticket. The ticket should be re-opened, as the same old problem is now occurring every 'site' build for us. Can someone please fix this soon? We cannot move forward on our project at this point. http://jira.codehaus.org/browse/MNG-3139 Tom - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version
I have been using version 2.1 of the maven-site-plugin all along; When I had no site.xml file, I got all my menu items and they all worked. Now, without the site.xml file, the 'site' build fails as described. With the site.xml file detailed below, the 'site' build succeeds, however the resulting site has no links at all on the left hand side. :| Tom -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Monday, February 01, 2010 3:32 PM To: Maven Users List Subject: Re: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version On 2010-02-01 21:24, Thomas Harris wrote: I attempted the workaround listed in the ticket (http://jira.codehaus.org/browse/MNG-3139), namely: 1. Create a /src/site/site.xml file in the top-level maven project, containing: [Code] project skin groupIdorg.apache.maven.skins/groupId artifactIdmaven-default-skin/artifactId version1.0/version /skin /project [/Code] Now the mvn site site-deploy works, however, there is no longer any links on the left-side menu, contrary to what I'd expect from a workaround. So, that's a bunk workaround. Which version of the Site Plugin are you using? There is a bug in version 2.1 about missing menu links. So, at this stage, our project is dead in the water until someone fixes the site plugin to get around this 'missing skin' defect. Every Hudson build fails with this error. Have users experienced similar issues in the past? How long does it usually take for a critical fix to get deployed to the central maven repos? Should I start writing the ant scripts for our projects? ;) Tom -Original Message- From: Thomas Harris Sent: Monday, February 01, 2010 1:26 PM To: users@maven.apache.org Subject: SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Friday, I was able to run the 'site' build on our project. This morning, I get the following error: [INFO] SiteToolException: ArtifactNotFoundException: The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE We've changed nothing, so something bad has occurred to something out on the public repositories. I'm running Maven v2.2.1, with Java 1.6.0_17, on Windows XP SP2 64bit, but it seems to occur for everyone (we all have Maven v2.2.1) on all platforms here when attempting to call mvn site on our project. I've updated this closed ticket. The ticket should be re-opened, as the same old problem is now occurring every 'site' build for us. Can someone please fix this soon? We cannot move forward on our project at this point. http://jira.codehaus.org/browse/MNG-3139 Tom - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
