maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Rohlfs (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MENFORCER-28) Create a rule, which fail when the upper most parent (corporate pom) is not the latest version
Date Thu, 17 Mar 2011 12:11:22 GMT

    [ http://jira.codehaus.org/browse/MENFORCER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=260536#action_260536
] 

Marc Rohlfs commented on MENFORCER-28:
--------------------------------------

We're (also) using a corporate Super POM. To prevent our projects to experience unexpected
side effects (or even broken builds) when changing that Super POM, we're preventing them to
inherit from snapshot versions.
A standard rule to achieve that would be nice, currently we use a Beanshell evaluation:
{code:xml}
<evaluateBeanshell>
  <condition>
    /* The rule shouldn't fail for the Super POM build itself. */
    "${project.parent}".equals("${"+"project.parent"+"}")
    @or
    (
    "${project.parent.artifactId}".equals("corporate-super-pom")
    @and
    !"${project.parent.version}".contains("SNAPSHOT")
    )
  </condition>
  <message>Don't use a SNAPSHOT version of the corporate super POM!</message>
</evaluateBeanshell>
{code}

> Create a rule, which fail when the upper most parent (corporate pom) is not the latest
version
> ----------------------------------------------------------------------------------------------
>
>                 Key: MENFORCER-28
>                 URL: http://jira.codehaus.org/browse/MENFORCER-28
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: New Feature
>          Components: Standard Rules
>            Reporter: Nick Stolwijk
>            Assignee: Brian Fox
>            Priority: Minor
>
> Basic functionality:
> - Should fail if the current project is a SNAPSHOT and there is a newer 
> version of the top most (the corporate pom) artifact. (Don't fail on 
> released versions)
> - Very optional (I can't find a good use case):Option to fail on 
> released versions also.
> - Option to not fail on major changes. (so update from 0.9.1 -> 0.9.2 
> fail, from 0.9.0 to 1.0.0 don't fail)

-- 
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