Mailing-List: contact dev-help@streams.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@streams.incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of m.ben.franklin@gmail.com
 designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAHduaq3i-=snH1=vx67WhP8oVsLO8WYQfK0R543VoAkWrb98hw@mail.gmail.com>
References: 
 <CAHduaq3i-=snH1=vx67WhP8oVsLO8WYQfK0R543VoAkWrb98hw@mail.gmail.com>
Date: Tue, 16 Sep 2014 13:06:35 -0400
Message-ID: 
 <CAENpzYX=trqXCWq4D0MvNJROJCD+87pkRRtCs+wP_pUPpU8sJg@mail.gmail.com>
Subject: Re: SNAPSHOT version dependencies
From: Matt Franklin <m.ben.franklin@gmail.com>
To: "dev@streams.incubator.apache.org" <dev@streams.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a11c223f41f9510050331c693

--001a11c223f41f9510050331c693
Content-Type: text/plain; charset=UTF-8

On Tue, Sep 16, 2014 at 1:05 PM, Stanton Sievers <ssievers@apache.org>
wrote:

> Hi everyone,
>
> I'm looking through the streams code base and I've noticed some
> dependencies on SNAPSHOT resources in a few places.  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.
>
> The few instances I've noticed are in the google-gmail,
> streams-persist-hbase, and streams-persist-hdfs modules.  The
> streams-master parent version is also a snapshot currently.
>
> If no one objects to the general idea of not having SNAPSHOT dependencies,
> I'll get a pull request up that fixes the versions in these 4 places.
>

Sounds like a great idea.


>
> Additionally, this project can make use of the maven-enforcer-plugin to
> ensure that no snapshots are used as part of project policy.
>

+1


>
> Thanks,
> -Stanton
>

--001a11c223f41f9510050331c693--