maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (Jira)" <>
Subject [jira] [Commented] (MRELEASE-1036) fix javadoc for JDK 8
Date Thu, 09 Jan 2020 08:01:00 GMT


Herve Boutemy commented on MRELEASE-1036:

[~cchacin] thank you for your help, I'll review the PR shortly
I updated the issue description:
- TLDR: the context is that it's currently impossible to release the plugin with JDK 8, because
the release process ({{mvn -Papache-release verify}}) generates javadoc then fail
- more in-depth: I personnally have JDK 7 installed on my computer, then it's not completely
an issue, I can release (I did a few weeks ago). But for Reproducible Builds, it means everybody
who wants to check the reference build will require JDK 7, which is not a requirement that
is easy for everybody on a modern computer

sadly, we can't assign issues to people outside committers: the discussion here at least avoid
duplicate parallel work from someone else...

> fix javadoc for JDK 8
> ---------------------
>                 Key: MRELEASE-1036
>                 URL:
>             Project: Maven Release Plugin
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 3.0.0-M1
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>            Priority: Major
>              Labels: up-for-grabs
>             Fix For: 3.0.0
>          Time Spent: 10m
>  Remaining Estimate: 0h
> When running {{mvn verify site -Preporting}} with JDK 8, the project fails due to javadoc
errors: this makes releasing the release plugin with JDK 8 impossible.
> Notice that you might also see stacktraces caused by {{org.eclipse.aether.transfer.ArtifactNotFoundException:
Failure to find org.eclipse.m2e:lifecycle-mapping:pom:1.0.0}}: these one can be ignored because
they are only warning (not a blocker) and will be fixed with MPIR-375 once released.

This message was sent by Atlassian Jira

View raw message