You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mark Struberg <st...@yahoo.de> on 2009/01/08 15:45:54 UTC
reporting plugin dependency question
Hi!
I'm currently enabling the checkstyle plugin for the OpenWebBeans build and stumbled over an interesting problem:
I'd like to define the openwebbeans_checks.xml in an own artifact for being used in different modules. My first idea was to simply define the checkstyle plugin in the reporting section kind of:
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.2</version>
<configuration>
<configLocation>default/openwebbeans_checks.xml</configLocation>
</configuration>
<dependencies>
<dependency>
<groupId>org.apache.openwebbeans</groupId>
<artifactId>checkstyle</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
...
</reporting>
But there is no way to specify dependencies for a reporting plugin, isn't it? Is this intended?
The only thing I could do is to also specify the plugin with its dependency in the <build><pluginManagement> section, but that's not really handsome.
WDYT? Should I create a Jira?
LieGrue,
strub
----------------------------------------------------------------
“Multiple exclamation marks are a sure sign of a diseased mind!”
(Sir Terry Pratchett)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: reporting plugin dependency question
Posted by Mark Struberg <st...@yahoo.de>.
And I apologies for obviously searching not good enough in Jira - so thank you for finding the bug for me :)
--- Adam Leggett <ad...@upco.co.uk> schrieb am Do, 8.1.2009:
> Von: Adam Leggett <ad...@upco.co.uk>
> Betreff: RE: reporting plugin dependency question
> An: "Maven Users List" <us...@maven.apache.org>
> Datum: Donnerstag, 8. Januar 2009, 17:13
> Apologies Mark, I seem to have not read all the way to the
> bottom of
> your mail :).
>
> Looks like this is an issue already -
> http://jira.codehaus.org/browse/MNG-1948, roadmapped for
> 3.x
>
> Adam
>
>
> -----Original Message-----
> From: Mark Struberg [mailto:struberg@yahoo.de]
> Sent: 08 January 2009 15:04
> To: Maven Users List
> Subject: RE: reporting plugin dependency question
>
> Yup Adam, that's exactly what I'm doing currently.
>
> I just wonder if not being able to specify dependencies in
> the reporting
> section is so by design (and there is a good reason for
> this), or if
> this is something we may improve in maven-3.0.
>
> txs and LieGrue,
> strub
> ----------------------------------------------------------------
> "Multiple exclamation marks are a sure sign of a
> diseased mind!"
> (Sir Terry Pratchett)
>
>
> --- Adam Leggett <ad...@upco.co.uk> schrieb am
> Do, 8.1.2009:
>
> > Von: Adam Leggett <ad...@upco.co.uk>
> > Betreff: RE: reporting plugin dependency question
> > An: "Maven Users List"
> <us...@maven.apache.org>
> > Datum: Donnerstag, 8. Januar 2009, 15:56
> > I think you need to specify the dependency within the
> > <build> section of
> > the pom and then reference in the reporting section:
> >
> > <build>
> > <plugins>
> > <plugin>
> >
> >
> <groupId>org.apache.maven.plugins</groupId>
> >
> >
> <artifactId>maven-checkstyle-plugin</artifactId>
> > <dependencies>
> > <dependency>
> >
> > <groupId>com.example.whizbang</groupId>
> >
> > <artifactId>build-tools</artifactId>
> > <version>1.0</version>
> > </dependency>
> > </dependencies>
> > </plugin>
> > </plugins>
> > </build>
> > <reporting>
> > <plugins>
> > <plugin>
> >
> >
> <groupId>org.apache.maven.plugins</groupId>
> >
> >
> <artifactId>maven-checkstyle-plugin</artifactId>
> > <configuration>
> >
> >
> <configLocation>whizbang/checkstyle.xml</configLocation>
> >
> >
> <headerLocation>whizbang/LICENSE.txt</headerLocation>
> > </configuration>
> > </plugin>
> > </plugins>
> > </reporting>
> >
> >
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-m
> > odule-config.html
> >
> > -----Original Message-----
> > From: Mark Struberg [mailto:struberg@yahoo.de]
> > Sent: 08 January 2009 14:46
> > To: users@maven.apache.org
> > Subject: reporting plugin dependency question
> >
> > Hi!
> >
> > I'm currently enabling the checkstyle plugin for
> the
> > OpenWebBeans build
> > and stumbled over an interesting problem:
> >
> > I'd like to define the openwebbeans_checks.xml in
> an
> > own artifact for
> > being used in different modules. My first idea was to
> > simply define the
> > checkstyle plugin in the reporting section kind of:
> >
> >
> > <reporting>
> > <plugins>
> > <plugin>
> >
> >
> <groupId>org.apache.maven.plugins</groupId>
> >
> >
> <artifactId>maven-checkstyle-plugin</artifactId>
> > <version>2.2</version>
> > <configuration>
> >
> >
> <configLocation>default/openwebbeans_checks.xml</configLocation>
> > </configuration>
> > <dependencies>
> > <dependency>
> >
> > <groupId>org.apache.openwebbeans</groupId>
> >
> <artifactId>checkstyle</artifactId>
> > <version>1.0-SNAPSHOT</version>
> > </dependency>
> > </dependencies>
> > </plugin>
> > ...
> > </reporting>
> >
> > But there is no way to specify dependencies for a
> reporting
> > plugin,
> > isn't it? Is this intended?
> >
> > The only thing I could do is to also specify the
> plugin
> > with its
> > dependency in the
> <build><pluginManagement>
> > section, but that's not
> > really handsome.
> >
> > WDYT? Should I create a Jira?
> >
> > LieGrue,
> > strub
> >
> ----------------------------------------------------------------
> > "Multiple exclamation marks are a sure sign of a
> > diseased mind!"
> > (Sir Terry Pratchett)
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > 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
>
>
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: reporting plugin dependency question
Posted by Adam Leggett <ad...@upco.co.uk>.
Apologies Mark, I seem to have not read all the way to the bottom of
your mail :).
Looks like this is an issue already -
http://jira.codehaus.org/browse/MNG-1948, roadmapped for 3.x
Adam
-----Original Message-----
From: Mark Struberg [mailto:struberg@yahoo.de]
Sent: 08 January 2009 15:04
To: Maven Users List
Subject: RE: reporting plugin dependency question
Yup Adam, that's exactly what I'm doing currently.
I just wonder if not being able to specify dependencies in the reporting
section is so by design (and there is a good reason for this), or if
this is something we may improve in maven-3.0.
txs and LieGrue,
strub
----------------------------------------------------------------
"Multiple exclamation marks are a sure sign of a diseased mind!"
(Sir Terry Pratchett)
--- Adam Leggett <ad...@upco.co.uk> schrieb am Do, 8.1.2009:
> Von: Adam Leggett <ad...@upco.co.uk>
> Betreff: RE: reporting plugin dependency question
> An: "Maven Users List" <us...@maven.apache.org>
> Datum: Donnerstag, 8. Januar 2009, 15:56
> I think you need to specify the dependency within the
> <build> section of
> the pom and then reference in the reporting section:
>
> <build>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <dependencies>
> <dependency>
>
> <groupId>com.example.whizbang</groupId>
>
> <artifactId>build-tools</artifactId>
> <version>1.0</version>
> </dependency>
> </dependencies>
> </plugin>
> </plugins>
> </build>
> <reporting>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <configuration>
>
> <configLocation>whizbang/checkstyle.xml</configLocation>
>
> <headerLocation>whizbang/LICENSE.txt</headerLocation>
> </configuration>
> </plugin>
> </plugins>
> </reporting>
>
>
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-m
> odule-config.html
>
> -----Original Message-----
> From: Mark Struberg [mailto:struberg@yahoo.de]
> Sent: 08 January 2009 14:46
> To: users@maven.apache.org
> Subject: reporting plugin dependency question
>
> Hi!
>
> I'm currently enabling the checkstyle plugin for the
> OpenWebBeans build
> and stumbled over an interesting problem:
>
> I'd like to define the openwebbeans_checks.xml in an
> own artifact for
> being used in different modules. My first idea was to
> simply define the
> checkstyle plugin in the reporting section kind of:
>
>
> <reporting>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <version>2.2</version>
> <configuration>
>
> <configLocation>default/openwebbeans_checks.xml</configLocation>
> </configuration>
> <dependencies>
> <dependency>
>
> <groupId>org.apache.openwebbeans</groupId>
> <artifactId>checkstyle</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
> </dependencies>
> </plugin>
> ...
> </reporting>
>
> But there is no way to specify dependencies for a reporting
> plugin,
> isn't it? Is this intended?
>
> The only thing I could do is to also specify the plugin
> with its
> dependency in the <build><pluginManagement>
> section, but that's not
> really handsome.
>
> WDYT? Should I create a Jira?
>
> LieGrue,
> strub
> ----------------------------------------------------------------
> "Multiple exclamation marks are a sure sign of a
> diseased mind!"
> (Sir Terry Pratchett)
>
>
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
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: reporting plugin dependency question
Posted by Mark Struberg <st...@yahoo.de>.
Yup Adam, that's exactly what I'm doing currently.
I just wonder if not being able to specify dependencies in the reporting section is so by design (and there is a good reason for this), or if this is something we may improve in maven-3.0.
txs and LieGrue,
strub
----------------------------------------------------------------
“Multiple exclamation marks are a sure sign of a diseased mind!”
(Sir Terry Pratchett)
--- Adam Leggett <ad...@upco.co.uk> schrieb am Do, 8.1.2009:
> Von: Adam Leggett <ad...@upco.co.uk>
> Betreff: RE: reporting plugin dependency question
> An: "Maven Users List" <us...@maven.apache.org>
> Datum: Donnerstag, 8. Januar 2009, 15:56
> I think you need to specify the dependency within the
> <build> section of
> the pom and then reference in the reporting section:
>
> <build>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <dependencies>
> <dependency>
>
> <groupId>com.example.whizbang</groupId>
>
> <artifactId>build-tools</artifactId>
> <version>1.0</version>
> </dependency>
> </dependencies>
> </plugin>
> </plugins>
> </build>
> <reporting>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <configuration>
>
> <configLocation>whizbang/checkstyle.xml</configLocation>
>
> <headerLocation>whizbang/LICENSE.txt</headerLocation>
> </configuration>
> </plugin>
> </plugins>
> </reporting>
>
> http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-m
> odule-config.html
>
> -----Original Message-----
> From: Mark Struberg [mailto:struberg@yahoo.de]
> Sent: 08 January 2009 14:46
> To: users@maven.apache.org
> Subject: reporting plugin dependency question
>
> Hi!
>
> I'm currently enabling the checkstyle plugin for the
> OpenWebBeans build
> and stumbled over an interesting problem:
>
> I'd like to define the openwebbeans_checks.xml in an
> own artifact for
> being used in different modules. My first idea was to
> simply define the
> checkstyle plugin in the reporting section kind of:
>
>
> <reporting>
> <plugins>
> <plugin>
>
> <groupId>org.apache.maven.plugins</groupId>
>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <version>2.2</version>
> <configuration>
>
> <configLocation>default/openwebbeans_checks.xml</configLocation>
> </configuration>
> <dependencies>
> <dependency>
>
> <groupId>org.apache.openwebbeans</groupId>
> <artifactId>checkstyle</artifactId>
> <version>1.0-SNAPSHOT</version>
> </dependency>
> </dependencies>
> </plugin>
> ...
> </reporting>
>
> But there is no way to specify dependencies for a reporting
> plugin,
> isn't it? Is this intended?
>
> The only thing I could do is to also specify the plugin
> with its
> dependency in the <build><pluginManagement>
> section, but that's not
> really handsome.
>
> WDYT? Should I create a Jira?
>
> LieGrue,
> strub
> ----------------------------------------------------------------
> "Multiple exclamation marks are a sure sign of a
> diseased mind!"
> (Sir Terry Pratchett)
>
>
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: reporting plugin dependency question
Posted by Adam Leggett <ad...@upco.co.uk>.
I think you need to specify the dependency within the <build> section of
the pom and then reference in the reporting section:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<dependencies>
<dependency>
<groupId>com.example.whizbang</groupId>
<artifactId>build-tools</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<configuration>
<configLocation>whizbang/checkstyle.xml</configLocation>
<headerLocation>whizbang/LICENSE.txt</headerLocation>
</configuration>
</plugin>
</plugins>
</reporting>
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-m
odule-config.html
-----Original Message-----
From: Mark Struberg [mailto:struberg@yahoo.de]
Sent: 08 January 2009 14:46
To: users@maven.apache.org
Subject: reporting plugin dependency question
Hi!
I'm currently enabling the checkstyle plugin for the OpenWebBeans build
and stumbled over an interesting problem:
I'd like to define the openwebbeans_checks.xml in an own artifact for
being used in different modules. My first idea was to simply define the
checkstyle plugin in the reporting section kind of:
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.2</version>
<configuration>
<configLocation>default/openwebbeans_checks.xml</configLocation>
</configuration>
<dependencies>
<dependency>
<groupId>org.apache.openwebbeans</groupId>
<artifactId>checkstyle</artifactId>
<version>1.0-SNAPSHOT</version>
</dependency>
</dependencies>
</plugin>
...
</reporting>
But there is no way to specify dependencies for a reporting plugin,
isn't it? Is this intended?
The only thing I could do is to also specify the plugin with its
dependency in the <build><pluginManagement> section, but that's not
really handsome.
WDYT? Should I create a Jira?
LieGrue,
strub
----------------------------------------------------------------
"Multiple exclamation marks are a sure sign of a diseased mind!"
(Sir Terry Pratchett)
---------------------------------------------------------------------
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