flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7281) Fix various issues in (Maven) release infrastructure
Date Fri, 28 Jul 2017 15:56:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105145#comment-16105145

ASF GitHub Bot commented on FLINK-7281:

Github user zentol commented on the issue:

    the changes for FLINK-7281 look good.
    As for FLINK-7290, you didn't adjust the existing release script. Do you intend to delete
it or adjust it to call the module scripts? (There is after all no documentation on how to
use the scripts, like their order)

> Fix various issues in (Maven) release infrastructure
> ----------------------------------------------------
>                 Key: FLINK-7281
>                 URL: https://issues.apache.org/jira/browse/FLINK-7281
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System
>    Affects Versions: 1.3.1, 1.4.0
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Blocker
>             Fix For: 1.4.0, 1.3.2
> I discovered couple of issues while getting ready for release 1.3.2:
> * some old, misleading release scripts and release README
> * the _maven-release-plugin_ is not correctly configured for doing actual releases with
> * the quickstarts are not configured to depend on the project version and thus require
manual updating, also of slf4j and log4j versions
> * the _maven-javadoc-plugin_ configuration does not work when using the the _maven-release-plugin_,
that is we have to move the config to the plugin section and out of the _release_ profile

This message was sent by Atlassian JIRA

View raw message