Dave Brosius

When i use the following mock code, it highlights the line currentCriteria = new SearchCriteriaBuilder().withFromDate(latestPaymentTime).withToDate(currentCriteria.getToDate()).build(); ------------- import java.time.LocalDateTime; import java.util.ArrayList; import java.util.List; public class Thrawn { private int queryLoopLimit; private...

Is there any kind of code generation/augmentation that perhaps is not updating the line number table properly?

while this is splitting hairs, you could pull SearchCriteriaBuilder builder = new SearchCriteriaBuilder(); out of the loop, and just do currentCriteria = builder.withFromDate(latestPaymentTime).withToDate(currentCriteria.getToDate()).build(); in the loop

yes no doubt it's a FP, and should be fixed. I'm just saying that in this specific example you could just allocate it once.

CE should only fire if the user and usee has similar packages. Normally in a third party situation that is not the case and CE is not fired. Is this...

I'll have to do some reading... pretty esoteric i'm thinking... Not that you are wrong, just i am ignorant here.

Well, this detector isn't about building circular object graphs, for instance, with a concern for building data islands that the gc would have trouble with. The JVM handles those effectively....

it's almost certainly the ternary... spotbugs doesn't handle them all that well, specifically the first part of the ternary is ldc #149 // String fr_FR 56: goto 61 is kind...

Alright, so i pushed your code to LSC_Sample.fp363 and it doesn't show the error, with this, javap ``` public java.lang.String fp393(); descriptor: ()Ljava/lang/String; flags: ACC_PUBLIC Code: stack=2, locals=2, args_size=1 0:...

You are likely correct, although in this case, "contains" more accurately depicts what you are trying to do, over indexOf. So the question is how much does it help performance-wise......