#10857 maven-javadoc-plugin retired: All maven RPM macros and builds now broken
Closed: Fixed 2 years ago by phsmoura. Opened 2 years ago by minfrin.

Name of the package?

maven-javadoc-plugin

FAS username of the new maintainer?

Branches that you need it to be unretired for?

Rawhide

Package re-review BZ URL?

Any extra information?

The maven macros in RPM packaging depend on maven-javadoc-plugin as part of their builds.

The maven-javadoc-plugin package was retired, and now it is not possible to build any RPM out of anything built with maven.

Please reinstate the package.

  • /usr/bin/python3 /usr/share/java-utils/mvn_build.py --xmvn-javadoc
    Executing: xmvn --batch-mode --offline verify org.fedoraproject.xmvn:xmvn-mojo:install org.fedoraproject.xmvn:xmvn-mojo:javadoc org.fedoraproject.xmvn:xmvn-mojo:builddep
    ['xmvn', '--batch-mode', '--offline', 'verify', 'org.fedoraproject.xmvn:xmvn-mojo:install', 'org.fedoraproject.xmvn:xmvn-mojo:javadoc', 'org.fedoraproject.xmvn:xmvn-mojo:builddep']
    [INFO] Scanning for projects...
    [INFO]
    [INFO] ---------------< org.apache.tomcat:jakartaee-migration >----------------
    [INFO] Building Apache Tomcat Migration Tool for Jakarta EE 1.0.0
    [INFO] --------------------------------[ jar ]---------------------------------
    [WARNING] The POM for org.apache.maven.plugins:maven-javadoc-plugin:jar:3.3.2 is missing, no dependency information available
    [INFO]
    [INFO] ------------------------------------------------------------------------
    [INFO] Skipping Apache Tomcat Migration Tool for Jakarta EE
    [INFO] This project has been banned from the build due to previous failures.
    [INFO] ------------------------------------------------------------------------
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 0.573 s
    [INFO] Finished at: 2022-06-26T13:28:15+02:00
    [INFO] ------------------------------------------------------------------------
    [ERROR] UndeclaredThrowableException: InvocationTargetException: Plugin org.apache.maven.plugins:maven-javadoc-plugin:3.3.2 or one of its dependencies could not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-javadoc-plugin:jar:3.3.2 has not been downloaded from it before.
    [ERROR]
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    error: Bad exit status from /var/tmp/rpm-tmp.lbotAB (%build)

RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.lbotAB (%build)


As far as I know Fedora 33+ and EPEL 8+ don't use the maven-javadoc-plugin to build the javadoc documentation. But the presence of a configuration block for it sometimes messes up the build.

In some packages I maintain I add in %prep

%pom_remove_plugin org.apache.maven.plugins:maven-javadoc-plugin

to avoid these issues.

See e.g.
https://koji.fedoraproject.org/koji/packageinfo?packageID=16842

So, releng cannot just unretire this. It needs to have some package maintainer(s) who will maintain it. Also, if it's been retired more than 8 weeks, it will need a re-review.

This is a common error indicating missing dependency.
But maven-javadoc-plugin is not used by default by RPM macros any longer, it must be listed explicitly in upstream POM files.
In most cases it should be enough to remove the plugin from POM files, like this, and rely on built-in mechanisms for generating javadocs.

We are closing this issue, seems that people have shared ways to work this problem around. If the issue still persists even trying those suggestions fell free to reopen it

Metadata Update from @phsmoura:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata