Even though Hervé has given the best answer, I thought I'd chime in
and say that The Maven Way would probably have you add the additional
dependency at the plugin level, and not the
configuration.reportPlugins.plugin level.. So, sorry, but you were
wrong twice. :-)
On Thu, Feb 13, 2014 at 10:34
Not sure I follow. Are you saying that if I need to add a dependency to a
project.build.plugins.plugin.configuration.reportPlugins.plugin I should do
it at project.build.plugins.plugin instead? E.g. as an additional
dependency of the maven-site-plugin itself? If so, I tried that and was
On Fri, Feb 14, 2014 at 7:55 AM, Alex Potsides a...@achingbrain.net wrote:
E.g. as an additional
dependency of the maven-site-plugin itself?
Yes.
If so, I tried that [...] The maven-site-plugin does not appear to
share it's classpath with child reportPlugins and quite rightly so.
Boo.
I'm sorry if this question has been asked already but I couldn't find much
in the archives.
I'm trying to convert some existing build plugins to instead be report
plugins with v3.3 of maven-site-plugin. One of the plugins needs an extra
dependency to be specified. When it lived as a direct
I'll make it short: please don't use reportPlugins in m-site-p configuration
see
http://maven.apache.org/plugins/maven-site-plugin/maven-3.html#Configuration_formats
use classic configuration and everything will work fine
Regards,
Hervé
Le jeudi 13 février 2014 15:34:03 Alex Potsides a écrit
Brevity appreciated. You sound like someone who has answered that question
before.
Thanks,
Alex
On Thu, Feb 13, 2014 at 5:50 PM, Hervé BOUTEMY herve.bout...@free.frwrote:
I'll make it short: please don't use reportPlugins in m-site-p
configuration
see
yes :)
it has taken a few maven-site-plugin releases to really understand we had make
a mistake switching to something that was finally not ready, and document it to
have a chance people understand the rationale
Regards,
Hervé
Le jeudi 13 février 2014 21:28:11 Alex Potsides a écrit :
