maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas J. Harris (JIRA)" <j...@codehaus.org>
Subject [jira] Issue Comment Edited: (MNG-3139) The skin does not exist: Unable to determine the release version
Date Mon, 01 Feb 2010 18:00:55 GMT

    [ http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208823#action_208823
] 

Thomas J. Harris edited comment on MNG-3139 at 2/1/10 11:59 AM:
----------------------------------------------------------------

This defect is occurring again as of February 1st, 2010. Last Friday, the "site" mojo worked
perfectly, and this Monday morning, it's broken with the original error message:

--- clip ---

[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

--- /clip ---

Since we do not require any special configuration for the site, we do not have a site.xml
file, and shouldn't need one, right? CoC, anyone?

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.

Maven needs to be a bit more stable going forward... When things work fine one day, and the
next day it's all broken because a single person can screw up some essential part of Maven
in the central repo. We are seriously considering moving back to Ant at this point, as our
business cannot be hindered and held hostage by some maverick developer messing up the central
repo of core plugins. Reopen this ticket, and fix it, so we can build again, please.

      was (Author: tharrisx):
    This defect is occurring again as of February 1st, 2010. Last Friday, the "site" mojo
worked perfectly, and this Monday morning, it's broken with the original error message:

[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

Since we do not require any special configuration for the site, we do not have a site.xml
file, and shouldn't need one, right? CoC, anyone?

Maven needs to be a bit more stable going forward... When things work fine one day, and the
next day it's all broken because a single person can screw up some essential part of Maven
in the central repo. We are seriously considering moving back to Ant at this point, as our
business cannot be hindered and held hostage by some maverick developer messing up the central
repo of core plugins. Reopen this ticket, and fix it, so we can build again.

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.

  
> The skin does not exist: Unable to determine the release version
> ----------------------------------------------------------------
>
>                 Key: MNG-3139
>                 URL: http://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 contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message