maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Lidgey (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MENFORCER-22) create a rule to check the current project is not a snapshot
Date Mon, 11 Feb 2008 14:30:29 GMT

    [ http://jira.codehaus.org/browse/MENFORCER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123269
] 

Ben Lidgey commented on MENFORCER-22:
-------------------------------------

We have the scenario where developers use a SNAPSHOT version for the project during development,
and depend on other SNAPSHOT artifacts which is fine. We want this setup to pass the build
in the CI server.

BUT, when the project version becomes a non-SNAPSHOT version then we want the check to ensure
that no dependencies are SNAPSHOTs.

Something like:

|| || Dependency versions || ||
|| || SNAPSHOT || non-SNAPSHOT ||
|| Project version || | |
|| SNAPSHOT | pass | pass |
|| non-SNAPSHOT | fail | pass |

> create a rule to check the current project is not a snapshot
> ------------------------------------------------------------
>
>                 Key: MENFORCER-22
>                 URL: http://jira.codehaus.org/browse/MENFORCER-22
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>    Affects Versions: 1.0-alpha-3
>            Reporter: Brian Fox
>            Assignee: Brian Fox
>             Fix For: 1.0
>
>
> There is already a rule to check that dependencies cannot be a snapshot, create a rule
to ensure the current project is not a snapshot.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message