You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2016/04/11 19:28:25 UTC

[jira] [Commented] (BEAM-154) Provide Maven BOM

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

Jean-Baptiste Onofré commented on BEAM-154:
-------------------------------------------

Related to that, most of the Beam modules pom.xml defines (and redefines) plugin configuration and version, and also dependencies version (for instance junit and hamcrest).
In order to simplify and align all pom files, the master parent pom should define pluginManagement and dependencyManagement, reused in all other child pom.

> Provide Maven BOM
> -----------------
>
>                 Key: BEAM-154
>                 URL: https://issues.apache.org/jira/browse/BEAM-154
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> When using the Java SDK (for instance to develop IO), the developer has to add dependencies in his pom.xml (like junit, hamcrest, slf4j, ...).
> To simplify the way to define the dependencies, each Beam SDK could provide a Maven BoM (Bill of Material) describing these dependencies. Then the developer could simply define this BoM as pom.xml dependency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)