What surprised me the most is people complaining about open source docs, but then very rarely supply any patches for improving them. As they surely do put time into figuring out how to use the software (and to write mail complaining), they would be the very best candidates for fixing the existing docs. Eric, you have an excellent opportunity here to show that you're not one of these people!
/Anders On Mon, Oct 10, 2011 at 02:10, Benson Margulies <bimargul...@gmail.com> wrote: > On Sun, Oct 9, 2011 at 7:35 PM, Stephen Connolly > <stephen.alan.conno...@gmail.com> wrote: >> in fairness i think i wrote most of the docs. Kohsuke's original docs were >> less than minimal. most of the docs were written while on public transport >> on a shitty little netbook. > > Well, little did I know. Having met KK's work before, I just assumed > that this was an unusually verbose example :-) > >> >> i don't currently have the time to prettify the docs further, and when i >> have time i want to sort out the versions-maven-plugin integration tests so >> that i can roll releases with new features safely >> >> - Stephen >> >> --- >> Sent from my Android phone, so random spelling mistakes, random nonsense >> words and other nonsense are a direct result of using swype to type on the >> screen >> On 9 Oct 2011 23:14, "Benson Margulies" <bimargul...@gmail.com> wrote: >> >>> 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: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
