You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Sievers (JIRA)" <ji...@codehaus.org> on 2010/04/01 15:15:22 UTC
[jira] Created: (MENFORCER-93) [maven 3.x] configuration not
recognized on level
[maven 3.x] configuration not recognized on <executions> level
--------------------------------------------------------------
Key: MENFORCER-93
URL: http://jira.codehaus.org/browse/MENFORCER-93
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Affects Versions: 1.0-beta-1
Environment: maven 3.0-alpha-7, enforcer plugin 1.0-beta-1
Reporter: Jan Sievers
Attachments: testcases.zip
I tried the example snippet from
http://maven.apache.org/plugins/maven-enforcer-plugin/usage.html
with enforcer plugin 1.0-beta-1 and maven 3.0-alpha-7.
It seems the enforcer configuration is only recognized if moved up to the <plugin> level.
<configuration> under <execution> is ignored. The plugin complains that no rules are configured.
This may be a general maven 3 bug ...
See example poms attached for reproducing the problem and an alternative pom with configuration on plugin level which works.
Also includes
mvn enforcer:enforce -X -e
output.
Regards
Jan
--
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
[jira] Closed: (MENFORCER-93) [maven 3.x] configuration not
recognized on level
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MENFORCER-93.
--------------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
As documented in [Guide to Configuring Plug-ins|http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag], execution-level configuration does only apply for the particular execution and not a direct invocation of a goal from the CLI. Recent Maven versions recognize a special execution id for CLI executions as documented in [Guide to Configuring Default Mojo Executions|http://maven.apache.org/guides/mini/guide-default-execution-ids.html].
> [maven 3.x] configuration not recognized on <executions> level
> --------------------------------------------------------------
>
> Key: MENFORCER-93
> URL: http://jira.codehaus.org/browse/MENFORCER-93
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Affects Versions: 1.0-beta-1
> Environment: maven 3.0-alpha-7, enforcer plugin 1.0-beta-1
> Reporter: Jan Sievers
> Assignee: Benjamin Bentmann
> Attachments: testcases.zip
>
>
> I tried the example snippet from
> http://maven.apache.org/plugins/maven-enforcer-plugin/usage.html
> with enforcer plugin 1.0-beta-1 and maven 3.0-alpha-7.
> It seems the enforcer configuration is only recognized if moved up to the <plugin> level.
> <configuration> under <execution> is ignored. The plugin complains that no rules are configured.
> This may be a general maven 3 bug ...
> See example poms attached for reproducing the problem and an alternative pom with configuration on plugin level which works.
> Also includes
> mvn enforcer:enforce -X -e
> output.
> Regards
> Jan
--
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