[
https://issues.apache.org/jira/browse/DRILL-8378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Turton updated DRILL-8378:
--------------------------------
Description:
While DRILL-8113 enabled the building of Drill using a modern JDK, more work is
required to enable a Maven release of Drill using a modern JDK. Presently, the
Maven Release Plugin will fail on Javadoc generation when run with a newer JDK
while it succeeds with JDK 8. The failures are due to dependencies missing from
the Maven Javadoc Plugin's config which I assume get treated with a more
lenient "skip" policy in the javadoc tool shipped with JDK 8 but cause errors
in newer JDKs (in my case OpenJDK 17).
DRILL-6637 removed dependencies on Drill artifacts from the Maven Javadoc
Plugin's config but this Jira proposes to reinstate them because their absence
prevents releasing using a modern JDK. As is reported in DRILL-6637, when
performing a release said artifacts are not present in any known repo with the
new version number so this Jira proposes additional logic in the release script
to install the artifacts locally just before the release.
was:
While DRILL-8113 enabled the building of Drill using a modern JDK, more work is
required to enable a Maven release of Drill using a modern JDK. Presently, the
Maven Release Plugin will fail on Javadoc generation when run with a newer JDK
while it succeeds with JDK 8. The failures are due to dependencies missing from
the Maven Javadoc Plugin's config which I assume get treated with a more
lenient "skip" policy in the javadoc tool shipped with JDK 8 but cause errors
in newer JDKs (in my case OpenJDK 17).
DRILL-6637 removed dependencies on Drill artifacts from the Maven Javadoc
Plugin's config but this Jira proposes to reinstate them because their absence
prevents releasing using a modern JDK. When performing a release, said
artifacts are not present in any known repo with the new version number so this
Jira proposes additional logic in the release script to install the artefacts
locally just before the release.
> Support doing Maven releases using modern JDKs
> ----------------------------------------------
>
> Key: DRILL-8378
> URL: https://issues.apache.org/jira/browse/DRILL-8378
> Project: Apache Drill
> Issue Type: Improvement
> Components: Tools, Build & Test
> Affects Versions: 1.20.2
> Reporter: James Turton
> Assignee: James Turton
> Priority: Minor
> Fix For: 1.21.0
>
>
> While DRILL-8113 enabled the building of Drill using a modern JDK, more work
> is required to enable a Maven release of Drill using a modern JDK. Presently,
> the Maven Release Plugin will fail on Javadoc generation when run with a
> newer JDK while it succeeds with JDK 8. The failures are due to dependencies
> missing from the Maven Javadoc Plugin's config which I assume get treated
> with a more lenient "skip" policy in the javadoc tool shipped with JDK 8 but
> cause errors in newer JDKs (in my case OpenJDK 17).
> DRILL-6637 removed dependencies on Drill artifacts from the Maven Javadoc
> Plugin's config but this Jira proposes to reinstate them because their
> absence prevents releasing using a modern JDK. As is reported in DRILL-6637,
> when performing a release said artifacts are not present in any known repo
> with the new version number so this Jira proposes additional logic in the
> release script to install the artifacts locally just before the release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
