Between the addition of the shaded jars in 1.1.0 and 1.1.1/1.2.0 building the shaded jars was moved to the release profile after complaints about how much time was added to the build by doing them all the time.
I think all the discussion was on JIRA: https://issues.apache.org/jira/browse/HBASE-13816 Rick, is there some place we could have called out this detail in docs to save you time? On 2017-11-03 20:49, Mike Drob <md...@apache.org> wrote: > Sean, > > Is this a historical vestige? Why can't we populate the shaded jars always? > > > > On Fri, Nov 3, 2017 at 7:51 PM, Sean Busbey <bus...@apache.org> wrote: > > > Hi Rick! > > > > You have to build with the "release" profile active for the shaded > > jars to be populated > > > > e.g.: > > > > mvn -Prelease -DskipTests clean install > > > > > > > > On Fri, Nov 3, 2017 at 7:16 PM, Rick Kellogg <rmkell...@comcast.net> > > wrote: > > > Greetings, > > > > > > > > > > > > I have been trying to build the latest HBase using the master branch. > > When > > > the hbase-sharded-client JAR file is generated, it does not include any > > > .class files. Build completes without any errors. Any ideas what > > might be > > > causing this issue? > > > > > > > > > > > > Attempted Maven Commands: mvn package -DskipTests=true and mvn install > > > -DskipTests=true > > > > > > > > > > > > Environnent: RHEL 7.3, Maven 3.5.0, Oracle JDK 1.8.0_152. > > > > > > > > > > > > Thanks, > > > > > > Rick Kellogg > > > > > > > > > > > > > > > > > >
