drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Altekruse <altekruseja...@gmail.com>
Subject Re: Proguard verbose output on latest master ?
Date Tue, 14 Oct 2014 21:11:39 GMT
Not sure about the impact of the proguard upgrade, but I almost always
cancel the build if I happen to see that output. I know if it gets to that
point that I haven't failed any tests. The only reason we have that in the
build is to make the thin jdbc jar, which most devs on the team aren't
making use of right now. The longer term solution has been discussed, which
is pulling out the proguard step into a release only version of the build
that will be run less frequently.


On Tue, Oct 14, 2014 at 1:58 PM, Aman Sinha <asinha@maprtech.com> wrote:

> I am seeing a whole bunch of Proguard verbose output when doing a build of
> latest 0.7 master branch.   Anyone else seeing this ?  I thought a prior
> commit had fixed this but maybe the upgrade of Proguard to 5.0 changed this
> behavior.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message