Good reporting plugins should be written such that, if they are run on
inappropriate project types (i.e. project packaging) - for instance a
javadoc report on a POM package project, they do nothing. Some of the
standard maven reports are a little annoying at the mo', for instance the
PMD report will
generate an empty PMD report for a POM project type, with a link in the
Project Reports menu etc. Anyways, your technique of defining reports in a
master POM project and then having those reports inherited by your
submodules is perfectly valid, indeed we do this a lot.
For instance, as all our projects have some kind of SCM and 'task'
semantics, our master poms include the maven-changes-plugin and the
maven-changelog-plugin and this means all the child modules get these
reports too.
Note you can configure these reports differently in each child module,
without having to respecifying the report and it's configuration using the
standard <reporting><plugins><plugin><configuration> stuff in each module
but instead use ${properties} which are 'overwritten' by the child modules
and used in the model interpolation and thus the report 'instances' run for
each module.
John
Aaron Zeckoski wrote:
>
> Just bumping my own message in the hopes I might get an answer. We
> really need this for a large open source project so any suggestions
> are greatly appreciated.
>
> Should I be sending this to a different list?
>
> Thanks
> :-)
> -AZ
>
>
> On 7/20/07, Aaron Zeckoski <[EMAIL PROTECTED]> wrote:
>> I have a configuration issue with maven 2.0.7 that I am not sure how
>> to get around and I have not been able to find my answers in the maven
>> 2 docs here:
>> http://maven.apache.org/pom.html
>>
>> I want to define a set of reports in a "base" pom file. Then I want to
>> run the reports on the entire set of modules for that POM at once. As
>> an alternative, we just want to run the reports on the modules only
>> but do not want to have to put the same reports tag in every module
>> pom.
>>
>> Here is an example of the structure
>> base/pom.xml (no code, refers to 5 modules)
>> api/pom.xml (module)
>> impl/pom.xml (module)
>> tool/pom.xml (module)
>> whatever/pom.xml (module)
>> other stuff/pom.xml (module)
>>
>> Unfortunately, I am having a problem with this approach. The base
>> project (the one with no code in it) tends to cause the reports to
>> fail to run and therefore cause the maven "site" to fail to build. If
>> we are building the site along with the rest of
>> the code (mvn clean install site) then this means that we get an
>> overall build failure. (Again, the idea here being that we put the report
>> generating tags in the base pom file.)
>>
>> Ideally I am hoping there is some way to run a report on the
>> completely build base projects. If not then maybe something like a
>> "no-reports" tag or maybe some way to keep the reports from running
>> for the base project but no stop the tags from being inherited from
>> the base by the related projects.
>>
>> I appreciate any suggestions and help
>> :-)
>> -AZ
>>
>>
>> --
>> Aaron Zeckoski ([EMAIL PROTECTED])
>> Senior Research Engineer - CARET - Cambridge University
>> [http://bugs.sakaiproject.org/confluence/display/~aaronz/]
>> Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
>>
>
>
> --
> Aaron Zeckoski ([EMAIL PROTECTED])
> Senior Research Engineer - CARET - Cambridge University
> [http://bugs.sakaiproject.org/confluence/display/~aaronz/]
> Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in context:
http://www.nabble.com/Maven-2-site-reporting-with-mutliple-projects-tf4115724s177.html#a11733642
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
