> Date: Sat, 24 Jul 2010 23:15:16 +0200 > From: Dennis Lundberg <[email protected]> > > This error usually shows up when there is a problem accessing the > central repository, or a corporate repository proxy.
Right; we periodically get timeouts from Central; that's why I wanted to set a fixed version for the skin. > Inheritance of site.xml from a parent is automatic, as long as the > parent pom has its site.xml attached to it when you deploy it to your > repository. Thanks. Is this documented somewhere? I searched a lot of places and could not determine how sites and parent poms worked. It was not at all obvious to me that I could run site-deploy on a parent pom project or that this would do something useful. And where exactly is the default skin and version specified - i.e. it not resolved locally when I added maven-default-skin 1.0 to our Artifactory repo - I assume because some default somewhere specifies a different version? > On 2010-07-23 17:34, David J. Biesack wrote: > > I'm seeing maven2 build failures because of the timeouts at central > > > > Caused by: org.apache.maven.doxia.tools.SiteToolException: > > ArtifactNotFoundException: The skin does not exist: Unable to determine the > > release version > > [...] > > -- > Dennis Lundberg -- David J. Biesack, SAS SAS Campus Dr. Cary, NC 27513 www.sas.com (919) 531-7771 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
