NIFI-10616 Resolve Reproducible ANTLR3 and JAXB Build Issues

[hboutemy]

Summary

NIFI-10616

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using mvn clean install -P contrib-check
  • JDK 8
  • JDK 11
  • JDK 17

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks for the contribution @hboutemy!

It looks like discussion is still going on regarding the ANTLR3 issue 209. The maven-replacer-plugin approach makes sense, but it seems that the plugin is not actively maintained, which is somewhat concerning.

What do you think about scoping the current changes to the JAXB2 configuration, and waiting for a resolution on the ANTLR3 issue for now?

[hboutemy]

waiting for ANTLR3 upstream solution seems to take ages: I don't think it's worth waiting for it

[exceptionfactory]

Thanks for the reply @hboutemy, based on the status of ANTLR 3 antlr/antlr3#209, moving forward with this solution looks good for now.