[ https://issues.apache.org/jira/browse/FLINK-34532 ]


    lincoln lee deleted comment on FLINK-34532:
    -------------------------------------

was (Author: lincoln.86xy):
An error occurred when build from the source package: 
[https://dist.apache.org/repos/dist/dev/flink/flink-1.19.0-rc1/flink-1.19.0-src.tgz]

{code}

[INFO] --- maven-checkstyle-plugin:3.1.2:check (validate) @ 
flink-table-planner_2.12 ---
[WARNING] Old version of checkstyle detected. Consider updating to >= v8.30
[WARNING] For more information see: 
https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/upgrading-checkstyle.html
[INFO] There are 2 errors reported by Checkstyle 8.14 with 
/tools/maven/checkstyle.xml ruleset.
[ERROR] 
src/main/scala/org/apache/flink/table/planner/plan/rules/logical/RemoteCalcCallFinder.java:[31]
 (whitespace) EmptyLineSeparator: 'METHOD_DEF' should be separated from 
previous statement.
[ERROR] 
src/main/scala/org/apache/flink/table/planner/plan/rules/logical/RemoteCalcCallFinder.java:[33]
 (whitespace) EmptyLineSeparator: 'METHOD_DEF' should be separated from 
previous statement.

...

[INFO] Flink : Table : Planner ............................ FAILURE [03:37 min]

...

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  16:45 min
[INFO] Finished at: 2024-03-05T23:10:46+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-checkstyle-plugin:3.1.2:check (validate) on 
project flink-table-planner_2.12: You have 2 Checkstyle violations. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :flink-table-planner_2.12

{code}

 

> Stage source and binary releases on dist.apache.org
> ---------------------------------------------------
>
>                 Key: FLINK-34532
>                 URL: https://issues.apache.org/jira/browse/FLINK-34532
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Lincoln Lee
>            Assignee: lincoln lee
>            Priority: Major
>
> Copy the source release to the dev repository of dist.apache.org:
> # If you have not already, check out the Flink section of the dev repository 
> on dist.apache.org via Subversion. In a fresh directory:
> {code:bash}
> $ svn checkout https://dist.apache.org/repos/dist/dev/flink --depth=immediates
> {code}
> # Make a directory for the new release and copy all the artifacts (Flink 
> source/binary distributions, hashes, GPG signatures and the python 
> subdirectory) into that newly created directory:
> {code:bash}
> $ mkdir flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> $ mv <flink-dir>/tools/releasing/release/* 
> flink/flink-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
> # Add and commit all the files.
> {code:bash}
> $ cd flink
> flink $ svn add flink-${RELEASE_VERSION}-rc${RC_NUM}
> flink $ svn commit -m "Add flink-${RELEASE_VERSION}-rc${RC_NUM}"
> {code}
> # Verify that files are present under 
> [https://dist.apache.org/repos/dist/dev/flink|https://dist.apache.org/repos/dist/dev/flink].
> # Push the release tag if not done already (the following command assumes to 
> be called from within the apache/flink checkout):
> {code:bash}
> $ git push <remote> refs/tags/release-${RELEASE_VERSION}-rc${RC_NUM}
> {code}
>  
> ----
> h3. Expectations
>  * Maven artifacts deployed to the staging repository of 
> [repository.apache.org|https://repository.apache.org/content/repositories/]
>  * Source distribution deployed to the dev repository of 
> [dist.apache.org|https://dist.apache.org/repos/dist/dev/flink/]
>  * Check hashes (e.g. shasum -c *.sha512)
>  * Check signatures (e.g. {{{}gpg --verify 
> flink-1.2.3-source-release.tar.gz.asc flink-1.2.3-source-release.tar.gz{}}})
>  * {{grep}} for legal headers in each file.
>  * If time allows check the NOTICE files of the modules whose dependencies 
> have been changed in this release in advance, since the license issues from 
> time to time pop up during voting. See [Verifying a Flink 
> Release|https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release]
>  "Checking License" section.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to