Thanks, Ben. You are absolutely correct. The hive-exec is an uber jar including all "protobuf" classes. So now my only option is to use "fileset" to filter these classes out. Thanks Yong
> Date: Wed, 19 Aug 2015 10:14:32 -0700 > Subject: Re: Why Maven included "provided" scope dependency in the final > jar-with-dependency > From: [email protected] > To: [email protected] > > Not saying it's likely, but maybe one of your other dependencies is > actually an uberjar which rolled protobuf into itself. We've run into that > before. > > On Wed, Aug 19, 2015 at 7:06 AM, java8964 <[email protected]> wrote: > > > Thanks for you suggestion, but it didn't work in my case. > > > > > From: [email protected] > > > Date: Wed, 19 Aug 2015 08:34:04 -0500 > > > Subject: Re: Why Maven included "provided" scope dependency in the final > > jar-with-dependency > > > To: [email protected] > > > > > > > 1) The scope is changed to "provided" in this case, why the final jar > > still > > > > contains protobuf-java classes? > > > > 2) If the above way is not the right way to handle this case, what > > should I > > > > do? Basically, I want hive-jdbc as "compile", but exclude > > "protobuf-java" > > > > dependency. > > > > > > 1. Not sure why that is happening. > > > > > > 2. Try adding an explicit dependency to protobuf-java in your own > > > project pom, and specify the scope as provided there. See if that > > > forces it to do what you want. > > > > > > Wayne > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > >
