[
http://jira.codehaus.org/browse/MNG-4271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-4271.
---------------------------
Resolution: Won't Fix
This is solved in Maven 3.x, but isn't really feasible in 2.x. The reason is
the wonky ordering of operations during project-loading...the import-scoped
dependencies in dependencyManagement are replaced with their
dependencyManagement section before they can be validated, which removes
basically all traces from the model. So, validation would need to be moved up
in the ordering, which would mean that other dependencies which rely on the
imported POM info for completion would be invalid.
Another chicken-and-egg scenario, brought to you by Maven 2.x.
> Validate type == POM and classifier == (empty) when scope == import, and
> scope != import in project/dependencies
> ----------------------------------------------------------------------------------------------------------------
>
> Key: MNG-4271
> URL: http://jira.codehaus.org/browse/MNG-4271
> Project: Maven 2
> Issue Type: Improvement
> Components: POM
> Affects Versions: 2.2.0
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.2.1
>
>
> Adding some simple validations to make import scope more intuitive for users.
> These validation rules are already in place in maven 3.x code, and are dead
> simple to add here as well.
--
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
