Skip to content

Conversation

@ctubbsii
Copy link
Member

Reduce warnings at the end of the build from using Maven 3.9.2 by updating several plugins whose versions are specified in the parent POM to the latest, which resolves the warnings from Maven. Specifically, update maven-resources-plugin, maven-compiler-plugin, exec-maven-plugin, apilyzer-maven-plugin, maven-dependency-plugin, and maven-enforcer-plugin.

Update some dependency declarations, based on new detections from latest version of maven-dependency-plugin (specifically, zookeeper-jute in minicluster and libthrift in the monitor).

Updating exec-maven-plugin required addressing #3033 with a workaround, and testing the script added for that workaround caught some additional shellcheck issues in the assembly module's cluster management scripts (unreachable redundant exit command) and generate-thrift.sh (unquoted path variable). So those fixes are included here as well.

This fixes #3033.

Reduce warnings at the end of the build from using Maven 3.9.2 by
updating several plugins whose versions are specified in the parent POM
to the latest, which resolves the warnings from Maven. Specifically,
update maven-resources-plugin, maven-compiler-plugin, exec-maven-plugin,
apilyzer-maven-plugin, maven-dependency-plugin, and
maven-enforcer-plugin.

Update some dependency declarations, based on new detections from latest
version of maven-dependency-plugin (specifically, zookeeper-jute in
minicluster and libthrift in the monitor).

Updating exec-maven-plugin required addressing apache#3033 with a workaround,
and testing the script added for that workaround caught some additional
shellcheck issues in the assembly module's cluster management scripts
(unreachable redundant exit command) and generate-thrift.sh (unquoted
path variable). So those fixes are included here as well.

This fixes apache#3033.
@ctubbsii ctubbsii self-assigned this May 25, 2023
@ctubbsii
Copy link
Member Author

Updating apilyzer required me to actually update that project and release a new version of it, which I hadn't done since 2017.

@ctubbsii ctubbsii merged commit 0017fd8 into apache:main May 25, 2023
@ctubbsii ctubbsii deleted the maven-392-updates branch May 25, 2023 19:30
asfgit pushed a commit that referenced this pull request Aug 14, 2023
Reduce warnings at the end of the build from using Maven 3.9.2 by
updating several plugins whose versions are specified in the parent POM
to the latest, which resolves the warnings from Maven. Specifically,
update maven-resources-plugin, maven-compiler-plugin, exec-maven-plugin,
apilyzer-maven-plugin, maven-dependency-plugin, and
maven-enforcer-plugin.

Update some dependency declarations, based on new detections from latest
version of maven-dependency-plugin (specifically, zookeeper-jute in
minicluster and libthrift in the monitor).

Updating exec-maven-plugin required addressing #3033 with a workaround,
and testing the script added for that workaround caught some additional
shellcheck issues in the assembly module's cluster management scripts
(unreachable redundant exit command) and generate-thrift.sh (unquoted
path variable). So those fixes are included here as well.

This fixes #3033.
@ctubbsii
Copy link
Member Author

Backported to 2.1.2 as 4f5d358

@ctubbsii ctubbsii added this to the 2.1.2 milestone Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error upgrading to exec-maven-plugin version 3.1.0

2 participants