[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8224:
-------------------------
Attachment: 8224.gen.scriptv3.txt
8224.gen.scriptv3.txt
Adds script to generate hadoop1 and hadoop2 poms that have modules
and profiles appropriately set.
Also cleaned up our dependency settings after review of dependency:tree
and dependency:analyze w/ hadoop1 and hadoop2 setups.
Purged our use of slf4j. We don't need it.
A dev-support/generate-hadoopX-poms.sh
Script to generate pom.xml.hadoop1 or pom.xml.hadoop2 everywhere
which we pass to maven w/ -f flag when we want to publish coherent
hbase-hadoop1 and hbase-hadoop2.
M hbase-client/pom.xml
Set marker string under hadoop1.1 profile. Ditto for hadoop2 profile
for use by above script so it can find where to set profiles.
Declare depenencies we were using anyways.
M hbase-common/pom.xml
M hbase-examples/pom.xml
M hbase-prefix-tree/pom.xml
M hbase-it/pom.xml
M hbase-server/pom.xml
Purge unused slf4js.
Declare depenencies we were using anyways.
Set marker string under hadoop1.1 profile. Ditto for hadoop2 profile
for use by above script so it can find where to set profiles.
M hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java
Remove unwarranted user of slf4j. Use our usual logging instead.
M hbase-hadoop1-compat/pom.xml
M hbase-hadoop2-compat/pom.xml
Moved the dependency up into parent pom rather than have it repeat
twice, once here and once in hadoop2-compat.
Declare depenencies we were using anyways.
M
hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java
M
hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java
Use commons logging instead of slf4j.
M pom.xml
Added to dependencymanagement libs we were using already but undeclared.
Removed our depnding on an explicit slf4j version -- let the transitive
includes
sort it out since we don't use it anymore.
Declare depenencies we were using anyways.
Add some excludes for stuff we don't need.
Set marker string under hadoop1.1 profile. Ditto for hadoop2 profile
for use by above script so it can find where to set profiles.
> Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to
> version string
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-8224
> URL: https://issues.apache.org/jira/browse/HBASE-8224
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.95.2
>
> Attachments: 8224-adding.classifiers.txt, 8224.gen.script.txt,
> 8224.gen.scriptv3.txt, 8224.gen.scriptv3.txt, hbase-8224-proto1.patch
>
>
> So we can publish both the hadoop1 and the hadoop2 jars to a maven
> repository, and so we can publish two packages, one for hadoop1 and one for
> hadoop2, given how maven works, our only alternative (to the best of my
> knowledge and after consulting others) is by amending the version string to
> include hadoop1 or hadoop2.
--
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
