streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (STREAMS-174) Snapshot dependencies in the project poms
Date Tue, 16 Sep 2014 18:58:35 GMT


ASF GitHub Bot commented on STREAMS-174:

GitHub user sieverssj opened a pull request:

     STREAMS-174 | Fix snapshot dependencies in the project poms

    The google4j behavior had to change because the mechanism to fetch all e-mails since the
2000 was introduced in 0.5-SNAPSHOT version. Because this is more of a sample task to illustrate
how e-mails may be fetched from gmail, I think this is OK.

You can merge this pull request into a Git repository by running:

    $ git pull STREAMS-174

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #87
commit 98c44efae2ca4f9b306b40e440531050d31071f6
Author: Stanton Sievers <>
Date:   2014-09-16T18:53:11Z

    STREAMS-174 | Lock the parent pom to the 0.1-incubating version

commit 006190a56fffb0ddeb9149f6ccd0915243e1a8e0
Author: Stanton Sievers <>
Date:   2014-09-16T18:53:28Z

    STREAMS-174 | Remove an unused property that refers to a SNAPSHOT version

commit 0759b49237e293b92812f31b389a13b5c3cc68c6
Author: Stanton Sievers <>
Date:   2014-09-16T18:53:51Z

    STREAMS-174 | Converge HDFS to the release version

commit 5c76c1742ae9f0b5fcf97633797a13d902d544a0
Author: Stanton Sievers <>
Date:   2014-09-16T18:54:26Z

    STREAMS-174 | Change google4j to the latest release and update the mechanism for fetching
e-mails to a mechanism supported in that release

commit 09a2995e20629c9298702977361b5b8e7e6acca3
Author: Stanton Sievers <>
Date:   2014-09-16T18:55:42Z

    STREAMS-174 | Use the maven-enforcer-plugin to fail builds if snapshot dependencies are


> Snapshot dependencies in the project poms
> -----------------------------------------
>                 Key: STREAMS-174
>                 URL:
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Stanton Sievers
> From a release standpoint this is generally frowned upon because functionality can change
over time without changes in the code base simply because a newer SNAPSHOT dependency was
pulled in.  In fact, it is the default behavior of the maven release plugin to fail a build
if SNAPSHOT dependencies are detected.
> These SNAPSHOT dependencies should be converted to using release versions.  It would
also be good to introduce a maven-enforcer-plugin rule to enforce no snapshot versions as
a project policy.

This message was sent by Atlassian JIRA

View raw message