[
https://issues.apache.org/jira/browse/HBASE-12909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14289359#comment-14289359
]
Sean Busbey commented on HBASE-12909:
-------------------------------------
I ran through -PrunAllTests and all tests pass. I had to rerun
TestCacheOnWrite. I presume the failure on first run was a resource contention
issue since this was on a VM that isn't very powerful.
Test scoped dependencies won't show up as transitive dependencies when an
artifact is listed as a dependency of another project, that's true. AFAICT, the
only artifact we publish where we would want junit to show up is
hbase-testing-util. the current patch properly changes the scope for that case.
for the curious, the reason junit and mockito weren't showing up properly there
is that the parent pom was setting the scope to test. This is normally what we
want, but that scope overrides the normal changing of test scope to compile
scope when hbase-testing-util tries to add the test-jars for other components.
> 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)
