If you have to support 1.5, the easiest thing to do is eschew the use of 1.6 features. Just set the compiler plugin options for source and target of 1.5.
After you do that, you might still want the sniffer, since this does not stop you from accidentally coding calls to methods introduced in 1.6. If you really need 1.6 features, you might consider looking at retroweaver, which can convert 1.6 jars into 1.5 jars. *However*, once you start having two versions of a jar floating around (one for 1.5, one for 1.6), Maven is not really terribly helpful. This is not a use-case, apparently, that was anywhere near the front of the collective Maven mind when the dependency model was designed. As for the comprehensibility of the AS docs, well, KK is one of the smartest, nicest, guys pumping out useful stuff for the rest of us. However, the doc he writes is the doc he writes. Or, for another perspective, I could quote Tom Lehrer: "The problem with folk music is that it is written by the people." Considering what you are paying for this stuff, you might be argued to be getting a pretty good deal. My usual modus operandi is to go looking at a live example of the use of something if I am unclear as to how to use it. This can be an interesting easter-egg hunt. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
