On 18.12.2007 11:16, david vicente wrote:
Hi,
for that, you must choose a mvn site:deploy with a correct configuration of
:
<distributionManagement>
<site>
<id>website</id>
<url>xxxx</url>
</site>
</distributionManagement>
In <url>xxxx</url> section , you can configure a local path as file://xxxxx
see the maven doc for file protocol
and after, you run a "mvn site:deploy" command to deploy in local directory
Indeed "site:deploy" works fine. Thanks.
Regards
Marcin
2007/12/18, Marcin Zajaczkowski <[EMAIL PROTECTED]>:
On 17.12.2007 15:42, david vicente wrote:
Hi,
you must add this section in your root pom.xml
<distributionManagement>
<site>
<id>website</id>
<url>xxxx</url>
</site>
</distributionManagement>
and after, you can run :
- mvn site
- mvn dahboard-report:dashboard
- mvn site:stage or mvn site:deploy
and all links work fine.
only site:stage or site:deploy goal can aggregate all modules site in
only
one directory structure.
I made changes suggested by you in the root pom.xml for a project and
site:deploy works fine. I was able to enable working links in
site:stage, but only with construction like that:
mvn site:stage -DstagingDirectory=/tmp/mymultiproj-staging
(then for submodule MultiReportMojo report output directory =
/tmp/multiproj-staging/localhost/tmp/mymultiproj/submod2)
Normal site:stage does (for submodule):
MultiReportMojo report output directory =
${path_to_working_copy}/mymultiproj/trunk/submod2/target/staging/tmp/mymultiproj/submod2
(instead of expected
${path_to_working_copy}/mymultiproj/trunk/target/staging/tmp/mymultiproj/submod2)
and links don't work.
Is it possible to define stagingDirectory (especially as a relative
path) in my root pom.xml which would be used by all submodules?
Thanks for your reply
Marcin
with mvn site only, each module has the site in \target\site but links
don't
work.
Best regards
David
(...)
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
