The official ASM distro has six JARs:
core: processing classes based on Class{Reader,Writer} visitors
tree: alternate API for processing classes; used in more advanced
applications
util: debugging utilities, such as the checking and tracing visitors
commons: random contributions, some of which are pretty useful (e.g.,
InstructionAdapter, SimpleRemapper)
xml: not even sure
analysis: a bytecode interpreter toolkit
Obviously people use core all the time. Everyone uses util and common
pieces sometimes; the util pieces are more commonly used at development
rather than runtime. I use the tree stuff not for code generation in
lambda, but I do use it in the 'indify' tool, for example. I've not
found any use for the analysis package yet.
Overall I think these boundaries are pretty reasonable ones.
On 2/3/2012 12:34 PM, Dmitry Samersoff wrote:
Brian,
Does any body has a justification to include all of them.
ASM has core and couple of interfaces around it. Subset included now to
jaxp workspace is enough to do all necessary things.
-Dmitry
On 2012-02-03 07:34, Brian Goetz wrote:
The main ASM distribution is broken into 5 jars, based on how people
tend to use it; this is probably a good starting candidate for module
boundaries.
On 2/2/2012 10:33 PM, Mandy Chung wrote:
On 2/2/2012 7:13 PM, David Holmes wrote:
Okay two questions :) : do you know when this will get modularized and
show up in the jigsaw repositories?
FWIW. We have been sync'ing up jigsaw forest with jdk8 periodically and
hope to do it in a regular basis. It's currently sync'ed with jdk8-b23.
When asm shows up in jdk8 promoted build, I hope to pull it down and do
the merge in the following week or two depending on how it'll be
modularized and their dependencies.
Mandy
