You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mike Perham (JIRA)" <ji...@codehaus.org> on 2006/01/19 17:41:40 UTC
[jira] Created: (MCHECKSTYLE-31) Multi-module reports do not
support custom classpath configurations
Multi-module reports do not support custom classpath configurations
-------------------------------------------------------------------
Key: MCHECKSTYLE-31
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-31
Project: Maven 2.x Checkstyle Plugin
Type: Bug
Versions: 2.0-beta-1
Reporter: Mike Perham
Priority: Critical
Fix For: 2.0-beta-2
The latest multi-module tip shows the following:
{noformat}
<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>
<dependencies>
<dependency>
<groupId>com.example.whizbang</groupId>
<artifactId>build-tools</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</reporting>
{noformat}
This is invalid according to the latest 2.0.2 POM schema. <dependencies> is not supported in reporting plugins.
So it seems impossible to provide a custom config in a multi-module build without using a network URL as we cannot use File or classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MCHECKSTYLE-31) Multi-module reports do not
support custom classpath configurations
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-31?page=all ]
fabrizio giustina reopened MCHECKSTYLE-31:
------------------------------------------
reopen: configuring the dependency as a project-wide dependency works but it's not what we want.
Configuring the build-tools dependency as a plugin dependency doesn't work either if the checkstyle plugin is called as a report, neither if it's called using checkstyle:check directly, see MCHECKSTYLE-27
> Multi-module reports do not support custom classpath configurations
> -------------------------------------------------------------------
>
> Key: MCHECKSTYLE-31
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-31
> Project: Maven 2.x Checkstyle Plugin
> Type: Bug
> Versions: 2.0-beta-1
> Reporter: Mike Perham
> Assignee: fabrizio giustina
> Priority: Critical
> Fix For: 2.0-beta-2
>
>
> The latest multi-module tip shows the following:
> {noformat}
> <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>
> <dependencies>
> <dependency>
> <groupId>com.example.whizbang</groupId>
> <artifactId>build-tools</artifactId>
> <version>1.0</version>
> </dependency>
> </dependencies>
> </plugin>
> </plugins>
> </reporting>
> {noformat}
> This is invalid according to the latest 2.0.2 POM schema. <dependencies> is not supported in reporting plugins.
> So it seems impossible to provide a custom config in a multi-module build without using a network URL as we cannot use File or classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MCHECKSTYLE-31) Multi-module reports do not support
custom classpath configurations
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-31?page=all ]
fabrizio giustina closed MCHECKSTYLE-31:
----------------------------------------
Assign To: fabrizio giustina
Resolution: Fixed
documentation issue, pom snippet fixed in svn
> Multi-module reports do not support custom classpath configurations
> -------------------------------------------------------------------
>
> Key: MCHECKSTYLE-31
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-31
> Project: Maven 2.x Checkstyle Plugin
> Type: Bug
> Versions: 2.0-beta-1
> Reporter: Mike Perham
> Assignee: fabrizio giustina
> Priority: Critical
> Fix For: 2.0-beta-2
>
>
> The latest multi-module tip shows the following:
> {noformat}
> <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>
> <dependencies>
> <dependency>
> <groupId>com.example.whizbang</groupId>
> <artifactId>build-tools</artifactId>
> <version>1.0</version>
> </dependency>
> </dependencies>
> </plugin>
> </plugins>
> </reporting>
> {noformat}
> This is invalid according to the latest 2.0.2 POM schema. <dependencies> is not supported in reporting plugins.
> So it seems impossible to provide a custom config in a multi-module build without using a network URL as we cannot use File or classpath.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org