[
https://issues.apache.org/jira/browse/MRESOLVER-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17922211#comment-17922211
]
Matthias Bünger commented on MRESOLVER-456:
-------------------------------------------
{quote}
Unsure how and what you build, but on master just with javadoc:jar I have this:
https://gist.github.com/cstamas/940ce5b63cbd86461e1735e25b0ce9c9
And this is only the first module (api)
{quote}
Hmm what I do is (ofc cmd with admin rights as otherwise builds fails)
{code}
D:\Github\Maven\maven-resolver>git status
On branch master
Your branch is up to date with 'origin/master'.
nothing to commit, working tree clean
D:\Github\Maven\maven-resolver>mvn --version
Apache Maven 4.0.0-rc-2 (273314404f85ec3c089e295d8b4e0cb18c287cf5)
Maven home: C:\apache-maven-4.0.0-rc-2
Java version: 21.0.1, vendor: Eclipse Adoptium, runtime: C:\JDK\Java21
Default locale: de_DE, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
D:\Github\Maven\maven-resolver>mvn clean verify site > ../resolver_log.txt
{code}
https://gist.github.com/Bukama/5115a90783bd10ca463abc1d400db375
A lot of depreacated warnings, but no javadoc issues
> Fix javadoc warnings
> --------------------
>
> Key: MRESOLVER-456
> URL: https://issues.apache.org/jira/browse/MRESOLVER-456
> Project: Maven Resolver
> Issue Type: Task
> Components: Resolver
> Reporter: Tamas Cservenak
> Priority: Major
> Labels: up-for-grabs
> Fix For: 2.0.7
>
>
> We have some warnings, those need to be fixed.
> Given build-time Java is 21, maybe we just want to migrate all to new Javadoc
> style? (as many of warnings are missing returns, that basically redundantly
> doubles the doco)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
