On Tue, Jun 29, 2010 at 21:58, Tor Norbye <[email protected]> wrote:
> On Jun 29, 2:29 am, Jan Goyvaerts <[email protected]> wrote: > > - The new java hints are certainly nice but in my opinion nothing > beats > > Findbugs indeed. It does the checks mentioned in the cast and quite > some > > others. The SQE project provides a plugin for Findbugs, PMD, > Checkstyle en > > dependency check. It's a bit performance-hungry though... > > Yes, findbugs is very nice, but I think it's also a good idea to have > IDE support for this. Findbugs will find the errors for you, but it > will not FIX them. To take the logger example again, NetBeans rewrites > your source code to use a message template rather than the string > concatenation syntax. For collections it replaces the .length == 0 > with isEmpty(), etc. etc. It also has an educational aspect in that > the warnings are right there when you are editing the source, rather > than when you are combing over the source code later. > > Findbugs has one huge strength: it operates on bytecode only. This > means that it can find bugs in your code regardless of which JVM > language you used. This was an amazing realization for me back when we > were working on the Visual Basic compiler -- we had debugging and even > findbugs working, since in both cases only the byte code and a > suitable linenumber table mattered! > I didn't know that - about Findbugs using bytecode only. I often wondered why the step wasn't taken to propose fixes. :-) > > why it is scanning the very same Maven libraries each time I'm > starting up ? > > Sorry, I don't use Maven so I can't really comment on this other than > to say I'm sorry it sounds like it's not fixed yet. > Logically, if the maven artifact is not a snapshot, it *should* not be changed anymore. *Ever.* It should also mean that whatever statistics, indexing, ... you made for an artifact it can be used for all the projects depending on it. Existing *and* future projects ! And in an ideal world the Maven repository would contain the stats and indices together with the code, source and javadoc. So we won't have to scan Maven jars at all. :-) That's for some far future of course. But what it possible *today* - in my opinion - is that the stats and indices can be stored in a central place and reused across projects. Just like it does already for jars in the local maven repository. Why not apply the same principle for indices ? -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
