You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/27 09:05:00 UTC
[jira] [Commented] (FLINK-7281) Fix various issues in (Maven)
release infrastructure
[ https://issues.apache.org/jira/browse/FLINK-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16102972#comment-16102972 ]
ASF GitHub Bot commented on FLINK-7281:
---------------------------------------
GitHub user aljoscha opened a pull request:
https://github.com/apache/flink/pull/4407
[FLINK-7281] Fix various issues in (Maven) release infrastructure
## What is the purpose of the change
Fix various issues in the release infrastructure and Maven.
## Brief change log
* remove old, misleading release scripts and release README
* configure the _maven-release-plugin_ for doing actual releases with it
* make the quickstarts depend on project versions
* configure _maven-javadoc-plugin_ to work with _maven-release-plugin_ (doc linting was not disabled)
## Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
## Does this pull request potentially affect one of the following parts:
no
## Documentation
- Does this pull request introduce a new feature? (no)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aljoscha/flink release-1.3
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4407.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4407
----
commit b37c29feb3814969031b573bc73dcd09c807744f
Author: Aljoscha Krettek <al...@gmail.com>
Date: 2017-07-25T13:07:59Z
[FLINK-7281] Remove old and misleading release scripts/README
commit 6d6b5289de72016ea65a4f869cda3ef58a26a5d4
Author: Aljoscha Krettek <al...@gmail.com>
Date: 2017-07-25T13:30:26Z
[FLINK-7281] Make quickstart versions depend on project versions
commit ded58c9bf0a21e5205d514e010b515b1ef1e7f2f
Author: Aljoscha Krettek <al...@gmail.com>
Date: 2017-07-25T13:30:42Z
[FLINK-7281] Bump maven-release-plugin version and make it work
commit 1a5cecab8f91cadbdd86c6194ef6276f1cc5df83
Author: Aljoscha Krettek <al...@gmail.com>
Date: 2017-07-26T10:10:15Z
[FLINK-7281] Move maven-javadoc-config out of execution blocks
commit 085852028837cf9d7835a6120385ea665e8510e3
Author: Aljoscha Krettek <al...@gmail.com>
Date: 2017-07-26T12:19:49Z
[FLINK-7281] Move maven-release-plugin out of release profile
----
> 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)