You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tim Moore (JIRA)" <ji...@codehaus.org> on 2010/03/25 07:18:23 UTC
[jira] Created: (MCHECKSTYLE-136) Running checkstyle:check on the
top-level POM of a multi-module build fails
Running checkstyle:check on the top-level POM of a multi-module build fails
---------------------------------------------------------------------------
Key: MCHECKSTYLE-136
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.5
Reporter: Tim Moore
{noformat}
[INFO] [checkstyle:check]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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] Commented: (MCHECKSTYLE-136) Running checkstyle:check on the
top-level POM of a multi-module build fails
Posted by "Tim Moore (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216256#action_216256 ]
Tim Moore commented on MCHECKSTYLE-136:
---------------------------------------
Oliver,
The {{-Dcheckstyle.skipExec}} flag is a bit of a trick. That tells the {{checkstyle:check}} goal not to run Checkstyle itself, but to check the existing results of a previous run. The {{checkstyle:checkstyle}} invocation right before it _does_ run Checkstyle, and doesn't look at the {{checkstyle.skipExec}} property, so the result is functionally the same, IIUC.
On further investigation, I think this issue is a duplicate of MCHECKSTYLE-130, which means it is fixed in trunk. I haven't tried yet, as there does not appear to be a 2.6-SNAPSHOT build available in central, and I haven't had a chance to build it myself.
> Running checkstyle:check on the top-level POM of a multi-module build fails
> ---------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-136
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Tim Moore
>
> {noformat}
> [INFO] [checkstyle:check]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
> This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
> Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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] Commented: (MCHECKSTYLE-136) Running checkstyle:check on the
top-level POM of a multi-module build fails
Posted by "Tim Moore (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=215245#action_215245 ]
Tim Moore commented on MCHECKSTYLE-136:
---------------------------------------
Workaround, run: '{{mvn checkstyle:checkstyle checkstyle:check -Dcheckstyle.skipExec}}' instead of '{{mvn checkstyle:check}}'
> Running checkstyle:check on the top-level POM of a multi-module build fails
> ---------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-136
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Tim Moore
>
> {noformat}
> [INFO] [checkstyle:check]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
> This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
> Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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] Commented: (MCHECKSTYLE-136) Running checkstyle:check on the
top-level POM of a multi-module build fails
Posted by "oliver.burkhalter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=217048#action_217048 ]
oliver.burkhalter commented on MCHECKSTYLE-136:
-----------------------------------------------
With the configuration {{skipExec}} the build doesn't throw anymore this error message, thanks for the tipp!
> Running checkstyle:check on the top-level POM of a multi-module build fails
> ---------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-136
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Tim Moore
>
> {noformat}
> [INFO] [checkstyle:check]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
> This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
> Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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-136) Running checkstyle:check on the
top-level POM of a multi-module build fails
Posted by "Tim Moore (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Moore closed MCHECKSTYLE-136.
---------------------------------
Resolution: Duplicate
> Running checkstyle:check on the top-level POM of a multi-module build fails
> ---------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-136
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Tim Moore
>
> {noformat}
> [INFO] [checkstyle:check]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
> This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
> Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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] Issue Comment Edited: (MCHECKSTYLE-136) Running
checkstyle:check on the top-level POM of a multi-module build fails
Posted by "oliver.burkhalter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216156#action_216156 ]
oliver.burkhalter edited comment on MCHECKSTYLE-136 at 3/31/10 8:07 AM:
------------------------------------------------------------------------
I'm facing the same problem. We have a parent pom an several submodules and sub-submodules.
Maybe a quick solution would be to activate the Checkstyle-Plugin only on the corresponding submodules, but this is a bit a pain(we have about 20 sub-modules)
The skip-Option for the Checkstyle-Plugin is not a solution for me, because we have to fullfill some business coding rules.
Is there maybe any other solution?
We use the current Maven 2.2.1 version.
was (Author: oliver.burkhalter):
I'm facing the same problem. We have a parent pom an several submodules and sub-submodules.
Maybe a quick solution would be to activate the Checkstyle-Plugin only on the corresponding submodules, but this is a bit a pain.
The skip-Option for the Checkstyle-Plugin is not a solution for me, because we have to fullfill some business coding rules.
Is there maybe any other solution?
We use the current Maven 2.2.1 version.
> Running checkstyle:check on the top-level POM of a multi-module build fails
> ---------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-136
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Tim Moore
>
> {noformat}
> [INFO] [checkstyle:check]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
> This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
> Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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] Issue Comment Edited: (MCHECKSTYLE-136) Running
checkstyle:check on the top-level POM of a multi-module build fails
Posted by "oliver.burkhalter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216156#action_216156 ]
oliver.burkhalter edited comment on MCHECKSTYLE-136 at 3/31/10 7:10 AM:
------------------------------------------------------------------------
I'm facing the same problem. We have a parent pom an several submodules and sub-submodules.
Maybe a quick solution would be to activate the Checkstyle-Plugin only on the corresponding submodules, but this is a bit a pain.
The skip-Option for the Checkstyle-Plugin is not a solution for me, because we have to fullfill some business coding rules.
Is there maybe any other solution?
We use the current Maven 2.2.1 version.
was (Author: oliver.burkhalter):
I'm facing the same problem. We have a parent pom an several submodules and sub-submodules.
Maybe a quick solution would be to activate the Checkstyle-Plugin only on the corresponding submodules, but this is a bit a pain.
The skip-Option for the Checkstyle-Plugin is not a solution for me, because we have to fullfill some business coding rules.
Is there maybe any other solution?
> Running checkstyle:check on the top-level POM of a multi-module build fails
> ---------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-136
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Tim Moore
>
> {noformat}
> [INFO] [checkstyle:check]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
> This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
> Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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] Commented: (MCHECKSTYLE-136) Running checkstyle:check on the
top-level POM of a multi-module build fails
Posted by "oliver.burkhalter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHECKSTYLE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216156#action_216156 ]
oliver.burkhalter commented on MCHECKSTYLE-136:
-----------------------------------------------
I'm facing the same problem. We have a parent pom an several submodules and sub-submodules.
Maybe a quick solution would be to activate the Checkstyle-Plugin only on the corresponding submodules, but this is a bit a pain.
The skip-Option for the Checkstyle-Plugin is not a solution for me, because we have to fullfill some business coding rules.
Is there maybe any other solution?
> Running checkstyle:check on the top-level POM of a multi-module build fails
> ---------------------------------------------------------------------------
>
> Key: MCHECKSTYLE-136
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-136
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
> Affects Versions: 2.5
> Reporter: Tim Moore
>
> {noformat}
> [INFO] [checkstyle:check]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.IllegalStateException: basedir /Users/tmoore/Projects/atlassian/JST/src/main/java does not exist
> at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> {noformat}
> This is without an existing report. It appears to be a regression of MCHECKSTYLE-25 and MCHECKSTYLE-26
> Probably introduced when the check mojo was refactored to invoke checkstyle directly rather than executing the report (http://svn.apache.org/viewvc?view=revision&revision=836274)
--
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