[
http://jira.codehaus.org/browse/MNG-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126852
]
Matthew McCullough commented on MNG-3139:
-----------------------------------------
This is really putting egg on the face of this particular maven plugin at a
consulting client of mine. I'd like to cure it to get it back in good standing
with my customer. Is it really as simple as me deploying to the central repo
with -DupdateReleaseInfo=true? How do I get permissions to do that? I'll try
to help and fix it (I'm not one of those open source whiners that wants other
people to fix everything) but I need to be told how I get permissions to deploy
to the central repo.
Thanks in advance,
Matthew McCullough
[EMAIL PROTECTED]
> 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
> Issue Type: Bug
> Components: Sites & Reporting
> Affects Versions: 2.0.7
> Reporter: eyal david
> Assignee: Brett Porter
>
> 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
