I think I've peeled the next layer of the onion. The maven build I'm using doesn't call javac as part of the build process; Instead it uses the classes already produced by Eclipse, which supports debugging and development. These classes are not optimized at all, and in particular each class is compiled separately, as though it would be linked at runtime with an arbitrary set of other classes.
In normal delivery environments, these ignorant-of-others classes would be presented to a JIT which would resolve all the linkages and optimize things like field references and enum dispatches, so the lack of optimization at the class level might be unimportant. Does this make sense? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
