Tracking here: https://issues.apache.org/jira/browse/BCEL-316
Gary
On Fri, Apr 12, 2019 at 8:58 AM Gary Gregory wrote:
> I'm going to take the same lame-ish approach as
> org.apache.bcel.classfile.JavaClass.debug. It's a hack, but we have a
> precedent here; until we come to a better solution.
I'm going to take the same lame-ish approach as
org.apache.bcel.classfile.JavaClass.debug. It's a hack, but we have a
precedent here; until we come to a better solution. I think JUL is ... not
great.
Gary
On Wed, Apr 10, 2019 at 8:01 PM Bruno P. Kinoshita
wrote:
> +1 for dropping or improving.
+1 for dropping or improving. [imaging] will go out in 1.0 with j.u.l if I
recall correctly. Maybe a similar approach would work here, if we decide to
keep the logs.
CheersBruno
On Thursday, 11 April 2019, 11:58:40 am NZST, Rob Tompkins
wrote:
> On Apr 10, 2019, at 7:46 PM, Gary Gr
> On Apr 10, 2019, at 7:46 PM, Gary Gregory wrote:
>
>> On Wed, Apr 10, 2019 at 7:44 PM Rob Tompkins wrote:
>>
>>
>>
>>> On Apr 10, 2019, at 7:20 PM, Gary Gregory
>> wrote:
>>>
>>> Hi All:
>>>
>>> In BCEL, we log a warning to the console:
>>>
>>>
>> https://github.com/apache/commons-b
On Wed, Apr 10, 2019 at 7:44 PM Rob Tompkins wrote:
>
>
> > On Apr 10, 2019, at 7:20 PM, Gary Gregory
> wrote:
> >
> > Hi All:
> >
> > In BCEL, we log a warning to the console:
> >
> >
> https://github.com/apache/commons-bcel/blob/master/src/main/java/org/apache/bcel/classfile/Attribute.java#L24
The problem is really that BCEL is used in many places and that when you
see 30 lines of this warning when you are running a Maven build, you go
"What the heck this? Panic?!" especially when your project does not depend
on BCEL but BCEL comes in from transitive deps.
Gary
On Wed, Apr 10, 2019 at
> On Apr 10, 2019, at 7:20 PM, Gary Gregory wrote:
>
> Hi All:
>
> In BCEL, we log a warning to the console:
>
> https://github.com/apache/commons-bcel/blob/master/src/main/java/org/apache/bcel/classfile/Attribute.java#L240
>
> Which you can't really do anything about since it does not tell
I added that warning while working on the StackMap support for Java7 (and
beyond). We were testing (daikon and randoop) on several very large test
suites and found a large number of class files compiled with an obsolete
version of Java that generated bogus StackMap entries. I don't feel too
s
