That fixed it.  I'll be sure to do that first in the future. 

Thank you.




"Siegfried Goeschl" <[email protected]> 

03/31/2009 05:15 AM
Please respond to
"Maven Users List" <[email protected]>, [email protected]



To
"Maven Users List" <[email protected]>
cc

Subject
Re: The skin does not exist: Unable to determine the release version






Hi Jerry,

the bad news are that I had the same problem - the good news are that I
was able to get rid of the problem

E.g. run "mvn -U site" to force an update of your repo - thanks to Wendy
Smoak helping me with this issue ...

Cheers,

Siegfried Goeschl

Jerry Thome wrote:
> Sorry if I missed this as a recent posting.  Last night, several of my 
> Maven projects running in Hudson starting to fail with the same error 
> message.  Does the recent "site" plug-in release have anything to do 
with 
> this?
>
> It's becoming problematic to delete files in a repo and have maven 
> auto-download them, which seems to fix this problem.
>
> Thanks.
>
>
> [INFO] 
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] 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
>
>
>
>
>
>
> The information contained in this e-mail and any accompanying documents 
may contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if 
this message has been addressed to you in error, please immediately alert 
the sender by reply e-mail and then delete this message, including any 
attachments. Any dissemination, distribution or other use of the contents 
of this message by anyone other than the intended recipient is strictly 
prohibited. All messages sent to and from this e-mail address may be 
monitored as permitted by applicable law and regulations to ensure 
compliance with our internal policies and to protect our business. E-mails 
are not secure and cannot be guaranteed to be error free as they can be 
intercepted, amended, lost or destroyed, or contain viruses. You are 
deemed to have accepted these risks if you communicate with us by e-mail. 
>
>
>
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]






The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient is strictly prohibited. All messages 
sent to and from this e-mail address may be monitored as permitted by 
applicable law and regulations to ensure compliance with our internal policies 
and to protect our business. E-mails are not secure and cannot be guaranteed to 
be error free as they can be intercepted, amended, lost or destroyed, or 
contain viruses. You are deemed to have accepted these risks if you communicate 
with us by e-mail. 


Reply via email to