Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 19, 2025

Bumps org.apache.maven.plugins:maven-javadoc-plugin from 3.11.2 to 3.11.3.

Release notes

Sourced from org.apache.maven.plugins:maven-javadoc-plugin's releases.

3.11.3

🚨 Removed

🚀 New features and improvements

🐛 Bug Fixes

  • Make the legacyMode consistent (Filter out all of the module-info.java files in legacy mode, do not use --source-path in legacy mode) (#1217) @​fridrich
  • [MJAVADOC-826] - Don't try to modify project source roots (#358) @​oehme

📝 Documentation updates

👻 Maintenance

📦 Dependency updates

... (truncated)

Commits
  • 8357bc2 [maven-release-plugin] prepare release maven-javadoc-plugin-3.11.3
  • ab6e97e Bump commons-io:commons-io from 2.19.0 to 2.20.0
  • 83788c1 Bump org.apache.commons:commons-text from 1.13.1 to 1.14.0
  • 99ee1fc Bump org.apache.commons:commons-lang3 in /src/it/projects/MJAVADOC-787
  • 18bfeb8 Maven Archiver 3.6.4 (#1226)
  • 63618bb Bump org.apache.commons:commons-lang3 (#1224)
  • 81afff9 Bump org.assertj:assertj-core from 3.27.3 to 3.27.4 (#1223)
  • 8bcdebf Add Apache 2.0 LICENSE file (#1220)
  • 2299072 Make the legacyMode consistent and actually useful (#1217)
  • 33c9f01 Be consistent about data encoding when copying files (#1215)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Aug 19, 2025
@akurtakov akurtakov force-pushed the dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.11.3 branch from ab51551 to 2c9348b Compare August 20, 2025 07:04
@akurtakov akurtakov force-pushed the dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.11.3 branch from 41ba79a to 65adc01 Compare September 1, 2025 07:22
@HannesWell HannesWell force-pushed the dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.11.3 branch from 65adc01 to e9134ad Compare September 10, 2025 17:59
@HannesWell
Copy link
Member

@akurtakov is this ready?

@akurtakov
Copy link
Member

TBH, I am not sure. Javadoc in non legacy mode(modules!) used to cause problems . If verification succeeds we might not have a choice but to merge it and see whether bundles javadoc fail after that.

dependabot bot and others added 2 commits September 11, 2025 18:11
Bumps [org.apache.maven.plugins:maven-javadoc-plugin](https://github.com/apache/maven-javadoc-plugin) from 3.11.2 to 3.11.3.
- [Release notes](https://github.com/apache/maven-javadoc-plugin/releases)
- [Commits](apache/maven-javadoc-plugin@maven-javadoc-plugin-3.11.2...maven-javadoc-plugin-3.11.3)

---
updated-dependencies:
- dependency-name: org.apache.maven.plugins:maven-javadoc-plugin
  dependency-version: 3.11.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Due to apache/maven-javadoc-plugin#1217 legacy
mode is no longer compatible with how sourcepath is defined.
@HannesWell HannesWell force-pushed the dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.11.3 branch from e9134ad to 279e4dc Compare September 11, 2025 16:11
@HannesWell
Copy link
Member

The verification build succeeded, then let's see if this also works in general.

@HannesWell HannesWell merged commit 404660e into master Sep 11, 2025
7 checks passed
@HannesWell HannesWell deleted the dependabot/maven/org.apache.maven.plugins-maven-javadoc-plugin-3.11.3 branch September 11, 2025 20:45
@akurtakov
Copy link
Member

So it broke the per module javadoc generation eclipse-equinox/p2#940 . Should we revert or give it some time for someone to investigate?

@iloveeclipse
Copy link
Member

So it broke the per module javadoc generation eclipse-equinox/p2#940 . Should we revert or give it some time for someone to investigate?

Also PDE build seems to be broken on Jenkins:

https://ci.eclipse.org/pde/job/eclipse.pde/job/PR-1965/2/pipeline-overview/

18:31:38  [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.11.3:jar (attach-javadocs) on project org.eclipse.pde.build: MavenReportException: Error while generating Javadoc: 
18:31:38  [ERROR] Exit code: 2
18:31:38  [ERROR] error: No source files for package org.eclipse.pde.build
18:31:38  [ERROR] 1 error
18:31:38  [ERROR] Command line was: /opt/tools/java/temurin/jdk-21/jdk-21.0.8+9/bin/javadoc -J-Duser.language= -J-Duser.country= @options @packages
18:31:38  [ERROR] 
18:31:38  [ERROR] Refer to the generated Javadoc files in '/home/jenkins/agent/workspace/eclipse.pde_PR-1965/build/org.eclipse.pde.build/target/reports/apidocs' dir.
18:31:38  [ERROR] -> [Help 1]
18:31:38  org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.11.3:jar (attach-javadocs) on project org.eclipse.pde.build: MavenReportException: Error while generating Javadoc: 
18:31:38  Exit code: 2
18:31:38  error: No source files for package org.eclipse.pde.build
18:31:38  1 error
18:31:38  Command line was: /opt/tools/java/temurin/jdk-21/jdk-21.0.8+9/bin/javadoc -J-Duser.language= -J-Duser.country= @options @packages
18:31:38  
18:31:38  Refer to the generated Javadoc files in '/home/jenkins/agent/workspace/eclipse.pde_PR-1965/build/org.eclipse.pde.build/target/reports/apidocs' dir.

@iloveeclipse
Copy link
Member

Should we revert or give it some time for someone to investigate?

With at least two projects affected I would revert.

@laeubi
Copy link
Contributor

laeubi commented Sep 12, 2025

The verification build succeeded, then let's see if this also works in general.

Please note that javadoc needs to be explicitly enabled with -Pjavadoc profile, but such changes are best tested with a local build first, the javadoc generation is quite brittle and the plugin often buggy, please report issues here:

@laeubi
Copy link
Contributor

laeubi commented Sep 13, 2025

I looked into this now and it could be that javadoc-plugin changed or it depends on java version (making a warning now an error).

@laeubi
Copy link
Contributor

laeubi commented Sep 13, 2025

@akurtakov is there any reason the <legacyMode> option was removed?

From the docu

Run the javadoc tool in pre-Java 9 (non-modular) style even if the java version is post java 9. This allows non-JPMS projects that have moved to newer Java versions to create javadocs without having to use JPMS modules.

I would assume we are not planning to move to JPMS module system at platform? If I add the option back the build is working again.

What also would work is using

pom.model.property.javadoc.excludePackageNames = org.eclipse.equinox.internal.p2.jarprocessor.ant

in the build.properties of the projects now failing to exclude package names that are not part of the result (e.g. because embedded as inner jars) but this gives me additional warning

[INFO] --- javadoc:3.11.3:jar (attach-javadocs) @ org.eclipse.equinox.p2.jarprocessor ---
[WARNING] Javadoc 1.4+ doesn't support the -1.1 switch anymore. Ignore this option.
[WARNING] Javadoc Warnings
[WARNING] warning: The code being documented uses modules but the packages defined in https://docs.osgi.org/javadoc/osgi.core/8.0.0/ are in the unnamed module.
[WARNING] 1 warning
[INFO] Building jar: /opt/eclipse/platform-sdk/git/p2/bundles/org.eclipse.equinox.p2.jarprocessor/target/org.eclipse.equinox.p2.jarprocessor-1.3.600-SNAPSHOT-javadoc.jar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants