You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Craig L Russell <Cr...@Sun.COM> on 2008/03/29 22:17:19 UTC
Fwd: Trouble generating the site
Hi,
We are using maven to generate the Apache JDO site (http://svn.apache.org/viewvc/db/jdo/site/
).
We upgraded from Maven 1.0.2 to Maven 1.1 and the site no longer
generates.
The full console output is below [1].
The error message is
>> Unable to obtain goal [site]
>> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
(No such file or directory)
Any ideas?
Thanks,
Craig
Begin forwarded message:
> From: Andy Jefferson <an...@jpox.org>
> Date: March 29, 2008 12:42:14 AM PDT
> To: jdo-dev@db.apache.org
> Subject: Re: Trouble generating the site
> Reply-To: jdo-dev@db.apache.org
>
> Hi,
>
> I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it
> works and I
> don't trust the (lack of) backwards compatibility concerns of the
> Maven
> project
>
>> I see the same error as Craig if I run 'maven site' in jdo/site. I
>> also
>> have a site.jsl in my
>> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But there
>> is a
>> (different) site.jsl checked in into jdo/site/xdocs. In addition the
>> file project.properties in jdo/site defines a property
>> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property 'maven
>> site'
>> succeds.
>
> There is a different "site.jsl" checked in to xdocs because that is
> there to
> override the default site generation of Maven1. Without it you get a
> chunky
> site with none of the refinements that were added ;-)
>
> maven-xdoc-plugin is *supposed* to allow overriding the default
> stylesheet via
> the property "maven.xdoc.jsl" (not that they can be bothered to
> document
> it) ... hence why it is in project.properties pointing to ours. It
> currently
> doesn't have ${basedir} prepended and maybe should have (but that
> doesn't
> solve this issue anyway so ignore that).
>
> The maven-xdoc-plugin bundled with Maven1.0.2 accepts that
> overriding. The one
> that comes with Maven1.1 accepts it so far (since it even prints out
> the "site.jsl" it will use ... correctly) but then tries to append
> that name
> on the end of the plugin workspace!!! duh.
>
> If you chase the process through the plugin.jelly of that plugin you
> get to
> <x:parse var="doc" xml="${file}"/>
> <j:file name="${outFile}" encoding="${outputencoding}"
> omitXmlDeclaration="true" outputMode="xml"
> prettyPrint="no">
> <j:include uri="${stylesheet.toString()}"/>
> </j:file>
>
> which has the correct stylesheet name going in (ours). Where that
> then goes to
> I've no idea.
>
> Maybe some Maven team member could comment, and there's some secret
> setting
> that you have to use to get it to work with your own site.jsl file
> in Maven
> 1.1 ?
>
>
>
> --
> Andy (Java Persistent Objects - http://www.jpox.org)
[1]
[CraigRussell:~/apache/jdo/site] clr% svn status
[CraigRussell:~/apache/jdo/site] clr% svn up
At revision 642332.
[CraigRussell:~/apache/jdo/site] clr% maven clean
site __ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1
build:start:
clean:clean:
xdoc:clean:
clean:
site:
xdoc:register-reports:
maven-javadoc-plugin:register:
[mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc
[mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src
site:run-reports:
xdoc:init-i18n:
[echo] Init the i18n support
xdoc:init:
[echo] Generates the directory structure required for xdocs
[mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated-
xdocs
[mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs
xdoc:i18n-validation:
[echo] Validation of the locale entries
xdoc:register-reports:
maven-javadoc-plugin:register:
xdoc:generate-from-pom:
[echo] Generating xdocs from POM ...
xdoc:transform:
xdoc:init-i18n:
xdoc:init:
[echo] Generates the directory structure required for xdocs
xdoc:copy-resources:
[copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/
style
[copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/
images
xdoc:init-i18n:
xdoc:init:
[echo] Generates the directory structure required for xdocs
Copying user supplied resources.
xdoc:copy-user-resources:
[copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs
[copy] Copied 3 empty directories to 2 empty directories under /
Users/clr/apache/jdo/site/target/docs
xdoc:init-i18n:
xdoc:init:
[echo] Generates the directory structure required for xdocs
xdoc:jelly-init:
xdoc:register-reports:
maven-javadoc-plugin:register:
xdoc:jelly-transform:
About to use JSL stylesheet xdocs/site.jsl
[echo] en
[echo] The current Locale is the default one
[echo] Scanning '/Users/clr/apache/jdo/site/target/generated-
xdocs'...
[echo] Generating /Users/clr/apache/jdo/site/target/docs/
dependencies.html from /Users/clr/apache/jdo/site/target/generated-
xdocs/dependencies.xml
-------------------------------------------------------------------------------
>> Unable to obtain goal [site]
>> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
(No such file or directory)
-------------------------------------------------------------------------------
BUILD FAILED
-------------------------------------------------------------------------------
Total time : 20 seconds
Finished at : Friday, March 28, 2008 11:47:38 AM PDT
Final Memory : 8M/15M
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Fwd: Trouble generating the site
Posted by Lukas Theussl <lt...@apache.org>.
I had a closer look at this (bugged me because I remember working on a
fix for custom style sheets before m1.1... ;) )
One issue you might experience concerns the number of slashes in the
file url prefix. Depending on your OS, especially on different Windows
versions, you might need
maven.xdoc.jsl=file://${basedir}/xdocs/site.jsl
or even three slashes.
The second problem is that you have an xpath syntax error in your custom
style sheet, line 154 in site.jsl should read:
<jsl:applyTemplates select="$nav/body/menu[not(@type)] |
$nav/body/menu[@type='header'] | $nav/body/search"/>
With that the jdo site builds fine for me.
HTH,
-Lukas
Lukas Theussl wrote:
> You have to use the form
>
> maven.xdoc.jsl=file:/${basedir}/xdocs/site.jsl
>
> in project.properties, this will find the style sheet. However, I'm
> still getting a build error after that, so before I dig into it: do you
> really need the custom style sheet? The site builds fine with the
> default jsl.
>
> -Lukas
>
>
> Craig L Russell wrote:
>
>> Hi,
>>
>> We are using maven to generate the Apache JDO site
>> (http://svn.apache.org/viewvc/db/jdo/site/ ).
>>
>> We upgraded from Maven 1.0.2 to Maven 1.1 and the site no longer
>> generates.
>>
>> The full console output is below [1].
>>
>> The error message is
>> >> Unable to obtain goal [site]
>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
>> (No such file or directory)
>>
>> Any ideas?
>>
>> Thanks,
>>
>> Craig
>>
>> Begin forwarded message:
>>
>>> From: Andy Jefferson <an...@jpox.org>
>>> Date: March 29, 2008 12:42:14 AM PDT
>>> To: jdo-dev@db.apache.org
>>> Subject: Re: Trouble generating the site
>>> Reply-To: jdo-dev@db.apache.org
>>>
>>> Hi,
>>>
>>> I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it
>>> works and I
>>> don't trust the (lack of) backwards compatibility concerns of the Maven
>>> project
>>>
>>>> I see the same error as Craig if I run 'maven site' in jdo/site. I
>>>> also
>>>> have a site.jsl in my
>>>> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But there is a
>>>> (different) site.jsl checked in into jdo/site/xdocs. In addition the
>>>> file project.properties in jdo/site defines a property
>>>> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property 'maven
>>>> site'
>>>> succeds.
>>>
>>>
>>>
>>> There is a different "site.jsl" checked in to xdocs because that is
>>> there to
>>> override the default site generation of Maven1. Without it you get a
>>> chunky
>>> site with none of the refinements that were added ;-)
>>>
>>> maven-xdoc-plugin is *supposed* to allow overriding the default
>>> stylesheet via
>>> the property "maven.xdoc.jsl" (not that they can be bothered to
>>> document
>>> it) ... hence why it is in project.properties pointing to ours. It
>>> currently
>>> doesn't have ${basedir} prepended and maybe should have (but that
>>> doesn't
>>> solve this issue anyway so ignore that).
>>>
>>> The maven-xdoc-plugin bundled with Maven1.0.2 accepts that
>>> overriding. The one
>>> that comes with Maven1.1 accepts it so far (since it even prints out
>>> the "site.jsl" it will use ... correctly) but then tries to append
>>> that name
>>> on the end of the plugin workspace!!! duh.
>>>
>>> If you chase the process through the plugin.jelly of that plugin you
>>> get to
>>> <x:parse var="doc" xml="${file}"/>
>>> <j:file name="${outFile}" encoding="${outputencoding}"
>>> omitXmlDeclaration="true" outputMode="xml"
>>> prettyPrint="no">
>>> <j:include uri="${stylesheet.toString()}"/>
>>> </j:file>
>>>
>>> which has the correct stylesheet name going in (ours). Where that
>>> then goes to
>>> I've no idea.
>>>
>>> Maybe some Maven team member could comment, and there's some secret
>>> setting
>>> that you have to use to get it to work with your own site.jsl file
>>> in Maven
>>> 1.1 ?
>>>
>>>
>>>
>>> --
>>> Andy (Java Persistent Objects - http://www.jpox.org)
>>
>>
>>
>> [1]
>> [CraigRussell:~/apache/jdo/site] clr% svn status
>> [CraigRussell:~/apache/jdo/site] clr% svn up
>> At revision 642332.
>> [CraigRussell:~/apache/jdo/site] clr% maven clean
>> site __ __
>> | \/ |__ _Apache__ ___
>> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>> |_| |_\__,_|\_/\___|_||_| v. 1.1
>>
>> build:start:
>>
>> clean:clean:
>> xdoc:clean:
>>
>>
>> clean:
>>
>> site:
>> xdoc:register-reports:
>> maven-javadoc-plugin:register:
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src
>>
>>
>> site:run-reports:
>>
>> xdoc:init-i18n:
>> [echo] Init the i18n support
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated-
>> xdocs
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs
>>
>> xdoc:i18n-validation:
>> [echo] Validation of the locale entries
>>
>> xdoc:register-reports:
>> maven-javadoc-plugin:register:
>>
>>
>> xdoc:generate-from-pom:
>> [echo] Generating xdocs from POM ...
>>
>>
>>
>>
>>
>> xdoc:transform:
>> xdoc:init-i18n:
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>>
>> xdoc:copy-resources:
>> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/
>> style
>> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/
>> images
>>
>> xdoc:init-i18n:
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>> Copying user supplied resources.
>>
>> xdoc:copy-user-resources:
>> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs
>> [copy] Copied 3 empty directories to 2 empty directories under /
>> Users/clr/apache/jdo/site/target/docs
>>
>> xdoc:init-i18n:
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>>
>> xdoc:jelly-init:
>>
>> xdoc:register-reports:
>> maven-javadoc-plugin:register:
>>
>>
>> xdoc:jelly-transform:
>> About to use JSL stylesheet xdocs/site.jsl
>> [echo] en
>> [echo] The current Locale is the default one
>> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated-
>> xdocs'...
>> [echo] Generating /Users/clr/apache/jdo/site/target/docs/
>> dependencies.html from /Users/clr/apache/jdo/site/target/generated-
>> xdocs/dependencies.xml
>> -------------------------------------------------------------------------------
>>
>> >> Unable to obtain goal [site]
>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
>> (No such file or directory)
>> -------------------------------------------------------------------------------
>>
>> BUILD FAILED
>> -------------------------------------------------------------------------------
>>
>> Total time : 20 seconds
>> Finished at : Friday, March 28, 2008 11:47:38 AM PDT
>> Final Memory : 8M/15M
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Fwd: Trouble generating the site
Posted by Lukas Theussl <lt...@apache.org>.
You have to use the form
maven.xdoc.jsl=file:/${basedir}/xdocs/site.jsl
in project.properties, this will find the style sheet. However, I'm
still getting a build error after that, so before I dig into it: do you
really need the custom style sheet? The site builds fine with the
default jsl.
-Lukas
Craig L Russell wrote:
> Hi,
>
> We are using maven to generate the Apache JDO site
> (http://svn.apache.org/viewvc/db/jdo/site/ ).
>
> We upgraded from Maven 1.0.2 to Maven 1.1 and the site no longer
> generates.
>
> The full console output is below [1].
>
> The error message is
> >> Unable to obtain goal [site]
> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl (No
> such file or directory)
>
> Any ideas?
>
> Thanks,
>
> Craig
>
> Begin forwarded message:
>
>> From: Andy Jefferson <an...@jpox.org>
>> Date: March 29, 2008 12:42:14 AM PDT
>> To: jdo-dev@db.apache.org
>> Subject: Re: Trouble generating the site
>> Reply-To: jdo-dev@db.apache.org
>>
>> Hi,
>>
>> I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it
>> works and I
>> don't trust the (lack of) backwards compatibility concerns of the Maven
>> project
>>
>>> I see the same error as Craig if I run 'maven site' in jdo/site. I also
>>> have a site.jsl in my
>>> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But there is a
>>> (different) site.jsl checked in into jdo/site/xdocs. In addition the
>>> file project.properties in jdo/site defines a property
>>> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property 'maven site'
>>> succeds.
>>
>>
>> There is a different "site.jsl" checked in to xdocs because that is
>> there to
>> override the default site generation of Maven1. Without it you get a
>> chunky
>> site with none of the refinements that were added ;-)
>>
>> maven-xdoc-plugin is *supposed* to allow overriding the default
>> stylesheet via
>> the property "maven.xdoc.jsl" (not that they can be bothered to document
>> it) ... hence why it is in project.properties pointing to ours. It
>> currently
>> doesn't have ${basedir} prepended and maybe should have (but that
>> doesn't
>> solve this issue anyway so ignore that).
>>
>> The maven-xdoc-plugin bundled with Maven1.0.2 accepts that
>> overriding. The one
>> that comes with Maven1.1 accepts it so far (since it even prints out
>> the "site.jsl" it will use ... correctly) but then tries to append
>> that name
>> on the end of the plugin workspace!!! duh.
>>
>> If you chase the process through the plugin.jelly of that plugin you
>> get to
>> <x:parse var="doc" xml="${file}"/>
>> <j:file name="${outFile}" encoding="${outputencoding}"
>> omitXmlDeclaration="true" outputMode="xml"
>> prettyPrint="no">
>> <j:include uri="${stylesheet.toString()}"/>
>> </j:file>
>>
>> which has the correct stylesheet name going in (ours). Where that
>> then goes to
>> I've no idea.
>>
>> Maybe some Maven team member could comment, and there's some secret
>> setting
>> that you have to use to get it to work with your own site.jsl file in
>> Maven
>> 1.1 ?
>>
>>
>>
>> --
>> Andy (Java Persistent Objects - http://www.jpox.org)
>
>
> [1]
> [CraigRussell:~/apache/jdo/site] clr% svn status
> [CraigRussell:~/apache/jdo/site] clr% svn up
> At revision 642332.
> [CraigRussell:~/apache/jdo/site] clr% maven clean
> site __ __
> | \/ |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.1
>
> build:start:
>
> clean:clean:
> xdoc:clean:
>
>
> clean:
>
> site:
> xdoc:register-reports:
> maven-javadoc-plugin:register:
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src
>
>
> site:run-reports:
>
> xdoc:init-i18n:
> [echo] Init the i18n support
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated- xdocs
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs
>
> xdoc:i18n-validation:
> [echo] Validation of the locale entries
>
> xdoc:register-reports:
> maven-javadoc-plugin:register:
>
>
> xdoc:generate-from-pom:
> [echo] Generating xdocs from POM ...
>
>
>
>
>
> xdoc:transform:
> xdoc:init-i18n:
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
>
> xdoc:copy-resources:
> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/ style
> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/
> images
>
> xdoc:init-i18n:
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
> Copying user supplied resources.
>
> xdoc:copy-user-resources:
> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs
> [copy] Copied 3 empty directories to 2 empty directories under /
> Users/clr/apache/jdo/site/target/docs
>
> xdoc:init-i18n:
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
>
> xdoc:jelly-init:
>
> xdoc:register-reports:
> maven-javadoc-plugin:register:
>
>
> xdoc:jelly-transform:
> About to use JSL stylesheet xdocs/site.jsl
> [echo] en
> [echo] The current Locale is the default one
> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated- xdocs'...
> [echo] Generating /Users/clr/apache/jdo/site/target/docs/
> dependencies.html from /Users/clr/apache/jdo/site/target/generated-
> xdocs/dependencies.xml
> -------------------------------------------------------------------------------
>
> >> Unable to obtain goal [site]
> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl (No
> such file or directory)
> -------------------------------------------------------------------------------
>
> BUILD FAILED
> -------------------------------------------------------------------------------
>
> Total time : 20 seconds
> Finished at : Friday, March 28, 2008 11:47:38 AM PDT
> Final Memory : 8M/15M
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Trouble generating the site
Posted by Martin Gainty <mg...@hotmail.com>.
I saw this answer from a POX engineer who suggested your stylesheet is exhausting memory..export MAVEN_OPTS="-Xmx512m"Anyone?Martin ______________________________________________Disclaimer and confidentiality noteEverything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.> Date: Sat, 29 Mar 2008 14:17:19 -0700> Wrom: AIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGcked in to xdocs because that is > > there to> > override the default site generation of Maven1. Without it you get a > > chunky> > site with none of the refinements that were added ;-)> >> > maven-xdoc-plugin is *supposed* to allow overriding the default > > stylesheet via> > the property "maven.xdoc.jsl" (not that they can be bothered to > > document> > it) ... hence why it is in project.properties pointing to ours. It > > currently> > doesn't have ${basedir} prepended and maybe should have (but that > > doesn't> > solve this issue anyway so ignore that).> >> > The maven-xdoc-plugin bundled with Maven1.0.2 accepts that > > overriding. The one> > that comes with Maven1.1 accepts it so far (since it even prints out> > the "site.jsl" it will use ... correctly) but then tries to append > > that name> > on the end of the plugin workspace!!! duh.> >> > If you chase the process through the plugin.jelly of that plugin you > > get to> > <x:parse var="doc" xml="${file}"/>> > <j:file name="${outFile}" encoding="${outputencoding}"> > omitXmlDeclaration="true" outputMode="xml"> > prettyPrint="no">> > <j:include uri="${stylesheet.toString()}"/>> > </j:file>> >> > which has the correct stylesheet name going in (ours). Where that > > then goes to> > I've no idea.> >> > Maybe some Maven team member could comment, and there's some secret > > setting> > that you have to use to get it to work with your own site.jsl file > > in Maven> > 1.1 ?> >> >> >> > -- > > Andy (Java Persistent Objects - http://www.jpox.org)> > [1]> [CraigRussell:~/apache/jdo/site] clr% svn status> [CraigRussell:~/apache/jdo/site] clr% svn up> At revision 642332.> [CraigRussell:~/apache/jdo/site] clr% maven clean > site __ __> | \/ |__ _Apache__ ___> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~> |_| |_\__,_|\_/\___|_||_| v. 1.1> > build:start:> > clean:clean:> xdoc:clean:> > > clean:> > site:> xdoc:register-reports:> maven-javadoc-plugin:register:> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src> > > site:run-reports:> > xdoc:init-i18n:> [echo] Init the i18n support> > xdoc:init:> [echo] Generates the directory structure required for xdocs> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated- > xdocs> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs> > xdoc:i18n-validation:> [echo] Validation of the locale entries> > xdoc:register-reports:> maven-javadoc-plugin:register:> > > xdoc:generate-from-pom:> [echo] Generating xdocs from POM ...> > > > > > xdoc:transform:> xdoc:init-i18n:> > xdoc:init:> [echo] Generates the directory structure required for xdocs> > xdoc:copy-resources:> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/ > style> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/ > images> > xdoc:init-i18n:> > xdoc:init:> [echo] Generates the directory structure required for xdocs> Copying user supplied resources.> > xdoc:copy-user-resources:> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs> [copy] Copied 3 empty directories to 2 empty directories under / > Users/clr/apache/jdo/site/target/docs> > xdoc:init-i18n:> > xdoc:init:> [echo] Generates the directory structure required for xdocs> > xdoc:jelly-init:> > xdoc:register-reports:> maven-javadoc-plugin:register:> > > xdoc:jelly-transform:> About to use JSL stylesheet xdocs/site.jsl> [echo] en> [echo] The current Locale is the default one> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated- > xdocs'...> [echo] Generating /Users/clr/apache/jdo/site/target/docs/ > dependencies.html from /Users/clr/apache/jdo/site/target/generated- > xdocs/dependencies.xml> -------------------------------------------------------------------------------> >> Unable to obtain goal [site]> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl > (No such file or directory)> -------------------------------------------------------------------------------> BUILD FAILED> -------------------------------------------------------------------------------> Total time : 20 seconds> Finished at : Friday, March 28, 2008 11:47:38 AM PDT> Final Memory : 8M/15M> > Craig Russell> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo> 408 276-5638 mailto:Craig.Russell@sun.com> P.S. A good JDO? O, Gasp!>
_________________________________________________________________
Watch “Cause Effect,” a show about real people making a real difference. Learn more.
http://im.live.com/Messenger/IM/MTV/?source=text_watchcause
RE: Trouble generating the site
Posted by Martin Gainty <mg...@hotmail.com>.
I saw this answer from a POX engineer who suggested your stylesheet is exhausting memory..export MAVEN_OPTS="-Xmx512m"Anyone?Martin ______________________________________________Disclaimer and confidentiality noteEverything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.> Date: Sat, 29 Mar 2008 14:17:19 -0700> Wrom: AIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGGMEPYOQKEDOTWFAOBUZXUWLSZLKBRNVWWCUFPEGAUTFJMVRESKPNKMBIPBARHDMNNSKVFVWRKJVZCMHVIBGDADRZFSQHYUCDDJBLVLMHAALPTCXLYRWTQTIPWIGYOKSTTZRCLBDXRQBGJSNBOHMKHJYFMYXOEAIJJPHSCRTNHGSWZIDREXCAXZOWCONEUQZAAFXISHJEXXIMQZUIVOTQNQEMSFDULHPQQWOYIYZUNNYCGPKYLEJGDGVCJVTLBXFGcked in to xdocs because that is > > there to> > override the default site generation of Maven1. Without it you get a > > chunky> > site with none of the refinements that were added ;-)> >> > maven-xdoc-plugin is *supposed* to allow overriding the default > > stylesheet via> > the property "maven.xdoc.jsl" (not that they can be bothered to > > document> > it) ... hence why it is in project.properties pointing to ours. It > > currently> > doesn't have ${basedir} prepended and maybe should have (but that > > doesn't> > solve this issue anyway so ignore that).> >> > The maven-xdoc-plugin bundled with Maven1.0.2 accepts that > > overriding. The one> > that comes with Maven1.1 accepts it so far (since it even prints out> > the "site.jsl" it will use ... correctly) but then tries to append > > that name> > on the end of the plugin workspace!!! duh.> >> > If you chase the process through the plugin.jelly of that plugin you > > get to> > <x:parse var="doc" xml="${file}"/>> > <j:file name="${outFile}" encoding="${outputencoding}"> > omitXmlDeclaration="true" outputMode="xml"> > prettyPrint="no">> > <j:include uri="${stylesheet.toString()}"/>> > </j:file>> >> > which has the correct stylesheet name going in (ours). Where that > > then goes to> > I've no idea.> >> > Maybe some Maven team member could comment, and there's some secret > > setting> > that you have to use to get it to work with your own site.jsl file > > in Maven> > 1.1 ?> >> >> >> > -- > > Andy (Java Persistent Objects - http://www.jpox.org)> > [1]> [CraigRussell:~/apache/jdo/site] clr% svn status> [CraigRussell:~/apache/jdo/site] clr% svn up> At revision 642332.> [CraigRussell:~/apache/jdo/site] clr% maven clean > site __ __> | \/ |__ _Apache__ ___> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~> |_| |_\__,_|\_/\___|_||_| v. 1.1> > build:start:> > clean:clean:> xdoc:clean:> > > clean:> > site:> xdoc:register-reports:> maven-javadoc-plugin:register:> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src> > > site:run-reports:> > xdoc:init-i18n:> [echo] Init the i18n support> > xdoc:init:> [echo] Generates the directory structure required for xdocs> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated- > xdocs> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs> > xdoc:i18n-validation:> [echo] Validation of the locale entries> > xdoc:register-reports:> maven-javadoc-plugin:register:> > > xdoc:generate-from-pom:> [echo] Generating xdocs from POM ...> > > > > > xdoc:transform:> xdoc:init-i18n:> > xdoc:init:> [echo] Generates the directory structure required for xdocs> > xdoc:copy-resources:> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/ > style> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/ > images> > xdoc:init-i18n:> > xdoc:init:> [echo] Generates the directory structure required for xdocs> Copying user supplied resources.> > xdoc:copy-user-resources:> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs> [copy] Copied 3 empty directories to 2 empty directories under / > Users/clr/apache/jdo/site/target/docs> > xdoc:init-i18n:> > xdoc:init:> [echo] Generates the directory structure required for xdocs> > xdoc:jelly-init:> > xdoc:register-reports:> maven-javadoc-plugin:register:> > > xdoc:jelly-transform:> About to use JSL stylesheet xdocs/site.jsl> [echo] en> [echo] The current Locale is the default one> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated- > xdocs'...> [echo] Generating /Users/clr/apache/jdo/site/target/docs/ > dependencies.html from /Users/clr/apache/jdo/site/target/generated- > xdocs/dependencies.xml> -------------------------------------------------------------------------------> >> Unable to obtain goal [site]> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl > (No such file or directory)> -------------------------------------------------------------------------------> BUILD FAILED> -------------------------------------------------------------------------------> Total time : 20 seconds> Finished at : Friday, March 28, 2008 11:47:38 AM PDT> Final Memory : 8M/15M> > Craig Russell> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo> 408 276-5638 mailto:Craig.Russell@sun.com> P.S. A good JDO? O, Gasp!>
_________________________________________________________________
Watch “Cause Effect,” a show about real people making a real difference. Learn more.
http://im.live.com/Messenger/IM/MTV/?source=text_watchcause
Re: Fwd: Trouble generating the site
Posted by Andy Jefferson <an...@jpox.org>.
> The second problem is that you have an xpath syntax error in your custom
> style sheet, line 154 in site.jsl should read:
> <jsl:applyTemplates select="$nav/body/menu[not(@type)] |
> $nav/body/menu[@type='header'] | $nav/body/search"/>
This was inherited from the default site.jsl in the maven-xdoc-1.8.jar that
comes with Maven 1.0.2.
> With that the jdo site builds fine for me.
Does for me too. Thx!
--
Andy (Java Persistent Objects - http://www.jpox.org)
Re: Trouble generating the site
Posted by Craig L Russell <Cr...@Sun.COM>.
I think it would be cleaner if we use no slashes at all in the jsl.
I made the changes and can generate the site on my MacOSX with either
1.0.2 or 1.1. W00t.
I've checked in these changes. If anyone else has any issues please
continue this thread.
Thanks, Lukas, for the help,
Craig
[CraigRussell:~/apache/jdo/site] clr% svn diff
Index: xdocs/site.jsl
===================================================================
--- xdocs/site.jsl (revision 642826)
+++ xdocs/site.jsl (working copy)
@@ -151,7 +151,7 @@
<div id="leftColumn">
<div id="navcolumn">
<x:if select="$nav">
- <jsl:applyTemplates select="$nav/body/menu[not(@type) |
@type='header'] | $nav/body/search"/>
+ <jsl:applyTemplates select="$nav/body/menu[not(@type)]
| $nav/body/menu[@type='header'] | $nav/body/search"/>
</x:if>
<jsl:applyTemplates select="$projectNav/body/menu"/>
<!-- allows user to put menu items after standard
reports -->
Index: project.properties
===================================================================
--- project.properties (revision 642826)
+++ project.properties (working copy)
@@ -3,7 +3,7 @@
#
------------------------------------------------------------------------------
# User Interface
-maven.xdoc.jsl=xdocs/site.jsl
+maven.xdoc.jsl=file:${basedir}/xdocs/site.jsl
maven.xdoc.date=bottom
maven.xdoc.date.format=dd MMMM yyyy
maven.xdoc.version=${pom.currentVersion}
On Mar 30, 2008, at 1:41 PM, Michael Bouschen wrote:
> Hi Lukas,
>
> thanks for the feedback, I was able to successfully sun 'maven site'
> with the changes you proposed.
>
> What concerns me is the issue with the slashes in the url. I'm
> running Windows XP: two slashes did not work, but three slashes
> worked fine:
> maven.xdoc.jsl=file:///${basedir}/xdocs/site.jsl
>
> Interestingly suing no slashes worked, too:
> maven.xdoc.jsl=file:${basedir}/xdocs/site.jsl
>
> So the question is whether we can find an url that works independend
> of the operating system.
>
> Regards Michael
>
>
>> [forwarding from the maven user list, I forgot to put jdo-dev in cc]
>>
>> I had a closer look at this (bugged me because I remember working
>> on a fix for custom style sheets before m1.1... ;) )
>>
>> One issue you might experience concerns the number of slashes in
>> the file url prefix. Depending on your OS, especially on different
>> Windows versions, you might need
>>
>> maven.xdoc.jsl=file://${basedir}/xdocs/site.jsl
>>
>> or even three slashes.
>>
>> The second problem is that you have an xpath syntax error in your
>> custom style sheet, line 154 in site.jsl should read:
>>
>>
<jsl:applyTemplates select="$nav/body/menu[not(@type)] | $nav/body/
menu[@type='header'] | $nav/body/search"/>
>>
>> With that the jdo site builds fine for me.
>>
>> HTH,
>> -Lukas
>>
>>
>> Craig L Russell wrote:
>>> Hi,
>>>
>>> We are using maven to generate the Apache JDO site (http://svn.apache.org/viewvc/db/jdo/site/
>>> ).
>>>
>>> We upgraded from Maven 1.0.2 to Maven 1.1 and the site no longer
>>> generates.
>>>
>>> The full console output is below [1].
>>>
>>> The error message is
>>> >> Unable to obtain goal [site]
>>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/
>>> site.jsl (No such file or directory)
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Begin forwarded message:
>>>
>>>> From: Andy Jefferson <an...@jpox.org>
>>>> Date: March 29, 2008 12:42:14 AM PDT
>>>> To: jdo-dev@db.apache.org
>>>> Subject: Re: Trouble generating the site
>>>> Reply-To: jdo-dev@db.apache.org
>>>>
>>>> Hi,
>>>>
>>>> I use Maven 1.0.2 (what I've used for the last 4 yrs ... since
>>>> it works and I
>>>> don't trust the (lack of) backwards compatibility concerns of
>>>> the Maven
>>>> project
>>>>
>>>>> I see the same error as Craig if I run 'maven site' in jdo/site.
>>>>> I also
>>>>> have a site.jsl in my
>>>>> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But
>>>>> there is a
>>>>> (different) site.jsl checked in into jdo/site/xdocs. In addition
>>>>> the
>>>>> file project.properties in jdo/site defines a property
>>>>> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property
>>>>> 'maven site'
>>>>> succeds.
>>>>
>>>>
>>>> There is a different "site.jsl" checked in to xdocs because that
>>>> is there to
>>>> override the default site generation of Maven1. Without it you
>>>> get a chunky
>>>> site with none of the refinements that were added ;-)
>>>>
>>>> maven-xdoc-plugin is *supposed* to allow overriding the default
>>>> stylesheet via
>>>> the property "maven.xdoc.jsl" (not that they can be bothered to
>>>> document
>>>> it) ... hence why it is in project.properties pointing to ours.
>>>> It currently
>>>> doesn't have ${basedir} prepended and maybe should have (but
>>>> that doesn't
>>>> solve this issue anyway so ignore that).
>>>>
>>>> The maven-xdoc-plugin bundled with Maven1.0.2 accepts that
>>>> overriding. The one
>>>> that comes with Maven1.1 accepts it so far (since it even prints
>>>> out
>>>> the "site.jsl" it will use ... correctly) but then tries to
>>>> append that name
>>>> on the end of the plugin workspace!!! duh.
>>>>
>>>> If you chase the process through the plugin.jelly of that plugin
>>>> you get to
>>>> <x:parse var="doc" xml="${file}"/>
>>>> <j:file name="${outFile}" encoding="${outputencoding}"
>>>> omitXmlDeclaration="true" outputMode="xml"
>>>> prettyPrint="no">
>>>> <j:include uri="${stylesheet.toString()}"/>
>>>> </j:file>
>>>>
>>>> which has the correct stylesheet name going in (ours). Where
>>>> that then goes to
>>>> I've no idea.
>>>>
>>>> Maybe some Maven team member could comment, and there's some
>>>> secret setting
>>>> that you have to use to get it to work with your own site.jsl
>>>> file in Maven
>>>> 1.1 ?
>>>>
>>>>
>>>>
>>>> --
>>>> Andy (Java Persistent Objects - http://www.jpox.org)
>>>
>>>
>>> [1]
>>> [CraigRussell:~/apache/jdo/site] clr% svn status
>>> [CraigRussell:~/apache/jdo/site] clr% svn up
>>> At revision 642332.
>>> [CraigRussell:~/apache/jdo/site] clr% maven clean
>>> site __ __
>>> | \/ |__ _Apache__ ___
>>> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>>> |_| |_\__,_|\_/\___|_||_| v. 1.1
>>>
>>> build:start:
>>>
>>> clean:clean:
>>> xdoc:clean:
>>>
>>>
>>> clean:
>>>
>>> site:
>>> xdoc:register-reports:
>>> maven-javadoc-plugin:register:
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src
>>>
>>>
>>> site:run-reports:
>>>
>>> xdoc:init-i18n:
>>> [echo] Init the i18n support
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/
>>> generated- xdocs
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs
>>>
>>> xdoc:i18n-validation:
>>> [echo] Validation of the locale entries
>>>
>>> xdoc:register-reports:
>>> maven-javadoc-plugin:register:
>>>
>>>
>>> xdoc:generate-from-pom:
>>> [echo] Generating xdocs from POM ...
>>>
>>>
>>>
>>>
>>>
>>> xdoc:transform:
>>> xdoc:init-i18n:
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>>
>>> xdoc:copy-resources:
>>> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/
>>> docs/ style
>>> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/
>>> docs/ images
>>>
>>> xdoc:init-i18n:
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>> Copying user supplied resources.
>>>
>>> xdoc:copy-user-resources:
>>> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs
>>> [copy] Copied 3 empty directories to 2 empty directories under /
>>> Users/clr/apache/jdo/site/target/docs
>>>
>>> xdoc:init-i18n:
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>>
>>> xdoc:jelly-init:
>>>
>>> xdoc:register-reports:
>>> maven-javadoc-plugin:register:
>>>
>>>
>>> xdoc:jelly-transform:
>>> About to use JSL stylesheet xdocs/site.jsl
>>> [echo] en
>>> [echo] The current Locale is the default one
>>> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated-
>>> xdocs'...
>>> [echo] Generating /Users/clr/apache/jdo/site/target/docs/
>>> dependencies.html from /Users/clr/apache/jdo/site/target/
>>> generated- xdocs/dependencies.xml
>>> -------------------------------------------------------------------------------
>>> >> Unable to obtain goal [site]
>>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/
>>> site.jsl (No such file or directory)
>>> -------------------------------------------------------------------------------
>>> BUILD FAILED
>>> -------------------------------------------------------------------------------
>>> Total time : 20 seconds
>>> Finished at : Friday, March 28, 2008 11:47:38 AM PDT
>>> Final Memory : 8M/15M
>>>
>>> Craig Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>
>
> --
> Michael Bouschen
> akquinet tech@spree GmbH
> Tempelhofer Ufer 23-24, 10963 Berlin
> Bülowstraße 66, 10783 Berlin
> Tel.: +49/(0)30/235 520-33 Fax.: +49/(0)30/217 520-12
>
> Geschäftsführung: Martin Weber, Hendrik Saly, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
>
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
Re: Fwd: Trouble generating the site
Posted by Lukas Theussl <lt...@apache.org>.
Here's an explanation and workaround that has been implemented in
mevenide: http://jira.codehaus.org/browse/MEVENIDE-174
It seems to say that it's a general windows problem, but I don't know
any details as I have never used this OS :)
However, my recommendation would be to re-evaluate your need of a custom
stylesheet. If it has been copied from xdoc-plugin-1.8 then it's pretty
old and a lot has changed until 1.10.1. I have built your site with the
default jsl and it looks fine to me, but then I don't know what custom
functionality you have implemented so I'm certainly missing a point.
Cheers,
-Lukas
Michael Bouschen wrote:
> Hi Lukas,
>
> thanks for the feedback, I was able to successfully sun 'maven site'
> with the changes you proposed.
>
> What concerns me is the issue with the slashes in the url. I'm running
> Windows XP: two slashes did not work, but three slashes worked fine:
> maven.xdoc.jsl=file:///${basedir}/xdocs/site.jsl
>
> Interestingly suing no slashes worked, too:
> maven.xdoc.jsl=file:${basedir}/xdocs/site.jsl
>
> So the question is whether we can find an url that works independend of
> the operating system.
>
> Regards Michael
>
>
>> [forwarding from the maven user list, I forgot to put jdo-dev in cc]
>>
>> I had a closer look at this (bugged me because I remember working on a
>> fix for custom style sheets before m1.1... ;) )
>>
>> One issue you might experience concerns the number of slashes in the
>> file url prefix. Depending on your OS, especially on different Windows
>> versions, you might need
>>
>> maven.xdoc.jsl=file://${basedir}/xdocs/site.jsl
>>
>> or even three slashes.
>>
>> The second problem is that you have an xpath syntax error in your
>> custom style sheet, line 154 in site.jsl should read:
>>
>> <jsl:applyTemplates select="$nav/body/menu[not(@type)] |
>> $nav/body/menu[@type='header'] | $nav/body/search"/>
>>
>> With that the jdo site builds fine for me.
>>
>> HTH,
>> -Lukas
>>
>>
>> Craig L Russell wrote:
>>
>>> Hi,
>>>
>>> We are using maven to generate the Apache JDO site
>>> (http://svn.apache.org/viewvc/db/jdo/site/ ).
>>>
>>> We upgraded from Maven 1.0.2 to Maven 1.1 and the site no longer
>>> generates.
>>>
>>> The full console output is below [1].
>>>
>>> The error message is
>>> >> Unable to obtain goal [site]
>>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
>>> (No such file or directory)
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> Begin forwarded message:
>>>
>>>> From: Andy Jefferson <an...@jpox.org>
>>>> Date: March 29, 2008 12:42:14 AM PDT
>>>> To: jdo-dev@db.apache.org
>>>> Subject: Re: Trouble generating the site
>>>> Reply-To: jdo-dev@db.apache.org
>>>>
>>>> Hi,
>>>>
>>>> I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it
>>>> works and I
>>>> don't trust the (lack of) backwards compatibility concerns of the
>>>> Maven
>>>> project
>>>>
>>>>> I see the same error as Craig if I run 'maven site' in jdo/site. I
>>>>> also
>>>>> have a site.jsl in my
>>>>> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But there
>>>>> is a
>>>>> (different) site.jsl checked in into jdo/site/xdocs. In addition the
>>>>> file project.properties in jdo/site defines a property
>>>>> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property 'maven
>>>>> site'
>>>>> succeds.
>>>>
>>>>
>>>>
>>>> There is a different "site.jsl" checked in to xdocs because that is
>>>> there to
>>>> override the default site generation of Maven1. Without it you get
>>>> a chunky
>>>> site with none of the refinements that were added ;-)
>>>>
>>>> maven-xdoc-plugin is *supposed* to allow overriding the default
>>>> stylesheet via
>>>> the property "maven.xdoc.jsl" (not that they can be bothered to
>>>> document
>>>> it) ... hence why it is in project.properties pointing to ours. It
>>>> currently
>>>> doesn't have ${basedir} prepended and maybe should have (but that
>>>> doesn't
>>>> solve this issue anyway so ignore that).
>>>>
>>>> The maven-xdoc-plugin bundled with Maven1.0.2 accepts that
>>>> overriding. The one
>>>> that comes with Maven1.1 accepts it so far (since it even prints out
>>>> the "site.jsl" it will use ... correctly) but then tries to append
>>>> that name
>>>> on the end of the plugin workspace!!! duh.
>>>>
>>>> If you chase the process through the plugin.jelly of that plugin
>>>> you get to
>>>> <x:parse var="doc" xml="${file}"/>
>>>> <j:file name="${outFile}" encoding="${outputencoding}"
>>>> omitXmlDeclaration="true" outputMode="xml"
>>>> prettyPrint="no">
>>>> <j:include uri="${stylesheet.toString()}"/>
>>>> </j:file>
>>>>
>>>> which has the correct stylesheet name going in (ours). Where that
>>>> then goes to
>>>> I've no idea.
>>>>
>>>> Maybe some Maven team member could comment, and there's some secret
>>>> setting
>>>> that you have to use to get it to work with your own site.jsl file
>>>> in Maven
>>>> 1.1 ?
>>>>
>>>>
>>>>
>>>> --
>>>> Andy (Java Persistent Objects - http://www.jpox.org)
>>>
>>>
>>>
>>> [1]
>>> [CraigRussell:~/apache/jdo/site] clr% svn status
>>> [CraigRussell:~/apache/jdo/site] clr% svn up
>>> At revision 642332.
>>> [CraigRussell:~/apache/jdo/site] clr% maven clean
>>> site __ __
>>> | \/ |__ _Apache__ ___
>>> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>>> |_| |_\__,_|\_/\___|_||_| v. 1.1
>>>
>>> build:start:
>>>
>>> clean:clean:
>>> xdoc:clean:
>>>
>>>
>>> clean:
>>>
>>> site:
>>> xdoc:register-reports:
>>> maven-javadoc-plugin:register:
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src
>>>
>>>
>>> site:run-reports:
>>>
>>> xdoc:init-i18n:
>>> [echo] Init the i18n support
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated-
>>> xdocs
>>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs
>>>
>>> xdoc:i18n-validation:
>>> [echo] Validation of the locale entries
>>>
>>> xdoc:register-reports:
>>> maven-javadoc-plugin:register:
>>>
>>>
>>> xdoc:generate-from-pom:
>>> [echo] Generating xdocs from POM ...
>>>
>>>
>>>
>>>
>>>
>>> xdoc:transform:
>>> xdoc:init-i18n:
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>>
>>> xdoc:copy-resources:
>>> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/
>>> style
>>> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/
>>> images
>>>
>>> xdoc:init-i18n:
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>> Copying user supplied resources.
>>>
>>> xdoc:copy-user-resources:
>>> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs
>>> [copy] Copied 3 empty directories to 2 empty directories under /
>>> Users/clr/apache/jdo/site/target/docs
>>>
>>> xdoc:init-i18n:
>>>
>>> xdoc:init:
>>> [echo] Generates the directory structure required for xdocs
>>>
>>> xdoc:jelly-init:
>>>
>>> xdoc:register-reports:
>>> maven-javadoc-plugin:register:
>>>
>>>
>>> xdoc:jelly-transform:
>>> About to use JSL stylesheet xdocs/site.jsl
>>> [echo] en
>>> [echo] The current Locale is the default one
>>> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated-
>>> xdocs'...
>>> [echo] Generating /Users/clr/apache/jdo/site/target/docs/
>>> dependencies.html from /Users/clr/apache/jdo/site/target/generated-
>>> xdocs/dependencies.xml
>>> -------------------------------------------------------------------------------
>>>
>>> >> Unable to obtain goal [site]
>>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
>>> (No such file or directory)
>>> -------------------------------------------------------------------------------
>>>
>>> BUILD FAILED
>>> -------------------------------------------------------------------------------
>>>
>>> Total time : 20 seconds
>>> Finished at : Friday, March 28, 2008 11:47:38 AM PDT
>>> Final Memory : 8M/15M
>>>
>>> Craig Russell
>>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>> P.S. A good JDO? O, Gasp!
>>>
>
>
Re: Fwd: Trouble generating the site
Posted by Michael Bouschen <mb...@spree.de>.
Hi Lukas,
thanks for the feedback, I was able to successfully sun 'maven site'
with the changes you proposed.
What concerns me is the issue with the slashes in the url. I'm running
Windows XP: two slashes did not work, but three slashes worked fine:
maven.xdoc.jsl=file:///${basedir}/xdocs/site.jsl
Interestingly suing no slashes worked, too:
maven.xdoc.jsl=file:${basedir}/xdocs/site.jsl
So the question is whether we can find an url that works independend of
the operating system.
Regards Michael
> [forwarding from the maven user list, I forgot to put jdo-dev in cc]
>
> I had a closer look at this (bugged me because I remember working on a
> fix for custom style sheets before m1.1... ;) )
>
> One issue you might experience concerns the number of slashes in the
> file url prefix. Depending on your OS, especially on different Windows
> versions, you might need
>
> maven.xdoc.jsl=file://${basedir}/xdocs/site.jsl
>
> or even three slashes.
>
> The second problem is that you have an xpath syntax error in your
> custom style sheet, line 154 in site.jsl should read:
>
> <jsl:applyTemplates select="$nav/body/menu[not(@type)] |
> $nav/body/menu[@type='header'] | $nav/body/search"/>
>
> With that the jdo site builds fine for me.
>
> HTH,
> -Lukas
>
>
> Craig L Russell wrote:
>> Hi,
>>
>> We are using maven to generate the Apache JDO site
>> (http://svn.apache.org/viewvc/db/jdo/site/ ).
>>
>> We upgraded from Maven 1.0.2 to Maven 1.1 and the site no longer
>> generates.
>>
>> The full console output is below [1].
>>
>> The error message is
>> >> Unable to obtain goal [site]
>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
>> (No such file or directory)
>>
>> Any ideas?
>>
>> Thanks,
>>
>> Craig
>>
>> Begin forwarded message:
>>
>>> From: Andy Jefferson <an...@jpox.org>
>>> Date: March 29, 2008 12:42:14 AM PDT
>>> To: jdo-dev@db.apache.org
>>> Subject: Re: Trouble generating the site
>>> Reply-To: jdo-dev@db.apache.org
>>>
>>> Hi,
>>>
>>> I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it
>>> works and I
>>> don't trust the (lack of) backwards compatibility concerns of the
>>> Maven
>>> project
>>>
>>>> I see the same error as Craig if I run 'maven site' in jdo/site. I
>>>> also
>>>> have a site.jsl in my
>>>> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But there
>>>> is a
>>>> (different) site.jsl checked in into jdo/site/xdocs. In addition the
>>>> file project.properties in jdo/site defines a property
>>>> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property 'maven
>>>> site'
>>>> succeds.
>>>
>>>
>>> There is a different "site.jsl" checked in to xdocs because that is
>>> there to
>>> override the default site generation of Maven1. Without it you get
>>> a chunky
>>> site with none of the refinements that were added ;-)
>>>
>>> maven-xdoc-plugin is *supposed* to allow overriding the default
>>> stylesheet via
>>> the property "maven.xdoc.jsl" (not that they can be bothered to
>>> document
>>> it) ... hence why it is in project.properties pointing to ours. It
>>> currently
>>> doesn't have ${basedir} prepended and maybe should have (but that
>>> doesn't
>>> solve this issue anyway so ignore that).
>>>
>>> The maven-xdoc-plugin bundled with Maven1.0.2 accepts that
>>> overriding. The one
>>> that comes with Maven1.1 accepts it so far (since it even prints out
>>> the "site.jsl" it will use ... correctly) but then tries to append
>>> that name
>>> on the end of the plugin workspace!!! duh.
>>>
>>> If you chase the process through the plugin.jelly of that plugin
>>> you get to
>>> <x:parse var="doc" xml="${file}"/>
>>> <j:file name="${outFile}" encoding="${outputencoding}"
>>> omitXmlDeclaration="true" outputMode="xml"
>>> prettyPrint="no">
>>> <j:include uri="${stylesheet.toString()}"/>
>>> </j:file>
>>>
>>> which has the correct stylesheet name going in (ours). Where that
>>> then goes to
>>> I've no idea.
>>>
>>> Maybe some Maven team member could comment, and there's some secret
>>> setting
>>> that you have to use to get it to work with your own site.jsl file
>>> in Maven
>>> 1.1 ?
>>>
>>>
>>>
>>> --
>>> Andy (Java Persistent Objects - http://www.jpox.org)
>>
>>
>> [1]
>> [CraigRussell:~/apache/jdo/site] clr% svn status
>> [CraigRussell:~/apache/jdo/site] clr% svn up
>> At revision 642332.
>> [CraigRussell:~/apache/jdo/site] clr% maven clean
>> site __ __
>> | \/ |__ _Apache__ ___
>> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>> |_| |_\__,_|\_/\___|_||_| v. 1.1
>>
>> build:start:
>>
>> clean:clean:
>> xdoc:clean:
>>
>>
>> clean:
>>
>> site:
>> xdoc:register-reports:
>> maven-javadoc-plugin:register:
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src
>>
>>
>> site:run-reports:
>>
>> xdoc:init-i18n:
>> [echo] Init the i18n support
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated-
>> xdocs
>> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs
>>
>> xdoc:i18n-validation:
>> [echo] Validation of the locale entries
>>
>> xdoc:register-reports:
>> maven-javadoc-plugin:register:
>>
>>
>> xdoc:generate-from-pom:
>> [echo] Generating xdocs from POM ...
>>
>>
>>
>>
>>
>> xdoc:transform:
>> xdoc:init-i18n:
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>>
>> xdoc:copy-resources:
>> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/
>> style
>> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/
>> images
>>
>> xdoc:init-i18n:
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>> Copying user supplied resources.
>>
>> xdoc:copy-user-resources:
>> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs
>> [copy] Copied 3 empty directories to 2 empty directories under /
>> Users/clr/apache/jdo/site/target/docs
>>
>> xdoc:init-i18n:
>>
>> xdoc:init:
>> [echo] Generates the directory structure required for xdocs
>>
>> xdoc:jelly-init:
>>
>> xdoc:register-reports:
>> maven-javadoc-plugin:register:
>>
>>
>> xdoc:jelly-transform:
>> About to use JSL stylesheet xdocs/site.jsl
>> [echo] en
>> [echo] The current Locale is the default one
>> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated-
>> xdocs'...
>> [echo] Generating /Users/clr/apache/jdo/site/target/docs/
>> dependencies.html from /Users/clr/apache/jdo/site/target/generated-
>> xdocs/dependencies.xml
>> -------------------------------------------------------------------------------
>>
>> >> Unable to obtain goal [site]
>> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl
>> (No such file or directory)
>> -------------------------------------------------------------------------------
>>
>> BUILD FAILED
>> -------------------------------------------------------------------------------
>>
>> Total time : 20 seconds
>> Finished at : Friday, March 28, 2008 11:47:38 AM PDT
>> Final Memory : 8M/15M
>>
>> Craig Russell
>> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!
>>
--
Michael Bouschen
akquinet tech@spree GmbH
Tempelhofer Ufer 23-24, 10963 Berlin
Bülowstraße 66, 10783 Berlin
Tel.: +49/(0)30/235 520-33 Fax.: +49/(0)30/217 520-12
Geschäftsführung: Martin Weber, Hendrik Saly, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680
Re: Fwd: Trouble generating the site
Posted by Lukas Theussl <lt...@apache.org>.
[forwarding from the maven user list, I forgot to put jdo-dev in cc]
I had a closer look at this (bugged me because I remember working on a
fix for custom style sheets before m1.1... ;) )
One issue you might experience concerns the number of slashes in the
file url prefix. Depending on your OS, especially on different Windows
versions, you might need
maven.xdoc.jsl=file://${basedir}/xdocs/site.jsl
or even three slashes.
The second problem is that you have an xpath syntax error in your custom
style sheet, line 154 in site.jsl should read:
<jsl:applyTemplates select="$nav/body/menu[not(@type)] |
$nav/body/menu[@type='header'] | $nav/body/search"/>
With that the jdo site builds fine for me.
HTH,
-Lukas
Craig L Russell wrote:
> Hi,
>
> We are using maven to generate the Apache JDO site
> (http://svn.apache.org/viewvc/db/jdo/site/ ).
>
> We upgraded from Maven 1.0.2 to Maven 1.1 and the site no longer
> generates.
>
> The full console output is below [1].
>
> The error message is
> >> Unable to obtain goal [site]
> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl (No
> such file or directory)
>
> Any ideas?
>
> Thanks,
>
> Craig
>
> Begin forwarded message:
>
>> From: Andy Jefferson <an...@jpox.org>
>> Date: March 29, 2008 12:42:14 AM PDT
>> To: jdo-dev@db.apache.org
>> Subject: Re: Trouble generating the site
>> Reply-To: jdo-dev@db.apache.org
>>
>> Hi,
>>
>> I use Maven 1.0.2 (what I've used for the last 4 yrs ... since it
>> works and I
>> don't trust the (lack of) backwards compatibility concerns of the Maven
>> project
>>
>>> I see the same error as Craig if I run 'maven site' in jdo/site. I also
>>> have a site.jsl in my
>>> .maven/cache/maven-xdoc-plugin-1.10.1/plugin-resources. But there is a
>>> (different) site.jsl checked in into jdo/site/xdocs. In addition the
>>> file project.properties in jdo/site defines a property
>>> 'maven.xdoc.jsl=xdocs/site.jsl'. If I delete this property 'maven site'
>>> succeds.
>>
>>
>> There is a different "site.jsl" checked in to xdocs because that is
>> there to
>> override the default site generation of Maven1. Without it you get a
>> chunky
>> site with none of the refinements that were added ;-)
>>
>> maven-xdoc-plugin is *supposed* to allow overriding the default
>> stylesheet via
>> the property "maven.xdoc.jsl" (not that they can be bothered to document
>> it) ... hence why it is in project.properties pointing to ours. It
>> currently
>> doesn't have ${basedir} prepended and maybe should have (but that
>> doesn't
>> solve this issue anyway so ignore that).
>>
>> The maven-xdoc-plugin bundled with Maven1.0.2 accepts that
>> overriding. The one
>> that comes with Maven1.1 accepts it so far (since it even prints out
>> the "site.jsl" it will use ... correctly) but then tries to append
>> that name
>> on the end of the plugin workspace!!! duh.
>>
>> If you chase the process through the plugin.jelly of that plugin you
>> get to
>> <x:parse var="doc" xml="${file}"/>
>> <j:file name="${outFile}" encoding="${outputencoding}"
>> omitXmlDeclaration="true" outputMode="xml"
>> prettyPrint="no">
>> <j:include uri="${stylesheet.toString()}"/>
>> </j:file>
>>
>> which has the correct stylesheet name going in (ours). Where that
>> then goes to
>> I've no idea.
>>
>> Maybe some Maven team member could comment, and there's some secret
>> setting
>> that you have to use to get it to work with your own site.jsl file in
>> Maven
>> 1.1 ?
>>
>>
>>
>> --
>> Andy (Java Persistent Objects - http://www.jpox.org)
>
>
> [1]
> [CraigRussell:~/apache/jdo/site] clr% svn status
> [CraigRussell:~/apache/jdo/site] clr% svn up
> At revision 642332.
> [CraigRussell:~/apache/jdo/site] clr% maven clean
> site __ __
> | \/ |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.1
>
> build:start:
>
> clean:clean:
> xdoc:clean:
>
>
> clean:
>
> site:
> xdoc:register-reports:
> maven-javadoc-plugin:register:
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/javadoc/src
>
>
> site:run-reports:
>
> xdoc:init-i18n:
> [echo] Init the i18n support
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/generated- xdocs
> [mkdir] Created dir: /Users/clr/apache/jdo/site/target/docs
>
> xdoc:i18n-validation:
> [echo] Validation of the locale entries
>
> xdoc:register-reports:
> maven-javadoc-plugin:register:
>
>
> xdoc:generate-from-pom:
> [echo] Generating xdocs from POM ...
>
>
>
>
>
> xdoc:transform:
> xdoc:init-i18n:
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
>
> xdoc:copy-resources:
> [copy] Copying 5 files to /Users/clr/apache/jdo/site/target/docs/ style
> [copy] Copying 16 files to /Users/clr/apache/jdo/site/target/docs/
> images
>
> xdoc:init-i18n:
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
> Copying user supplied resources.
>
> xdoc:copy-user-resources:
> [copy] Copying 17 files to /Users/clr/apache/jdo/site/target/docs
> [copy] Copied 3 empty directories to 2 empty directories under /
> Users/clr/apache/jdo/site/target/docs
>
> xdoc:init-i18n:
>
> xdoc:init:
> [echo] Generates the directory structure required for xdocs
>
> xdoc:jelly-init:
>
> xdoc:register-reports:
> maven-javadoc-plugin:register:
>
>
> xdoc:jelly-transform:
> About to use JSL stylesheet xdocs/site.jsl
> [echo] en
> [echo] The current Locale is the default one
> [echo] Scanning '/Users/clr/apache/jdo/site/target/generated- xdocs'...
> [echo] Generating /Users/clr/apache/jdo/site/target/docs/
> dependencies.html from /Users/clr/apache/jdo/site/target/generated-
> xdocs/dependencies.xml
> -------------------------------------------------------------------------------
>
> >> Unable to obtain goal [site]
> >> /Users/clr/.maven/cache/maven-xdoc-plugin-1.10.1/xdocs/site.jsl (No
> such file or directory)
> -------------------------------------------------------------------------------
>
> BUILD FAILED
> -------------------------------------------------------------------------------
>
> Total time : 20 seconds
> Finished at : Friday, March 28, 2008 11:47:38 AM PDT
> Final Memory : 8M/15M
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>