[
https://issues.apache.org/jira/browse/FLINK-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474258#comment-16474258
]
Yazdan Shirvany commented on FLINK-1044:
----------------------------------------
[~StephanEwen]
here is a suggestion:
* Create a submodule in the project (e.g.,
flink-examples/flink-sample-project) which using ${project.version} for basic
flink dependencies
* Build this submodule with all dependencies included in .jar
* Add script to after_script in .travis.yml to push
flink-examples/flink-sample-project/target/*.jar file for this submodule to the
S3 (or any other location that flink keeps this type of assets)
* Point the document to this new artifact location via params coordinated with
${projcet.version}
To make this work for each merged PR, we need to point this submodule to
internal repos where the flink pushes packages after each build (if any)
There might be complexity in this approach also as I am not familiar with CICD
pipeline for the project and what is the process to make this submodule package
public facing.
> Website: Offer a zip archive with a pre-setup user project
> ----------------------------------------------------------
>
> Key: FLINK-1044
> URL: https://issues.apache.org/jira/browse/FLINK-1044
> Project: Flink
> Issue Type: Improvement
> Components: Project Website
> Reporter: Stephan Ewen
> Priority: Minor
> Labels: starter
> Attachments: flink-project.zip
>
>
> This is basically a shortcut for those that are not familiar with maven
> archetypes or do not have maven installed (other then as part of the Eclipse
> IDE or so).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
