On 22/06/2010 20:44, Paul Lindner wrote: > +0 to java 6. I know that many corporate users will choose to not use this > library if java 5 is not supported and we will intentionally limit the > customer base. > > However by the time it's ready to roll we can expect more java 6 uptake.
Maybe we can work out a way to release an implementation that ditches the features we're after using, I'll have a think. Would probably mean programmatic configuration only though. p > On Tue, Jun 22, 2010 at 11:12 AM, Simone Tripodi > <[email protected]>wrote: > >> Hi all, >> Pid and I are doing - even if small - progresses to design the OAuth >> java APIs, there are small but crucial points that have to be fixed. >> We need now to know which Java version we should support, so please >> cast your votes to >> >> [] Java6 >> [] Java5 >> >> Choices explanations would be more than appreciated. >> >> My vote is for Java6, mainly because we can use: >> >> * the ServiceLoader engine; >> * the APT invoked by javac (and we could generate oauth POJOs >> marshallers/unmarshallers to/from various formats); >> * the built-in JAXB APIs. >> >> All the best, >> Simo >> >> http://people.apache.org/~simonetripodi/ >> http://www.99soft.org/ >> >
signature.asc
Description: OpenPGP digital signature
