Re: ASM 4.0 RC2 released
Martin Ellis <[email protected]>
| Newsgroups | gmane.comp.java.objectweb.asm |
|---|---|
| Message-ID | <CAH1co3=Rr728UhCQt==5rEqa7vAY9P-f0bufMu8PyaJ6EqSWMA@mail.gmail.com> |
On Sun, Sep 11, 2011 at 3:21 PM, <[email protected]> wrote: > as discussed on this mailing list, we decided to make the necessary changes to support backward binary compatibility right now, instead of in one or two years. This required some big, non backward compatible API changes in this new release candidate, compared to RC1 (mainly the replacement of interfaces with abstract classes). However, the goal of these modifications is that all future ASM versions will be backward compatible with ASM 4.0. RC2 seems good to me. I've upgraded at work, and used it on a weekend project without any problems. A suggestion for 4.0: it'd be good to have sources for all the jars in the Maven repository. Having source available in the IDE makes it much easier to check documentation when using code-completion (or even browsing the source to check something). I realise that most ASM jars don't have debug info, so tracing through ASM source in a debugger wouldn't work. But (unlike some other Java libraries I could mention), ASM isn't a library that I frequently have to trace through to investigate bugs, so no great loss there. I accept that there's some scope for confusion if people expect to be able to trace through the libraries, but for me at least, sources for all jars would be an improvement over the current situation (using asm-debug-all, even though I don't use a big chunk of it). Regards, Martin
message-footer.txt
(text/plain, 238 B)
-- You receive this message as a subscriber of the [email protected] mailing list. To unsubscribe: mailto:[email protected] For general help: mailto:[email protected]?subject=help OW2 mailing lists service home page: http://www.ow2.org/wws