kriegaex commented on PR #26:
URL:
https://github.com/apache/maven-reporting-impl/pull/26#issuecomment-1804970463
> Even if a plugin uses a subdir in the shared one, there are still assets
from the skin which need to be present to properly render the report in the
browser.
Then, I think I am with you concerning the idea to have a dedicated common
base directory for reports, because now you just gave me a good reason for it:
common assets from the skin. I had not thought about that before.
Of course, the current default `${project.reporting.outputDirectory}` serves
this purpose, but as we discussed, calling a stand-alone goal could yield a
different kind of report (per module, not aggregated) than building a site. Now
that we established that `${project.build.directory}` might be inadequate,
something like `${project.build.directory}/reports` might actually be the
better solution.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
