Rob,
Just to reconfirm...
The following works fine from trunk (under Maven 2.2.1 on MacOSX and Java
1.6_0_22-b04):
mvn site-deploy -P standard,deploy-local -o
I must admit I didn't try without the -o; it was just taking too long on the
connection I'm on (internet cafe).
With a -o it zipped along though. Note that an internet connection is still
required, for the docbkx-maven-plugin to resolve DTDs.
~~~
I also tried running in a subdirectory, eg:
cd viewer/junit
mvn site-deploy -P deploy-local -o
This also worked; so did
cd applib
mvn site-deploy -P deploy-local -o
~~~
Looking at your build output for applib, I can see two differences, which
makes me wonder about versioning.
First, I don't get any warnings for the project reports.
Second, and perhaps more significantly, my build doesn't try to run
pdf:pdf. This is right, because for applib there is no pdf.xml file. Maybe
that's the thing to look into?
Worst case... if it's the pdf plugin that's breaking the build, we could
perhaps drop using it; now we've decided to standardize on docbkx, there's
less value in it.
Anyway, here's my applib output:
[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 "Dependency Convergence" report.
[INFO] Generating "Project Plugins" report.
[INFO] Generating "Project Summary" report.
[INFO] Generating "Dependencies" report.
[INFO] Generating Sitemap.
[INFO] [pdf:pdf {execution: pdf}]
[INFO] Skipped report generation.
[INFO] [docbkx:generate-html {execution: html-docs}]
[INFO] Executing tasks
[copy] Warning: /Users/dan/SVN/isis/trunk/applib/src/docbkx/style not
found.
[INFO] Executed tasks
[INFO] [docbkx:generate-pdf {execution: pdf-docs}]
[INFO] Executing tasks
[INFO] Executed tasks
[INFO] Executing tasks
[INFO] Executed tasks
[INFO] [site:jar {execution: jar}]
[INFO] Building jar:
/Users/dan/SVN/isis/trunk/applib/target/site/isis-0.1-SNAPSHOT-site.jar
[INFO] [site:deploy {execution: default-deploy}]
file:///tmp/m2-sites/isis/applib - Session: Opened
file:///tmp/m2-sites/isis/applib - Session: Disconnecting
file:///tmp/m2-sites/isis/applib - Session: Disconnected
Hope that's of some help...
Dan
~~~~
On 27 October 2010 18:13, Robert Matthews <[email protected]>wrote:
> A quick update.
>
> I have tried building on three machines now. Two fail as stated before.
> The third (on completely new machine) works through a good many projects
> then fails while trying to create a PDF for the headless viewer (Dan has
> just changed this so I'll make those changes and give it another go).
>
> Has anybody else other than Dan built all of the documentation? (Actually
> Dan. can you confirm that you've built it in it's entirety).
>
> 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
>>
>>
>>
>
