et" 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: bpodgur...@gmail.com
>> To: users@maven.apa
to that
> before.
>
> On Wed, Aug 19, 2015 at 7:06 AM, java8964 wrote:
>
> > Thanks for you suggestion, but it didn't work in my case.
> >
> > > From: wayne...@gmail.com
> > > Date: Wed, 19 Aug 2015 08:34:04 -0500
> > > Subject: Re: Why Maven in
t; From: wayne...@gmail.com
> > Date: Wed, 19 Aug 2015 08:34:04 -0500
> > Subject: Re: Why Maven included "provided" scope dependency in the final
> jar-with-dependency
> > To: users@maven.apache.org
> >
> > > 1) The scope is changed to "provided
Thanks for you suggestion, but it didn't work in my case.
> From: wayne...@gmail.com
> Date: Wed, 19 Aug 2015 08:34:04 -0500
> Subject: Re: Why Maven included "provided" scope dependency in the final
> jar-with-dependency
> To: users@maven.apache.org
>
> &g
> 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 th
