[jira] Commented: (MNG-4293) Extend Mojo API to allow resolution of both compile and runtime dependencies
[
http://jira.codehaus.org/browse/MNG-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186924#action_186924
]
Paul Benedict commented on MNG-4293:
Too bad the inverse is not supported. With source annotation processors, they
only need compile scope but not runtime scope.
Extend Mojo API to allow resolution of both compile and runtime dependencies
Key: MNG-4293
URL: http://jira.codehaus.org/browse/MNG-4293
Project: Maven 2
Issue Type: Improvement
Components: Plugin API, Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: Benjamin Bentmann
Assignee: Benjamin Bentmann
Priority: Minor
Fix For: 3.0-alpha-3
Right now, only {...@requiresdependencyresolution compile|runtime|test}} is
supported. However, {{runtime}} is no superset of {{compile}} but plugins
occasionally need both scopes. To better support those use cases, a new
resolution scope {{compile+runtime}} will be introduced. See also
[\[DISCUSS\] Extend Mojo API to allow for resolution of multiple dependency
scopes|http://markmail.org/message/2z4vlqhxm6qb4owk]
--
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] Commented: (MNG-4293) Extend Mojo API to allow resolution of both compile and runtime dependencies
[
http://jira.codehaus.org/browse/MNG-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186925#action_186925
]
Benjamin Bentmann commented on MNG-4293:
The inverse of the new scope compile+runtime would be test-only, so I don't
get how that fits together with your statement about needing only compile
scope. Those goals can already use {...@requiresdependencyresolution compile}}.
Extend Mojo API to allow resolution of both compile and runtime dependencies
Key: MNG-4293
URL: http://jira.codehaus.org/browse/MNG-4293
Project: Maven 2
Issue Type: Improvement
Components: Plugin API, Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: Benjamin Bentmann
Assignee: Benjamin Bentmann
Priority: Minor
Fix For: 3.0-alpha-3
Right now, only {...@requiresdependencyresolution compile|runtime|test}} is
supported. However, {{runtime}} is no superset of {{compile}} but plugins
occasionally need both scopes. To better support those use cases, a new
resolution scope {{compile+runtime}} will be introduced. See also
[\[DISCUSS\] Extend Mojo API to allow for resolution of multiple dependency
scopes|http://markmail.org/message/2z4vlqhxm6qb4owk]
--
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] Commented: (MNG-4293) Extend Mojo API to allow resolution of both compile and runtime dependencies
[
http://jira.codehaus.org/browse/MNG-4293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=186981#action_186981
]
Paul Benedict commented on MNG-4293:
I misspoke. It's actually a problem for the package phase (or for MWAR). Right
now, the assumption is that all dependencies of compile scope are also
necessary for packaging. That's not necessarily correct. If a library is only
need for compile scope (such as annotation processor), it gets bundled into
WEB-INF/lib. While not necessarily directly related to this ticket, a new
possible scope would be great for this purpose. Is it simply a matter of
packaging exclusion or is it really another scope?
By the way, I know a plus-sign can have the same semantics as a comma (i.e.,
logical or), but if you used the comma it could leave room for future
expansion. Maybe one day users could configure any combination of scopes.
Specifying compile,runtime seems like the natural path, imo.
Extend Mojo API to allow resolution of both compile and runtime dependencies
Key: MNG-4293
URL: http://jira.codehaus.org/browse/MNG-4293
Project: Maven 2
Issue Type: Improvement
Components: Plugin API, Plugins and Lifecycle
Affects Versions: 2.0.10
Reporter: Benjamin Bentmann
Assignee: Benjamin Bentmann
Priority: Minor
Fix For: 3.0-alpha-3
Right now, only {...@requiresdependencyresolution compile|runtime|test}} is
supported. However, {{runtime}} is no superset of {{compile}} but plugins
occasionally need both scopes. To better support those use cases, a new
resolution scope {{compile+runtime}} will be introduced. See also
[\[DISCUSS\] Extend Mojo API to allow for resolution of multiple dependency
scopes|http://markmail.org/message/2z4vlqhxm6qb4owk]
--
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
