[
https://issues.apache.org/jira/browse/FLINK-13855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-13855.
------------------------------------
Fix Version/s: (was: 1.10.0)
Resolution: Won't Fix
Closing this for now as as we aren't gonna touch the Travis infrastructure
anytime soon due to the proposed azure migration.
> Keep Travis build in sync with module structure
> -----------------------------------------------
>
> Key: FLINK-13855
> URL: https://issues.apache.org/jira/browse/FLINK-13855
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Minor
>
> We currently run all Travis profiles with {{-Pinclude-kinesis}} even though
> some of the build profiles don't contain the Kinesis connector module.
> Morever, we run every build profile with {{-Pskip-webui-build}} even though
> {{flink-runtime-web}} is not built by every profile. This causes Maven to log:
> {code}
> 19:15:47.404 [WARNING] The requested profile "skip-webui-build" could not be
> activated because it does not exist.
> 19:15:47.404 [WARNING] The requested profile "include-kinesis" could not be
> activated because it does not exist.
> {code}
> I think it would be good to keep the build on Travis in sync with the actual
> module structure and not specifying options for module where they are
> superfluous. This might prevent the accidental shadowing/inclusion of modules
> if the profiles change in the future.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
