You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2018/01/19 15:29:01 UTC

[jira] [Commented] (BEAM-3440) Generic IOIT profiles configuration in io's parent pom.xml

    [ https://issues.apache.org/jira/browse/BEAM-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332396#comment-16332396 ] 

Kenneth Knowles commented on BEAM-3440:
---------------------------------------

Since we are moving to Gradle, perhaps this can be rephrased in those terms. It is probably best to have shared groovy snippets rather than inheritance, since inheritance can be quite hard to follow.

> Generic IOIT profiles configuration in io's parent pom.xml
> ----------------------------------------------------------
>
>                 Key: BEAM-3440
>                 URL: https://issues.apache.org/jira/browse/BEAM-3440
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Łukasz Gajowy
>            Assignee: Kenneth Knowles
>            Priority: Major
>
> Currently developing IOITs requires copying maven profile configuration to every's IO pom for profiles like: io-it-suite, runner profiles etc. This can be avoided by moving all the common profiles to sdks/java/io/pom.xml parent pom and leave only some test specific argument settings in concrete child modules. This can be done using maven properties (<properties> section in appropriate child pom's profile section). This would reduce lots of xml code duplication.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)