On 2012-04-25 14:36, Gilles Sadowski wrote:
> Hi.
>
>>>>>
>>>>> Clirr now fails the build on error:
>>>>> ---CUT---
>>>>> [ERROR] Unable to find information in class
>>>>> [org.apache.commons.math3.linear.SymmLQ referring back to nested class
>>>>> [org.apache.commons.math3.linear.SymmLQ$SymmLQEvent ERROR] Unable to
>>>>> [find information in class
>>>>> [org.apache.commons.math3.optimization.direct.PowellOptimizer referring
>>>>> [back to nested class
>>>>>
>> [org.apache.commons.math3.optimization.direct.PowellOptimizer$SimpleValueChecker
>>>>> ---CUT---
>>>>>
>>>>> Since I don't know what causes those errors, I'd like to be able to
>>>>> skip the "clirr" check altogether.
>>>>
>>>> Clirr does not like the output from the Eclipse compiler.
>>>> Make sure you run mvn clean first - and ensure that Eclipse is not set
>>>> to build the project.
>>>>
>>>>> I tried to mimic settings suggested in an earlier messafe about
>>>>> skipping lengthy report, i.e.
>>>>> <clirr.skip>true</clirr.skip>
>>>>
>>>> AFAIK, that's not the same as setting a command-line property.
>>>
>>> This syntax worked for other reports (you suggested it).
>>>
>>>>
>>>>> It didn't work.
>>>>>
>>>>> I tried this:
>>>>> <clirr.fail.on.error>false</clirr.fail.on.error>
>>>>> as documented here:
>>>>> http://clirr.sourceforge.net/clirr-maven/properties.html
>>>>
>>>> That is for an obsolete version of the Clirr plugin
>>>>
>>>> The current version is documented at:
>>>>
>>>> http://mojo.codehaus.org/clirr-maven-plugin/
>>>
>>> The usage page there is rather terse, there is no information about
>>> which properties could alter the behaviour of the plugin (like disabling
>>> it, making just a warning, not a error that fails the build).
>>
>> The properties from command line should be the ones used in "Expression:"
>> http://mojo.codehaus.org/clirr-maven-plugin/check-mojo.html
>
> Thanks.
> I tried "failOnError" set to "false". Didn't work.
>
> Here the stack trace from maven output:
> ---CUT---
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project commons-math3: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project commons-math3: Execution default-site of goal
> org.apache.maven.plugins:maven-site-plugin:3.0:site failed: 780
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-site of goal org.apache.maven.plugins:maven-site-plugin:3.0:site
> failed: 780
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 780
> at
> org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:666)
> at
> org.codehaus.mojo.clirr.AbstractClirrMojo.reportDiffs(AbstractClirrMojo.java:679)
> at
> org.codehaus.mojo.clirr.AbstractClirrMojo.executeClirr(AbstractClirrMojo.java:263)
> at org.codehaus.mojo.clirr.ClirrReport.doReport(ClirrReport.java:243)
> at org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:219)
> at org.codehaus.mojo.clirr.ClirrReport.generate(ClirrReport.java:355)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:228)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:317)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:134)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 20 more
> ---CUT---
>
> Does anyone have an idea of what can cause this?
Yep, that's a bug in the clirr-maven-plugin that was fixed in the latest
release.
Please use version 2.4 of clirr-maven-plugin.
>
> In the meantime, I'd be glad to be able to disable this tool... :-{
>
>>
>>>>> It didn't work.
>>>>>
>>>>
>>>> mvn .... -Dclirr.skip
>>>>
>>>> works for me.
>>>
>>> Doesn't work here! Using:
>>>
>>> $ mvn -version
>>> Apache Maven 3.0.4
>>> Maven home: /usr/share/maven
>>> Java version: 1.7.0_03-icedtea, vendor: Oracle Corporation
>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "2.6.32-5-vserver-amd64", arch: "amd64",
>>> family: "unix"
>>
>> Can you try with M221? Maybe the system property is no longer passed to the
>> forked process ... :-/
>> Or try to use the check-no-fork goal instead.
>
> I'm launching the "site" target. I really don't know much about maven. How
> can I do that?
>
> Thanks,
> Gilles
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
