You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@apache.org> on 2017/06/22 19:54:00 UTC

[jira] [Updated] (MENFORCER-204) Add new rule: should be able to make sure that project artifact is a Snapshot

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

Stephen Connolly updated MENFORCER-204:
---------------------------------------
    Fix Version/s: 3.0.0

> Add new rule: should be able to make sure that project artifact is a Snapshot
> -----------------------------------------------------------------------------
>
>                 Key: MENFORCER-204
>                 URL: https://issues.apache.org/jira/browse/MENFORCER-204
>             Project: Maven Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>    Affects Versions: 1.4.1
>            Reporter: Adrien Lecharpentier
>            Assignee: Guillaume Boué
>             Fix For: 1.4.2, 3.0.0
>
>         Attachments: MENFORCER-RequireSnapshotVersion.patch
>
>
> As it is currently possible to validate the current project is a release, we should have to inverse rule: validate the current project is a snapshot.
> The use case: in CI, ensure that the current project is in snapshot version before doing a `mvn deploy`. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)