Hi,

The way I like to do this is as follows:

PARENT:
Specify a report output directory for the parent.

<reporting>
        <outputDirectory>c:/myreports/myproject/site</outputDirectory>

        <plugins>
                ... Specify all report plugins ..
        </plugins>
</reporting>

CHILD:

Use pom inheritance to get the parent directory then put the child site
generation in a sub directory named after the artifact id.
This is what Maven expects when it generates the parent site (its
children to be in subdirectories named after the artifact id). 

<build>
        <plugins>
                 <plugin>
                        <groupId>org.apache.maven.plugins</groupId>
                        <artifactId>maven-site-plugin</artifactId>
                        <configuration>
        
<outputDirectory>${project.reporting.outputDirectory}/${artifactId}</out
putDirectory>
                        </configuration>
                </plugin>       
          </plugins>
  </build>

Please note that nearly all report plugins (jxr, changelog etc) use the
child outputdirectory specifed in the build section over the parent.
There are however a couple that don't, one that springs to mind is the
Cobatura. If you want this to work you must put this in all your
individual child reporting sections:

<reporting>
        <plugins>       
                <!-- a bug in the cobertura plugin doesnt reference the
site output directory when specified in the build section so we have to
manually specify it again.-->
                <plugin>
                        <groupId>org.codehaus.mojo</groupId>
                        <artifactId>cobertura-maven-plugin</artifactId>
                        <configuration>
        
<outputDirectory>${project.reporting.outputDirectory}/${artifactId}/cobe
rtura</outputDirectory>
                        </configuration>
                </plugin>       
        </plugins>  
</reporting> 

Good luck :)

Rob Langridge 



-----Original Message-----
From: gc134728 [mailto:[EMAIL PROTECTED] 
Sent: 08 January 2007 14:21
To: users
Subject: Site generation on a parent level

Dear Maven Users,

Does anyone know a good way to set up the site generation on a parent
level?
I would like to have all reports of the individual modules changed moved
to the target directory of the parent project so that all information
together will be together and not on a module level.

Any ideas ?

Thx, for you help.---
Scarlet ONE -  Combine ADSL with unlimited fixed phone and save 400
euros http://www.scarlet.be


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This communication together with any attachments transmitted with it ("this 
E-Mail") is intended only for the use of the addressee and may contain 
information which is privileged and confidential.  If the reader of this E-Mail 
is not the intended recipient or the employee or agent responsible for 
delivering it to the intended recipient you are hereby notified that any use, 
dissemination, forwarding, printing or copying of this E-Mail is strictly 
prohibited.  Addressees should check this E-mail for viruses.  The Company 
makes no representations as regards the absence of viruses in this E-Mail.  If 
you have received this E-Mail in error please notify our IT Service Desk 
immediately by e-mail at [EMAIL PROTECTED]  Please then immediately delete, 
erase or otherwise destroy this E-Mail and any copies of it.

Any opinions expressed in this E-Mail are those of the author and do not 
necessarily constitute the views of the Company.  Nothing in this E-Mail shall 
bind the Company in any contract or obligation.

For the purposes of this E-Mail "the Company" means The Carphone Warehouse 
Group Plc and/or any of its subsidiaries.

Please feel free to visit our website:  http:// www.carphonewarehouse.com or 
http://www.phonehouse.com

The Carphone Warehouse Group Plc (Registered in England No. 3253714) 1 Portal 
Way, London W3 6RS


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to