streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STREAMS-174) Snapshot dependencies in the project poms
Date Tue, 16 Sep 2014 19:09:34 GMT

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

ASF GitHub Bot commented on STREAMS-174:
----------------------------------------

Github user steveblackmon commented on the pull request:

    https://github.com/apache/incubator-streams/pull/87#issuecomment-55796918
  
    +1


> 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