[ https://issues.apache.org/jira/browse/FLINK-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104836#comment-16104836 ]
ASF GitHub Bot commented on FLINK-7281: --------------------------------------- Github user aljoscha commented on the issue: https://github.com/apache/flink/pull/4407 @zentol I will remove some changes from this so that only the Quickstart changes remain and the removal of the old release script and README. I think using `maven-release-plugin` is currently not a good option so I will leave that as is. What do you think? > 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)