I've found the source of my problem.
In my settings.xml I was trying to turn of the use of Apache snapshot
repo using
<settings>
<profiles>
<profile>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties/>
<repositories>
<repository>
<snapshots>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</snapshots>
<id>apache.snapshots</id>
<url>http://repository.apache.org/snapshots</url>
</repository>
</repositories>
</profile>
</profiles>
</settings>
This actually has the effect of ensuring they are used. It turned out
that Maven was looking for the snapshot version of the unneeded default
skin. So in .m2-disabled/repository/org/apache/maven/skins$ tree
maven-default-skin/ I ended up with the files:
maven-default-skin/
|-- maven-metadata-apache.snapshots.xml
|-- maven-metadata-apache.snapshots.xml.sha1
|-- maven-metadata-central.xml
`-- maven-metadata-central.xml.sha1
However after deactivating the profile (and clearing out that directory
in the repo - not sure if that was necessary) I end up with:
maven-default-skin/
|-- 1.0
| |-- maven-default-skin-1.0.jar
| `-- maven-default-skin-1.0.jar.sha1
|-- maven-metadata-central.xml
`-- maven-metadata-central.xml.sha1
At which point it builds! If I add the -o flag it also bulds in a few
minutes, whereas without it took 20-30.
Now I can start looking at the documentation!
Regards
Rob
On 25/10/10 16:04, Robert Matthews wrote:
Has anybody else has problems building the site/documentation as per
Dan's instructions. I'm getting a peculiar Maven error, see below,
even though it has just downloaded the site artifact it is talking about.
Many mentions of it online where the problems typically is a missing
definition in site.xml. However in the root site.xml
(trunk/src/site/site.xml) there is our own skin defined (which I have
install per instructions).
Dan, I am assuming that you did not have this problem - although you
obviously did not do a new build as you where working on it. Anybody
built it or not?
Rob
[INFO]
------------------------------------------------------------------------
[INFO] Building Isis AppLib
[INFO] task-segment: [site-deploy]
[INFO]
------------------------------------------------------------------------
[INFO] [site:site {execution: default-site}]
[INFO] Parent project loaded from repository.
[INFO] Generating "Project Plugins" report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating "Dependency Convergence" report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating "Project Summary" report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating "Dependencies" report.
[WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
instance and no SinkFactory available. Please update this plugin.
[INFO] Generating Sitemap.
[INFO] [pdf:pdf {execution: pdf}]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[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
