RE: reporting plugin dependency question

[Adam Leggett]

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:strub...@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-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org