[jira] Commented: (MENFORCER-29) Enforcer complains about its own version

["Nick Stolwijk (JIRA)" <ji...@codehaus.org>]

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

Nick Stolwijk commented on MENFORCER-29:
----------------------------------------

I've tested this against the current trunk (r669424) and had to change the jar plugin to version 2.2 (from 2.0.2, which could not be found) but then the commands "mvn install" and "mvn compile -Penforce" worked perfectly.

Not reproducible.

> Enforcer complains about its own version
> ----------------------------------------
>
>                 Key: MENFORCER-29
>                 URL: http://jira.codehaus.org/browse/MENFORCER-29
>             Project: Maven 2.x Enforcer Plugin
>          Issue Type: Bug
>          Components: Plugin
>    Affects Versions: 1.0
>         Environment: GNU/Linux
>            Reporter: Hilco Wijbenga
>            Assignee: Brian Fox
>             Fix For: 1.0
>
>         Attachments: pom.xml
>
>
> The attached POM uses the latest version of the Enforcer (revision 611262), i.e. 1.0-SNAPSHOT. I've called it 1.0-Local-1, so that's what's defined in the POM.
> If I use the Enforcer normally, without a profile, everything works beautifully. The attached POM, however, tries to use the Enforcer from a profile ("enforce"). If you now try something like "mvn compile -Penforce" it complains about its own version not being set, even though it's specified *twice*.

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