[
http://jira.codehaus.org/browse/MENFORCER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian Fox updated MENFORCER-29:
-------------------------------
Fix Version/s: 1.0
> 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