You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Ian Rowlands (JIRA)" <ji...@codehaus.org> on 2007/05/29 06:00:58 UTC

[jira] Created: (MCHECKSTYLE-73) Checkstyle has trouble locating config file using build extensions in a multi-module project

Checkstyle has trouble locating config file using build extensions in a multi-module project
--------------------------------------------------------------------------------------------

                 Key: MCHECKSTYLE-73
                 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-73
             Project: Maven 2.x Checkstyle Plugin
          Issue Type: Bug
    Affects Versions: 2.1
         Environment: Windows 2000 Workstation / Windows Server 2003
            Reporter: Ian Rowlands
            Priority: Minor


The example used to configure a multi-module project fails to work when you add additional java code to the project containing the config file.

To reproduce:
1.  Create 2 projects (call them A and Z).  A is the parent of Z.  Z contains the code, and is where you run the "site" command from.
2.  Create another project (called "Build").  This contains the checkstyle config file.
3.  Configure project A to use Build as an extension (as specified in http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html).
4.  Run "mvn site" in project Z, after deploying the other projects.
5.  Add some java code to project Build, and deploy it.
6.  Run "mvn site" in project Z, which produces the following error:
    Embedded error: Error rendering Maven report: Unable to find configuration file location.

As soon as you take out the java code, everything goes back to normal.

There is a workaround - set project Build as a plugin dependency.  This has no problems in both cases.


-- 
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

        

[jira] Closed: (MCHECKSTYLE-73) Checkstyle has trouble locating config file using build extensions in a multi-module project

Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MCHECKSTYLE-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg closed MCHECKSTYLE-73.
--------------------------------------

    Resolution: Won't Fix

Adding the custom configuration as a plugin dependency is the preferred way.

> Checkstyle has trouble locating config file using build extensions in a multi-module project
> --------------------------------------------------------------------------------------------
>
>                 Key: MCHECKSTYLE-73
>                 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-73
>             Project: Maven 2.x Checkstyle Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: Windows 2000 Workstation / Windows Server 2003
>            Reporter: Ian Rowlands
>            Priority: Minor
>
> The example used to configure a multi-module project fails to work when you add additional java code to the project containing the config file.
> To reproduce:
> 1.  Create 2 projects (call them A and Z).  A is the parent of Z.  Z contains the code, and is where you run the "site" command from.
> 2.  Create another project (called "Build").  This contains the checkstyle config file.
> 3.  Configure project A to use Build as an extension (as specified in http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html).
> 4.  Run "mvn site" in project Z, after deploying the other projects.
> 5.  Add some java code to project Build, and deploy it.
> 6.  Run "mvn site" in project Z, which produces the following error:
>     Embedded error: Error rendering Maven report: Unable to find configuration file location.
> As soon as you take out the java code, everything goes back to normal.
> There is a workaround - set project Build as a plugin dependency.  This has no problems in both cases.

-- 
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