[
https://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327022#comment-327022
]
Chris Graham commented on MNG-3139:
-----------------------------------
In my case, it was an expired password in Archiva. Which makes sense. The local
Archiva is mirroring central, and the password had expired/been locked out, and
thus contact with the (proxied) central repo fails, which causes the error.
So put another way, when I see this error, it's time to reset the password.
I'm mostly putting this comment here for the benfit of others.
> The skin does not exist: Unable to determine the release version
> ----------------------------------------------------------------
>
> Key: MNG-3139
> URL: https://jira.codehaus.org/browse/MNG-3139
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Sites & Reporting
> Affects Versions: 2.0.7
> Reporter: eyal david
> Assignee: John Casey
> Fix For: 2.0.11, 2.1.0, 3.0-alpha-3
>
> Attachments: cached-metadata.patch, mvn_site_debug.zip
>
>
> hi I have problem generating site when im using the command mvn site
> it performs all stagegs and when it came to site generation the message is
> shown :
> 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
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
> do u have an idea what is the problem ?
> p.s the jar is registered in my local repository and in the remote repository
> thank u
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
