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 7:35 PM Mark Roberts <mar...@cs.washington.edu> wrote: > 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 > strongly that it needs to remain. Perhaps change the message to suggest > recompiling with a newer version of Java? But of course, a lot of these > classfiles have been passed about and have become disconnected from their > source. > > Mark > > -----Original Message----- > From: Gary Gregory [mailto:garydgreg...@gmail.com] > Sent: Wednesday, April 10, 2019 4:20 PM > To: Commons Developers List <dev@commons.apache.org> > Subject: [BCEL] Console warning > > 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 you what > class file it is complaining about. > > 1) Should remove the logging? > or, > 2) Should we improve the logging? > or, > 3) Do nothing? > > Gary > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
