[ 
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-deprioritized-major auto-unassigned build stale-minor  (was: 
auto-deprioritized-major 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 
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is 
still Minor, 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: Minor
>              Labels: auto-deprioritized-major, auto-unassigned, build, 
> stale-minor
>
> 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.20.10#820010)

Reply via email to