[
https://issues.apache.org/jira/browse/SLING-3286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848974#comment-13848974
]
Felix Meschberger commented on SLING-3286:
------------------------------------------
bq. However of course, I don't see any use case, where you want a package in
both lists...so I guess I new issue is a good idea
While there probably is no practical use case for having both (mandatory)
static and dynamic imports, there are explanations for having optional static
and dynamic imports at the same time: The resolver is allowed to eagerly
resolve a dependency which might give some performance improvement.
> Remove plugin version overrides from poms
> -----------------------------------------
>
> Key: SLING-3286
> URL: https://issues.apache.org/jira/browse/SLING-3286
> Project: Sling
> Issue Type: Task
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
>
> Multiple modules specify their own versions instead of picking up the one
> from the parent pom. For consistency and for making sure that we always get
> the upgrades, all these modules should have the same versions.
> Situations where this isn't possible should be clearly documented in the pom.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
