[
https://issues.apache.org/jira/browse/ONAMI-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618032#comment-13618032
]
Mikhail Mazursky commented on ONAMI-98:
---------------------------------------
Point 1: let us leave "provided" as is - if some Onami user face any problems
with this we can always re-open this issue and start discussion;
Point 3: removed "compile" scope and "jar" type in r1462724;
Point 4: it's not so easy to do that unless we use single versioned modules
tree. I mean currently we have to add those dependencies to dep. management in
parent, release the parent, change parent version in all modules and only then
remove versions. WDYT?
> Improve dependency management
> -----------------------------
>
> Key: ONAMI-98
> URL: https://issues.apache.org/jira/browse/ONAMI-98
> Project: Apache Onami
> Issue Type: Improvement
> Components: parent
> Affects Versions: parent-3
> Reporter: Mikhail Mazursky
> Priority: Minor
>
> - Why Guice have "provided" scope in dep. management? I think it should be
> "compile".
> - We can set scope for JUnit, TestNg dependencies to be "test" to avoid
> setting it in each module.
> - We may want to remove explicit "compile" scope and "jar" type from all
> dependencies from all modules because they are defaults. Less noise in poms.
> - Manage all dependencies' versions from parent dependency management to
> ensure consistent versions and easy maintenance.
> WDYT?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
