You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Alex Potsides <al...@achingbrain.net> on 2014/02/13 16:34:03 UTC
Maven Site Plugin and report plugins that need dependencies declared
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 child of
build/plugins this was ok, but when I do this sort of thing:
<plugin>
<artifactId>maven-site-plugin</artifactId>
<version>3.3</version>
<configuration>
<reportPlugins>
<plugin>
<groupId>..</groupId>
<artifactId>..</artifactId>
<version>..</version>
<dependencies>
<dependency>
<artifactId>..</artifactId>
<groupId>..</groupId>
...
I get:
Cannot find setter, adder nor field in
org.apache.maven.reporting.exec.ReportPlugin for 'dependencies'
Is this sort of configuration not possible?
Thanks in advance.
Alex Potsides
Re: Maven Site Plugin and report plugins that need dependencies declared
Posted by Hervé BOUTEMY <he...@free.fr>.
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 :
> 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 <he...@free.fr>wrote:
> > 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#Configurati
> > on_formats
> >
> > use classic configuration and everything will work fine
> >
> > Regards,
> >
> > Hervé
> >
> > Le jeudi 13 février 2014 15:34:03 Alex Potsides a écrit :
> > > 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 child of
> > > build/plugins this was ok, but when I do this sort of thing:
> > >
> > > <plugin>
> > >
> > > <artifactId>maven-site-plugin</artifactId>
> > > <version>3.3</version>
> > > <configuration>
> > >
> > > <reportPlugins>
> > >
> > > <plugin>
> > >
> > > <groupId>..</groupId>
> > > <artifactId>..</artifactId>
> > > <version>..</version>
> > > <dependencies>
> > >
> > > <dependency>
> > >
> > > <artifactId>..</artifactId>
> > > <groupId>..</groupId>
> > > ...
> > >
> > > I get:
> > >
> > > Cannot find setter, adder nor field in
> > > org.apache.maven.reporting.exec.ReportPlugin for 'dependencies'
> > >
> > > Is this sort of configuration not possible?
> > >
> > > Thanks in advance.
> > >
> > > Alex Potsides
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Site Plugin and report plugins that need dependencies declared
Posted by Alex Potsides <al...@achingbrain.net>.
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 <he...@free.fr>wrote:
> 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 :
> > 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 child of
> > build/plugins this was ok, but when I do this sort of thing:
> >
> > <plugin>
> > <artifactId>maven-site-plugin</artifactId>
> > <version>3.3</version>
> > <configuration>
> > <reportPlugins>
> > <plugin>
> > <groupId>..</groupId>
> > <artifactId>..</artifactId>
> > <version>..</version>
> > <dependencies>
> > <dependency>
> > <artifactId>..</artifactId>
> > <groupId>..</groupId>
> > ...
> >
> > I get:
> >
> > Cannot find setter, adder nor field in
> > org.apache.maven.reporting.exec.ReportPlugin for 'dependencies'
> >
> > Is this sort of configuration not possible?
> >
> > Thanks in advance.
> >
> > Alex Potsides
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven Site Plugin and report plugins that need dependencies declared
Posted by Hervé BOUTEMY <he...@free.fr>.
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 :
> 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 child of
> build/plugins this was ok, but when I do this sort of thing:
>
> <plugin>
> <artifactId>maven-site-plugin</artifactId>
> <version>3.3</version>
> <configuration>
> <reportPlugins>
> <plugin>
> <groupId>..</groupId>
> <artifactId>..</artifactId>
> <version>..</version>
> <dependencies>
> <dependency>
> <artifactId>..</artifactId>
> <groupId>..</groupId>
> ...
>
> I get:
>
> Cannot find setter, adder nor field in
> org.apache.maven.reporting.exec.ReportPlugin for 'dependencies'
>
> Is this sort of configuration not possible?
>
> Thanks in advance.
>
> Alex Potsides
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Site Plugin and report plugins that need dependencies declared
Posted by jieryn <ji...@gmail.com>.
On Fri, Feb 14, 2014 at 7:55 AM, Alex Potsides <al...@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.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Site Plugin and report plugins that need dependencies declared
Posted by Alex Potsides <al...@achingbrain.net>.
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
unsurprised when it didn't work. The maven-site-plugin does not appear to
share it's classpath with child reportPlugins and quite rightly so.
Following Hervé's advice I'm now using the older project.reporting.plugins
config instead. However due to
http://jira.codehaus.org/browse/MSITE-444(unresolved since 2007)
project.reporting.plugins.plugin can't hold a
dependencies element so the whole thing is a bust.
a.
On Fri, Feb 14, 2014 at 12:19 PM, jieryn <ji...@gmail.com> wrote:
> 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 AM, Alex Potsides <al...@achingbrain.net>
> wrote:
> > <plugin>
> > <artifactId>maven-site-plugin</artifactId>
> > <version>3.3</version>
> > <configuration>
> > <reportPlugins>
> > <plugin>
> > <groupId>..</groupId>
> > <artifactId>..</artifactId>
> > <version>..</version>
> > <dependencies>
> > <dependency>
> > <artifactId>..</artifactId>
> > <groupId>..</groupId>
> > ...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven Site Plugin and report plugins that need dependencies declared
Posted by jieryn <ji...@gmail.com>.
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 AM, Alex Potsides <al...@achingbrain.net> wrote:
> <plugin>
> <artifactId>maven-site-plugin</artifactId>
> <version>3.3</version>
> <configuration>
> <reportPlugins>
> <plugin>
> <groupId>..</groupId>
> <artifactId>..</artifactId>
> <version>..</version>
> <dependencies>
> <dependency>
> <artifactId>..</artifactId>
> <groupId>..</groupId>
> ...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org