[ http://jira.codehaus.org/browse/MCHECKSTYLE-10?page=comments#action_54283
]
Carlos Sanchez commented on MCHECKSTYLE-10:
-------------------------------------------
Workaround:
Add extensions to your build section
<extensions>
<extension>
<groupId>checkstyle</groupId>
<artifactId>checkstyle</artifactId>
<version>4.1</version>
</extension>
</extensions>
unfortunately that causes another problem
[INFO] org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
[INFO]
----------------------------------------------------------------------------
[DEBUG] Trace
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:532)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:272)
at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:246)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:395)
at
org.apache.commons.beanutils.ConvertUtilsBean.<init>(ConvertUtilsBean.java:130)
at
com.puppycrawl.tools.checkstyle.api.AutomaticBean.createBeanUtilsBean(AutomaticBean.java:73)
at
com.puppycrawl.tools.checkstyle.api.AutomaticBean.configure(AutomaticBean.java:150)
at
org.apache.maven.plugin.checkstyle.CheckstyleReport.executeCheckstyle(CheckstyleReport.java:632)
at
org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:457)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
at
org.apache.maven.plugins.site.SiteMojo.generateReportsPages(SiteMojo.java:922)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:361)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:414)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:531)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:472)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
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:585)
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)
Caused by: org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:416)
at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
... 29 more
Caused by: org.apache.commons.logging.LogConfigurationException: Class
org.apache.commons.logging.impl.Log4JLogger does not implement Log
at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:412)
... 30 more
> Exception when creating Checkstyle report as part of a 'site' build
> -------------------------------------------------------------------
>
> Key: MCHECKSTYLE-10
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-10
> Project: Maven 2.x Checkstyle Plugin
> Type: Bug
> Versions: 2.0-beta-2
> Environment: Windows XP, JDK 1.4.2_10, Maven 2.0.2-SNAPSHOT,
> maven-checkstyle-plugin 2.0-beta-2-SNAPSHOT
> Reporter: Nick Giles
> Priority: Blocker
> Fix For: 2.0-beta-2
> Attachments: error_trace.txt
>
>
> When attempting to create a project site including a checkstyle report, the
> build fails with the attached stack trace. However, when creating a
> checkstyle report simply by running 'mvn checkstyle:checkstyle', the build is
> successful and the report is produced.
> From some initial investigation, it appears that the classloader passed in to
> checkstyle itself by the plugin can locate essential resources when the build
> is specifically for checkstyle, but cannot locate them when it is invoked as
> part of a call for 'site'. This can be tested by adding the following lines
> of code into
> org.apache.maven.plugin.checkstyle.CheckstyleReport.getModuleFactory(), where
> 'loader' is the ClassLoader being passed to the PackageNamesLoader:
> getLog().info("\n\n\n\nClass loader: " + loader.getClass().getName());
> getLog().info("Input stream: " +
> loader.getResourceAsStream("com/puppycrawl/tools/checkstyle/checkstyle_packages.xml"));
> getLog().info("DTD: " +
> loader.getResourceAsStream("com/puppycrawl/tools/checkstyle/packages_1_0.dtd"));
> These should show jar file URLs if found, and null if not, which will happen
> respectively when run as 'mvn checkstyle:checkstyle' and 'mvn site'.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
