[mojo-dev] [jira] (MCOBERTURA-193) Cobertura doesn't aggregate results if last submodule type is 'pom'

[JIRA]

Title: Message Title

Jakub Boche?ski created an issue   Mojo's Cobertura Maven Plugin / MCOBERTURA-193 Cobertura doesn't aggregate results if last submodule type is 'pom' Issue Type: Bug Affects Versions: 2.6 Assignee: Unassigned Created: 29/Dec/14 10:10 AM Environment: Maven 3.0.4 Priority: Blocker Reporter: Jakub Boche?ski I have an aggregate project layout e.g. main (type: pom) java (type: pom) common (type: jar) war1 (type: war) war2 (type: war) dev-server (type: pom; only included with 'p1' profile on) misc (type: pom) The dev-server module just contains an assembly of binaries from modules war1 and war2. When I execute clean cobertura:cobertura deploy the build order is [INFO] Reactor Build Order: [INFO] [INFO] main [INFO] misc [INFO] java [INFO] common [INFO] war1 [INFO] war2 and the aggregation is working e.g. [INFO] Executing aggregate cobertura:report for main When I include the dev-server module with clean cobertura:cobertura deploy -P p1 the build order is [INFO] Reactor Build Order: [INFO] [INFO] main [INFO] misc [INFO] java [INFO] common [INFO] war1 [INFO] war2 [INFO] dev-server and the aggregation is not performed at all. Add Comment   This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email