[
https://issues.apache.org/jira/browse/BEAM-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264100#comment-15264100
]
ASF GitHub Bot commented on BEAM-154:
-------------------------------------
GitHub user jbonofre opened a pull request:
https://github.com/apache/incubator-beam/pull/267
[BEAM-154] Use dependencyManagement and pluginManagement to keep all …
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:
- [X] Make sure the PR title is formatted like:
`[BEAM-<Jira issue #>] Description of pull request`
- [X] Make sure tests pass via `mvn clean verify`. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
- [X] Replace `<Jira issue #>` in the title with the actual Jira issue
number, if there is one.
- [X] If this contribution is large, please file an Apache
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.txt).
---
Use of dependencyManagement and pluginManagement to align versions between
modules.
There's checkstyle errors in several modules, I will fix in new commits.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jbonofre/incubator-beam DEPMANAGEMENT
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/267.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #267
----
commit 2b174b1bf5e18e1e20b09a4e029750f8ad9ca95d
Author: Jean-Baptiste Onofré <jbono...@apache.org>
Date: 2016-04-29T13:26:01Z
[BEAM-154] Use dependencyManagement and pluginManagement to keep all
modules sync in term of version
----
> 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)
