[
http://jira.codehaus.org/browse/MENFORCER-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Rekutin updated MENFORCER-113:
-----------------------------------
Attachment: menforcer113.patch
1-line patch against EnforcerMojo.java. Tested locally, but no integration test
written.
> enforce goal should require dependency collection, not resolution
> -----------------------------------------------------------------
>
> Key: MENFORCER-113
> URL: http://jira.codehaus.org/browse/MENFORCER-113
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 1.0
> Reporter: Oleg Rekutin
> Attachments: menforcer113.patch
>
>
> Enforce goal presently has @requiresDependencyResolution("test"), which
> forces all dependencies to be downloaded for a project at the start of the
> lifecycle (e.g. if the plugin is bounded to initialize). If a project has
> really large dependencies that are resolved on an as-needed basis (e.g. by
> the assembly plugin), inserting the enforcer plugin (e.g. to enforce certain
> properties being set) causes everything to be downloaded.
> The goal should use the new Maven 3.0 requiresDependencyCollection
> annotation, which should be sufficient for all existing rules (banned
> dependencies and such). Any investigation of the contents of the dependencies
> themselves should be an on-demand resolve by the enforcer.
--
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
