People, please look at the data base before you post.   There has been a fix 
available since August of last year.   (Shortly before the last effort to 
produce a 6.0 pooped out.)  There is also a test case that demonstrates the 
problem.

> -----Original Message-----
> From: Andrey Loskutov [mailto:losku...@gmx.de]
> Sent: Tuesday, June 14, 2016 9:27 AM
> To: Commons Developers List; Mark Roberts; 'Commons Developers List'
> Subject: RE: [BCEL] Release Candidate on Thursday
> 
> 1) You mentioned "private Daikon" build. Can you propose a patch?
> 2) The bcel-243 reads as an enhancement (some functionality from 1.8 is
> missing). Is this true? Are there any regressions or any errors which can be
> demonstrated with current trunk state? It would be nice to add this info to
> Jira task.
> 
> 
> Am 14. Juni 2016 18:04:24 MESZ, schrieb Mark Roberts
> <mar...@cs.washington.edu>:
> >243 is a show stopper for Daikon.  It will continue to be shipped with
> >our private version of BCEL if it is not fixed.
> >
> >> -----Original Message-----
> >> From: James Carman [mailto:ja...@carmanconsulting.com]
> >> Sent: Tuesday, June 14, 2016 8:51 AM
> >> To: Commons Developers List
> >> Subject: Re: [BCEL] Release Candidate on Thursday
> >>
> >> Are they show stoppers?
> >>
> >> On Tue, Jun 14, 2016 at 11:50 AM Mark Roberts
> >> <mar...@cs.washington.edu>
> >> wrote:
> >>
> >> > I can tell you right now I would vote -1 as you have not picked up
> >the
> >> > fix for https://issues.apache.org/jira/browse/BCEL-243.
> >> >
> >> > Also, I think https://issues.apache.org/jira/browse/BCEL-195 is
> >fixed,
> >> > but has not been closed.
> >> >
> >> >
> >> > Thank you,
> >> > Mark Roberts
> >> >
> >> > > -----Original Message-----
> >> > > From: Benedikt Ritter [mailto:brit...@apache.org]
> >> > > Sent: Monday, June 13, 2016 11:49 PM
> >> > > To: Commons Developers List
> >> > > Subject: [BCEL] Release Candidate on Thursday
> >> > >
> >> > > Hi,
> >> > >
> >> > > I'm going to try to create an RC for BCEL 6.0 on friday. Please
> >have
> >> > > a
> >> > look at
> >> > > the current state of the code base and report any issues you see.
> >> > >
> >> > > Thank you!
> >> > > Benedikt
> >> >
> >> >
> >> >
> >---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> > For additional commands, e-mail: dev-h...@commons.apache.org
> >> >
> >> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >For additional commands, e-mail: dev-h...@commons.apache.org
> 
> --
> Kind regards,
> Andrey Loskutov
> 
> http://google.com/+AndreyLoskutov


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to