osdir.com

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RNG] How to enable japicmp?


Hi.

On 24/11/2018 10:48, Gilles wrote:
> Hi.
> 
> On Fri, 23 Nov 2018 15:37:15 +0100, Gilles wrote:
>> Hello.
>>
>> POM of [RNG] includes CP 47 which states:
>> ---CUT---
>> <!-- skip japicmp on "mvn site" - use "mvn package site" to include
>> report -->
>> ---CUT---
>>
>> Yet
>>  $ mvn package site site:stage
>> still produces an empty report, despite the presence of a
>>  profile.japicmp
>> file in directory
>>  src/site/resources
> 
> I copied this
> ---CUT---
>         <plugin>
>           <groupId>com.github.siom79.japicmp</groupId>
>           <artifactId>japicmp-maven-plugin</artifactId>
>           <configuration>
>             <skip>false</skip>
>           </configuration>
>         </plugin>
> ---CUT---
> from [Lang].[1]
> The plugin crashes with NPE.
> Last part of the stack trace:
> ---CUT---
> Caused by: java.lang.NullPointerException
>     at japicmp.maven.JApiCmpMojo.isPomModuleNeedingSkip
> (JApiCmpMojo.java:1243)
>     at japicmp.maven.JApiCmpMojo.executeWithParameters
> (JApiCmpMojo.java:130)
>     at japicmp.maven.JApiCmpReport.executeReport (JApiCmpReport.java:75)
>     at org.apache.maven.reporting.AbstractMavenReport.generate
> (AbstractMavenReport.java:255)
>     at
> org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
> (ReportDocumentRenderer.java:230)
>     at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
> (DefaultSiteRenderer.java:349)
>     at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
> (SiteMojo.java:198)
>     at org.apache.maven.plugins.site.render.SiteMojo.execute
> (SiteMojo.java:147)
>     at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:134)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
>     at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
>     at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>     at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
>     at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
>     at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
>     at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
>     at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
>     at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
>     at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
>     at java.lang.reflect.Method.invoke (Method.java:498)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:229)
>     at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:415)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:356)
> ---CUT---
> 
> Are there problems with "japicmp" that are specific to multi-modules
> projects?

It seems that's already fixed:
https://github.com/siom79/japicmp/issues/210

Worth trying with a newer version.

Best regards.

> Gilles
> 
> [1] Which confirms (?) that the profile-enabling of the report
>     does not work for "japicmp".  I couldn't find a page (build,
>     release, ?) that documents what works an not.
>     CP's doc is unclear about what can be overridden in
>     components/modules POMs.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
> For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx