Github user hboutemy commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-76888558
Reporting is a key feature of Maven I strongly want to keep working (or fix
when we introduced problems while improving build consistency during Maven 3.x
refactoring)
I like the option idea to fix (or workaround) the described use case, but I
understand Jason resistance to adding it since it causes inconsistency. I still
don't have strong final opinion if this is the way to go or not, either only as
a temporary workaround or as a real permanent feature.
What I know is that, while working on maven-reporting-exec, ie the
component that launches report mojos during site generation, in MSHARED-266 for
version 1.2, I found that there were more than this resolution issue that makes
reporting mojo execution a special case: build forking and aggregate are other
special cases that cause issues, IMHO
And every change I could imagine to avoid build forking worked with most
report plugins, but not with cobertura-maven-plugin: "producing artifacts or
consuming artifacts" is a key factor, ie most reports are "consuming artifacts"
but a few are "producing artifacts".
I imagine this idea about "disabling workspace resolution" will affect
cobertura-maven-plugin: since this report is producing artifacts, it will
require workspace resolution, isn't it?
Christian, did you try with a build that uses cobertura-maven-plugin?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
