[
https://issues.apache.org/jira/browse/MSITE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898911#comment-17898911
]
Gary D. Gregory commented on MSITE-1026:
----------------------------------------
If I update [https://gitbox.apache.org/repos/asf/commons-parent.git] from
2.12.1 to 3.0.0-SNAPSHOT I get:
[INFO] Generating "JIRA Report" report ---
maven-changes-plugin:3.0.0-SNAPSHOT:jira-report
[WARNING] An issue has occurred with
maven-changes-plugin:3.0.0-SNAPSHOT:jira-report report, skipping LinkageError
'boolean com.fasterxml.jackson.core.JsonFactory.requiresPropertyOrdering()',
please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'boolean
com.fasterxml.jackson.core.JsonFactory.requiresPropertyOrdering()'
at com.fasterxml.jackson.databind.ObjectMapper.<init>
(ObjectMapper.java:649)
at com.fasterxml.jackson.databind.ObjectMapper.<init>
(ObjectMapper.java:567)
at com.fasterxml.jackson.databind.MappingJsonFactory.<init>
(MappingJsonFactory.java:31)
at com.fasterxml.jackson.databind.MappingJsonFactory.<init>
(MappingJsonFactory.java:24)
at org.apache.maven.plugins.jira.RestJiraDownloader.<init>
(RestJiraDownloader.java:93)
at org.apache.maven.plugins.jira.AdaptiveJiraDownloader.doExecute
(AdaptiveJiraDownloader.java:36)
at org.apache.maven.plugins.jira.JiraMojo.executeReport (JiraMojo.java:339)
at org.apache.maven.reporting.AbstractMavenReport.generate
(AbstractMavenReport.java:255)
at
org.apache.maven.plugins.site.render.ReportDocumentRenderer.renderDocument
(ReportDocumentRenderer.java:226)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render
(DefaultSiteRenderer.java:348)
at org.apache.maven.plugins.site.render.SiteMojo.renderLocale
(SiteMojo.java:194)
at org.apache.maven.plugins.site.render.SiteMojo.execute (SiteMojo.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:126)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2
(MojoExecutor.java:328)
at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute
(MojoExecutor.java:316)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:212)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:174)
at org.apache.maven.lifecycle.internal.MojoExecutor.access$000
(MojoExecutor.java:75)
at org.apache.maven.lifecycle.internal.MojoExecutor$1.run
(MojoExecutor.java:162)
at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute
(DefaultMojosExecutionStrategy.java:39)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:159)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:105)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:73)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:53)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:118)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:206)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:77)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:569)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:255)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:201)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:361)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:314)
> How to go ahead as a user of unsupported plugins - is there a documentation
> available to fix (newly built) broken site-webpages
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: MSITE-1026
> URL: https://issues.apache.org/jira/browse/MSITE-1026
> Project: Maven Site Plugin
> Issue Type: Improvement
> Affects Versions: 3.21.0
> Reporter: Philipp Ottlinger
> Priority: Critical
>
> If I understood correctly some of the plugins are not planned for migration
> to the new doxia stack, such as:
> * maven-changes-plugin -
> https://maven.apache.org/plugins/maven-changes-plugin/
> * jdepend-plugin - [broken report
> example|https://ottlinger.github.io/fotorenamer/jdepend-report.html]
> * dev-activity-report - [broken report
> example|https://ottlinger.github.io/fotorenamer/dev-activity.html]
> * file-activity-report - [broken report
> example|https://ottlinger.github.io/fotorenamer/file-activity.html]
> From a consumer perspective that results in broken site reports as the new
> layout does not play well with the new maven-site-plugin as can be seen by
> comparing OLD (pre-2.x) and NEW (doxia-2.x) on Apache Creadur:
> * OLD - formatted ok:
> ** https://creadur.apache.org/rat/
> ** https://creadur.apache.org/rat/changes-report.html
> ** https://creadur.apache.org/rat/jira-report.html
> * NEW - broken layout: test deployed while working on RAT-397
> ** https://creadur.apache.org/RAT-397/
> ** https://creadur.apache.org/RAT-397/changes-report.html
> ** https://creadur.apache.org/RAT-397/jira-report.html
> Via chat [~michaelo] suggested that there is a way to configure a post-site
> step that transforms the old format into the new format .... where can I find
> more details or examples on what to do in order to accomplish a more complete
> and correctly formatted site/webpage with the new stack.
> Thanks for any help, hints, examples or documentation
> -------
> [~ggregory] does commons have a solution for the problem? How do you solve
> the problem?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
