maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seidel (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MJAVADOC-171) Modules in multi-module projects are "built" too often
Date Mon, 04 Feb 2008 12:28:57 GMT

     [ http://jira.codehaus.org/browse/MJAVADOC-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Seidel updated MJAVADOC-171:
-----------------------------------

    Attachment: 2.2.log

It's not about twice. It's about _all_ modules are built twice for _each_ module. I have removed
the maven-surefire-report-plugin from the parent pom (to show the problem more distinctively)
and when I run clean site the following logs come out with version 2.3 and 2.2 respectively.
Notice the vast increase of
{code}
[INFO] Building Unnamed - org.test.forked:...
[INFO] ------------------------------------------------------
[INFO] [xmlbeans:xmlbeans {execution: default}]
[INFO] Nothing to generate.
{code}
parts from 2.2 to 2.3.

> Modules in multi-module projects are "built" too often
> ------------------------------------------------------
>
>                 Key: MJAVADOC-171
>                 URL: http://jira.codehaus.org/browse/MJAVADOC-171
>             Project: Maven 2.x Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3
>         Environment: Maven 2.0.8, Linux
>            Reporter: Stefan Seidel
>            Priority: Critical
>         Attachments: 2.2.log, 2.3.log, mvnexec.zip
>
>
> In a multi-module project, all modules are "built" twice for each module. This leads
to huge performance problems when many modules are in a project. In the attached sample project,
the xmlbeans plugin is executed 27 times for a project with one parent module and two submodules.
18 of these executions can be attributed to the javadoc plugin. With version 2.2, only 3 invocations
(once for each project) are caused by the javadoc plugin.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message