[
https://issues.apache.org/jira/browse/FLINK-15832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-15832:
-----------------------------------
Labels: auto-unassigned build stale-major (was: auto-unassigned build)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Major
> Labels: auto-unassigned, build, stale-major
>
> 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)
