[
https://issues.apache.org/jira/browse/FLINK-15832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17436733#comment-17436733
]
Fei Feng commented on FLINK-15832:
----------------------------------
share a workaround:
# test `mvn package` to know if your code compile and package correctly or not
# if build success，run `mvn deploy` with `--fail-never`, to ignore this
error
it works but a little dangerous.
> Test jars are installed twice
> -----------------------------
>
> Key: FLINK-15832
> URL: https://issues.apache.org/jira/browse/FLINK-15832
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 1.9.1
> Reporter: static-max
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, build
>
> I built Flink 1.9.1 myself and merged the changes from
> [https://github.com/apache/flink/pull/10936].
> When I uploaded the artifacts to our repository (using {{mvn deploy }}
> {{-DaltDeploymentRepository}}) the build fails as
> {{flink-metrics-core-tests}} will be uploaded twice and we have redeployments
> disabled.
>
> I'm not sure if other artifacts are affected as well, as I enabled
> redeployment as a quick workaround.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
