You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (JIRA)" <ji...@apache.org> on 2017/07/28 19:44:00 UTC
[jira] [Closed] (FLINK-7281) Fix various issues in (Maven) release
infrastructure
[ https://issues.apache.org/jira/browse/FLINK-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aljoscha Krettek closed FLINK-7281.
-----------------------------------
Resolution: Fixed
Implemented on master in
50a818b1bb74e9442478157bb10c0d5de05ad665
f1c92f2367183d7e215466b3ff227fff11efc470
Implemented on release-1.3 in
62b67876cec0ef13e35eec242a01029899b916b4
b5c9617b41eb38c104ea5c20f15a1f937c591b40
> 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 it
> * 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
(v6.4.14#64029)