Hi Csaba, We haven't discussed really about 1.3 and 1.4 capability. In fact, although I'm afraid you won't be happy about this, I was going to ask the rest of the JSecurity dev team if we should only focus on 1.5+ from now on.
1.5 already begun its end-of-life phase a while ago and 1.3 and 1.4 are already decommissioned by Sun. I don't know that it would be worth our effort to continually check for 1.3/1.4 compatibility when probably 99% of our uses are 1.5+. My estimation could be incorrect of course. I'm open to feedback from others if we should continue to support 1.4 and below... If you are able to identify what parts of the API fail, then maybe we might be able to revert some code to be compatible. But I don't know if it would be worth it or not when there is already a lot of work to be done for JSecurity 1.0 :/ Thanks for the feedback. How do others feel? Cheers, Les On Fri, Jan 30, 2009 at 9:48 AM, Csaba Nemeth <[email protected]> wrote: > Hello, > > I am testing jsecurity for a project that is based on jdk14. > I was happy to see while the code is jdk15, it uses retroweaver for earlier > jdks. > > The only problem I found is that while the classes are jdk14 compatible, > the api used is not. > > For example, running a simple example under jdk14 uses the > TextConfigurationRealm - which uses the java.util.Scanner - java 1.5 api. > > Are there any plans on using 1.4 api only? > Is it still the plan that jsecurity is going to work under 1.4 and 1.3? > > Thank you, > Csaba > > > __________________________________________________________________ > Instant Messaging, free SMS, sharing photos and more... Try the new Yahoo! > Canada Messenger at http://ca.beta.messenger.yahoo.com/ >
