apache / apache/maven-javadoc-plugin
fixed snapshot versions are ignored and latest snapshot is used instead
- Dominant language
- Java
- Stars
- 107
- Forks
- 116
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 16
Description
### Affected version
3.11.2
### Bug description
We use fixed snapshot versions, when we reference dependencies. Now we get compile issues that looks like this if I execute `mvn site:site site:stage`
```
Error: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:4.0.0-M16:site (default-cli) on project request: Error generating maven-javadoc-plugin:3.11.2:aggregate-no-fork report:
Error: Exit code: 1
Error: /home/runner/work/ReBuild/ReBuild/ReQuest/src/main/java/works/reload/request/dialog/InventoryHandler.java:11: error: cannot find symbol
Error: import org.betonquest.betonquest.util.LocalChatPaginator;
Error: ^
Error: symbol: class LocalChatPaginator
Error: location: package org.betonquest.betonquest.util
Error: [ERROR] 1 error
Error: Command line was: /usr/lib/jvm/temurin-21-jdk-amd64/bin/javadoc -J-Duser.language= -J-Duser.country= @options @packages
```
If I look up the log output, I can find that the latest snapshot version was downloaded and is now used, instead of the fixed version we actually reference, and there where braking changes, so we get this compile issue.
We had a similar issue some time ago: https://github.com/apache/maven-project-info-reports-plugin/issues/582
Now I think that booth use maybe the same library to manage the versions.
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the problem with `mvn site:site site:stage` using the fixed snapshot dependency versions described in the issue. Compare the resolved version with the referenced fixed version and review the related maven-project-info-reports-plugin issue for context on the shared version-management library. Done means the fixed snapshot remains selected and site generation no longer uses the latest snapshot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100