[ 
https://issues.apache.org/jira/browse/ONAMI-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591688#comment-13591688
 ] 

Simone Tripodi commented on ONAMI-98:
-------------------------------------

(unfortunately, we cannot quote text until someone helps me to enable the wiki 
markup text, which is a configuration hell for me :D)

>From Maven documentation you pointed:

"provided
This is much like compile, but indicates you expect the JDK or a container to 
provide the dependency at runtime. For example, when building a web application 
for the Java Enterprise Edition, you would set the dependency on the Servlet 
API and related Java EE APIs to scope provided because the web container 
provides those classes. This scope is only available on the compilation and 
test classpath, and is not transitive."

It says "indicates you expect the JDK or a container to provide the dependency 
at runtime".
Onami modules are Guice extensions and users that intend to use Onami-XXX must 
have to depend to Guice already. Can whatever Onami extension be used without 
Guice? No. :)

OTOH, Onami-Test: follows the inverse logic: it aims to become the unit tests 
container, with its own runner and its own extension, that is why scopes 
changed there.

+1 to put slf4j-api in dependencyManagement in parent, guess [scheduler] and 
[logging] there wont' be the only places where to use them.
                
> 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

Reply via email to