streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Ebanks (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (STREAMS-174) Snapshot dependencies in the project poms
Date Tue, 21 Oct 2014 14:45:34 GMT

     [ https://issues.apache.org/jira/browse/STREAMS-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ryan Ebanks resolved STREAMS-174.
---------------------------------
    Resolution: Fixed

> Snapshot dependencies in the project poms
> -----------------------------------------
>
>                 Key: STREAMS-174
>                 URL: https://issues.apache.org/jira/browse/STREAMS-174
>             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
(v6.3.4#6332)

Mime
View raw message