[
https://issues.apache.org/jira/browse/HBASE-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291333#comment-14291333
]
Enis Soztutar commented on HBASE-12909:
---------------------------------------
Ok, I've reverted the commit pushed to master. In HBASE-8421 the reason for
having junit dep in the main scope was to be able to run ITs from command line
(ITDriver). I've created a tarball with this patch, and it does not contain
junit jar which is necessary. I thought previously that the tarball will be
made from the test scope, but apparently it is not the case.
What we should do with this? Close as won't fix? I am temporarily removing this
from 1.0.0.
> Junit listed at compile scope instead of test
> ---------------------------------------------
>
> Key: HBASE-12909
> URL: https://issues.apache.org/jira/browse/HBASE-12909
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 1.0.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Fix For: 1.0.0, 2.0.0
>
> Attachments: HBASE-12909.1.patch.txt
>
>
> Right now our top level pom lists junit as a dependency for every module in
> the compile scope, which makes it subject to our compatibility promises.
> It should instead be test scope.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
