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
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
We have multiple Maven 2 builds and run Artifactory for a repo cache.
I've downloaded maven-default-skin-1.0 to our repo cache so it will be resolved
there,
but we still get the errors. Perhaps something is trying to reference a
snapshot skin,
but I don't know where it is coming from.
I've read what I can find; it seems I need to specify the skin in a site.xml
but
I don't want to duplicate that in more than a dozen projects - I want to
inherit it from a parent pom
that they all use.
The on-line Maven book discusses creating a skin or configuring a skin, but I
can find no doc on
how to configure the skin site.xml via the parent pom or otherwise configure so
that all projects pick
up the same skin - maven-default-skin 1.0.
Alternatively, is there is a fixed plug-in dependency that I can add to the
parent pom
so that it uses the 1.0 skin. We already have
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>2.1.1</version>
</plugin>
in the parent pom and we still get the above error sometimes.
thanks
--
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]