[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[
https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-22052:
Release Note:
Fixed awkward dependency issue that prevented site building.
note specific to HBase 2.1.4
HBase 2.1.4 shipped with an early version of this fix that incorrectly altered
the libraries included in our binary assembly for using Apache Hadoop 2.7 (the
current build default Hadoop version for 2.1.z). For folks running out of the
box against a Hadoop 2.7 cluster (or folks who skip the installation step of
[replacing the bundled Hadoop
libraries](http://hbase.apache.org/book.html#hadoop)) this will result in a
failure at Region Server startup due to a missing class definition. e.g.:
```
2019-03-27 09:02:05,779 ERROR [main] regionserver.HRegionServer: Failed
construction RegionServer
java.lang.NoClassDefFoundError: org/apache/htrace/SamplerBuilder
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:644)
at org.apache.hadoop.hdfs.DFSClient.(DFSClient.java:628)
at
org.apache.hadoop.hdfs.DistributedFileSystem.initialize(DistributedFileSystem.java:149)
at
org.apache.hadoop.fs.FileSystem.createFileSystem(FileSystem.java:2667)
at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:93)
at
org.apache.hadoop.fs.FileSystem$Cache.getInternal(FileSystem.java:2701)
at org.apache.hadoop.fs.FileSystem$Cache.get(FileSystem.java:2683)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:372)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:171)
at org.apache.hadoop.fs.FileSystem.get(FileSystem.java:356)
at org.apache.hadoop.fs.Path.getFileSystem(Path.java:295)
at
org.apache.hadoop.hbase.util.CommonFSUtils.getRootDir(CommonFSUtils.java:362)
at
org.apache.hadoop.hbase.util.CommonFSUtils.isValidWALRootDir(CommonFSUtils.java:411)
at
org.apache.hadoop.hbase.util.CommonFSUtils.getWALRootDir(CommonFSUtils.java:387)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.initializeFileSystem(HRegionServer.java:704)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.(HRegionServer.java:613)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.constructRegionServer(HRegionServer.java:3029)
at
org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.start(HRegionServerCommandLine.java:63)
at
org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.run(HRegionServerCommandLine.java:87)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at
org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:149)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.main(HRegionServer.java:3047)
Caused by: java.lang.ClassNotFoundException: org.apache.htrace.SamplerBuilder
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 26 more
```
Workaround via any _one_ of the following:
* If you are running against a Hadoop cluster that is 2.8+, ensure you replace
the Hadoop libaries in the default binary assembly with those for your version.
* If you are running against a Hadoop cluster that is 2.8+, build the binary
assembly from the source release while specifying your Hadoop version.
* If you are running against a Hadoop cluster that is a supported 2.7 release,
ensure the `hadoop` executable is in the `PATH` seen at Region Server startup
and that you are not using the `HBASE_DISABLE_HADOOP_CLASSPATH_LOOKUP` bypass.
* For any supported Hadoop version, manually make the Apache HTrace artifact
`htrace-core-3.1.0-incubating.jar` available to all Region Servers via the
HBASE_CLASSPATH environment variable.
* For any supported Hadoop version, manually make the Apache HTrace artifact
`htrace-core-3.1.0-incubating.jar` available to all Region Servers by copying
it into the directory `${HBASE_HOME}/lib/client-facing-thirdparty/`.
was:
Fixed awkward dependency issue that prevented site building.
*note*
The HBase Shaded Client is likely 'busted' in 2.1.4. HBase 2.1.4 shipped with
the first version of this patch. The patch was subsequently reopened when it
was found that it failed a special IT test that was using the shaded hbase
mapreduce client. The IT test was failing because an old htrace
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Release Note: Fixed awkward dependency issue that prevented site building. *note* The HBase Shaded Client is likely 'busted' in 2.1.4. HBase 2.1.4 shipped with the first version of this patch. The patch was subsequently reopened when it was found that it failed a special IT test that was using the shaded hbase mapreduce client. The IT test was failing because an old htrace lib was excluded in the original committed patch. was: Fixed awkward dependency issue that prevented site building. *note* HBase 2.1.4 shipped with the first version of this patch. The patch was subsequently reopened when it was found that it failed a special IT test that was using the shaded hbase mapreduce client. The IT test was failing because an old htrace lib was excluded in the original committed patch. > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.0.5, 2.3.0, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch, nothing_change.patch, nothing_change.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-22052: Release Note: Fixed awkward dependency issue that prevented site building. *note* HBase 2.1.4 shipped with the first version of this patch. The patch was subsequently reopened when it was found that it failed a special IT test that was using the shaded hbase mapreduce client. The IT test was failing because an old htrace lib was excluded in the original committed patch. was: Fixed awkward dependency issue that prevented site building. HBase 2.1.4 shipped with the first version of this patch. The patch was subsequently reopened when it was found that it failed a special IT test that was using the shaded hbase mapreduce client. The IT test was failing because an old htrace lib was excluded in the original committed patch. > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.0.5, 2.3.0, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch, nothing_change.patch, nothing_change.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Release Note: Fixed awkward dependency issue that prevented site building. HBase 2.1.4 shipped with the first version of this patch. The patch was subsequently reopened when it was found that it failed a special IT test that was using the shaded hbase mapreduce client. The IT test was failing because an old htrace lib was excluded in the original committed patch. > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.0.5, 2.3.0, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch, nothing_change.patch, nothing_change.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Resolution: Fixed Fix Version/s: 2.3.0 3.0.0 Status: Resolved (was: Patch Available) Reverted from 2.2 and then applied a compound of the mess I'd worked out on branch-2.1 as a single commit on branch-2.2. Cherry-picked from 2.2 to branch-2 and master. > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 3.0.0, 2.2.0, 2.0.5, 2.3.0, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch, nothing_change.patch, nothing_change.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: nothing_change.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.2.0, 2.0.5, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch, nothing_change.patch, nothing_change.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: nothing_change.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.2.0, 2.0.5, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch, nothing_change.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052-branch-2.1.003.addendum2.txt > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.2.0, 2.0.5, 2.1.4 > > Attachments: HBASE-22052-branch-2.1.003.addendum2.txt, > HBASE-22052.2.1.003.addendum1.txt, HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.2.1.003.addendum1.txt > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.2.0, 2.0.5, 2.1.4 > > Attachments: HBASE-22052.2.1.003.addendum1.txt, > HBASE-22052.branch-2.0.001.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.003.patch, > HBASE-22052.branch-2.0.004.patch, HBASE-22052.branch-2.1.001.patch, > HBASE-22052.branch-2.1.002.patch, HBASE-22052.branch-2.1.003.patch, > HBASE-22052.branch-2.2.001.patch, HBASE-22052.branch-2.2.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.1.003.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.2.0, 2.0.5, 2.1.4 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.1.003.patch, HBASE-22052.branch-2.2.001.patch, > HBASE-22052.branch-2.2.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Fix Version/s: 2.1.4 2.2.0 > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.2.0, 2.0.5, 2.1.4 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.2.001.patch, HBASE-22052.branch-2.2.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.2.002.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.5 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.2.001.patch, HBASE-22052.branch-2.2.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.2.001.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.5 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch, > HBASE-22052.branch-2.2.001.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.1.002.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.5 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch, HBASE-22052.branch-2.1.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.0.004.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.5 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.0.004.patch, > HBASE-22052.branch-2.1.001.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.1.001.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.5 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch, HBASE-22052.branch-2.1.001.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Fix Version/s: 2.0.5 > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Fix For: 2.0.5 > > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.0.003.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch, > HBASE-22052.branch-2.0.003.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.0.002.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch, HBASE-22052.branch-2.0.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.0.002.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Attachments: HBASE-22052.branch-2.0.001.patch, > HBASE-22052.branch-2.0.002.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Assignee: stack Status: Patch Available (was: Open) > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Assignee: stack >Priority: Major > Attachments: HBASE-22052.branch-2.0.001.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (HBASE-22052) pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove redunant version specifications
[ https://issues.apache.org/jira/browse/HBASE-22052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-22052: -- Attachment: HBASE-22052.branch-2.0.001.patch > pom cleaning; filter out jersey-core in hadoop2 to match hadoop3 and remove > redunant version specifications > --- > > Key: HBASE-22052 > URL: https://issues.apache.org/jira/browse/HBASE-22052 > Project: HBase > Issue Type: Task >Reporter: stack >Priority: Major > Attachments: HBASE-22052.branch-2.0.001.patch > > > Working on HBASE-22029, where we fail compile of hbase-it module four hours > into an RC build, it looks like transitive include of jersey-core is the > culprit. hadoop3 profile does a bunch of jersey-core exclusions. This issue > is about having hadoop2 profile and hadoop3 profiles match around jersey-core > treatment. Some miscellaneous cleanups are also done. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
