Aggregate use case - parent pom of type pom

23 views
Skip to first unread message

Tim Pizey

unread,
Jun 1, 2016, 6:46:44 PM6/1/16
to jac...@googlegroups.com
Hi,

Hoping that this is the right place to discuss this, rather than the
issue tracker.

At work we have a use case for the aggregate report which I do not
think is currently considered.

We use a parent pom of type pom which defines common plugins and
external dependencies and lists a number of war and jar projects as
modules not dependencies.

It would be nice to have all the modules reported upon, ideally also
with a total for the whole project.

At the moment I do not think that the proposed aggregate report,
currently in SNAPSHOT, can be made to do this, without declaring the
modules as dependencies.

Is the answer to also define the child projects as dependencies?

I would be happy to define an integration test if this requirement makes sense.

best regards
Tim


--
Tim Pizey - http://tim.pizey.uk/

Marc R. Hoffmann

unread,
Jun 2, 2016, 12:36:41 AM6/2/16
to jac...@googlegroups.com
Hi,

we had a long discussion about this when designing the the new goal:
Basically Maven does not support to do this in a single run. A parent
POM is not the proper place to create the report as it is executed
*before* its child modules. See this for details:

https://github.com/jacoco/jacoco/wiki/MavenMultiModule

Regards,
-marc
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages