You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/10/13 10:07:30 UTC

[GitHub] [flink] rmetzger commented on pull request #13599: [FLINK-19459] Run certain maven-enforcer-plugin executions only in release profile

rmetzger commented on pull request #13599:
URL: https://github.com/apache/flink/pull/13599#issuecomment-707637050


   How about introducing a profile that activates automatically if the maven version is 3.2x? Then it would run on CI, in the release profile and in proper local setups? (I could add a comment that people need to use maven 3.2.5 for this ban to be active. That should be sufficient for tracing back the issue from a CI failure to reproducing it locally?)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org