[
https://issues.apache.org/jira/browse/HBASE-11422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Boudnik updated HBASE-11422:
---------------------------------------
Attachment: HBASE-11422.0.98.patch
I don't think that such use of classifier is legit. It would be in Ivy, however
Maven's classifier has a somewhat different semantic, e.g. "sources" or
"javadoc". Or, perhaps, "hadoop1"
It might help with the issue, but it doesn't sound like correct solution to me.
I think the main issue is the missed {{<scope>test</scope>}} in the number of
the modules like hbase-shell. I have tried to add it to hbase-server and
hbase-shell and it seems much better now. Attaching the patch for an
observation.
In fact, it fixes everything except for hbase-testing-util as this module
_explicitly_ uses test artifacts in the compilation phase. Like this
{code}
<dependency>
<groupId>org.apache.hadoop</groupId>
<artifactId>hadoop-hdfs</artifactId>
<type>test-jar</type>
<scope>compile</scope>
</dependency>
{code}
I don't have enough knowledge about this module to judge if this is a
reasonable expectation. I will check on it.
To sum it up: I think the use of {{classifier}} will just camouflage the
problem.
> Specification of classifier is missing for certain Hadoop dependencies
> ----------------------------------------------------------------------
>
> Key: HBASE-11422
> URL: https://issues.apache.org/jira/browse/HBASE-11422
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Assignee: Ted Yu
> Fix For: 0.99.0, 0.98.4
>
> Attachments: 11422-trunk-v1.txt, 11422-v1.txt, HBASE-11422.0.98.patch
>
>
> [~cos] reported in the mailing thread, 'HBase 0.98.x dependency problems',
> that specifying hadoop-two.version with value other than 2.2.0 pulls in
> incorrect dependencies such as:
> {code}
> [INFO] | \- org.apache.hadoop:hadoop-hdfs:test-jar:tests:2.2.0:compile
> {code}
> This is due to missing specification of classifier in the pom.xml files.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
