Hi Chris, the issue is not the project itself, e.g., Jackrabbit, but the applications that build on it. There are many products out in commercial land that are still tied to Java 1.4. Once you start prereqing Java 1.5, those products will no longer be able to use your component. So the lower down in the food chain you are, the more you need to cater for backwards versions of Java (at least if you're interested in being used by commercial products).
--Thilo Chris Mattmann wrote: > Hi Guys, > > I don't have a strong preference for this either way. I simply ported over > the code for the Nutch metadata framework, which happened to use some > features from 1.5. I was a proponent of staying with 1.4 in the Nutch > community, however, was overruled there ;) > > Just to stir the pot a bit, I will say though, that IMHO, Java 1.5 is > entirely stable, has a strong, solid user base, and is becoming pervasive. > It also offers a lot of features that I think are truly useful. Is it too > much to ask of projects like Jackrabbit, etc., for them to create JDK 1.5 > builds? I know that this is possible even if the project only uses JDK 1.4 > language constructs, right? > > I think we may have to call for a vote on this though. What do others > think? > > Thanks! > > Cheers, > Chris > > > > On 6/13/07 3:43 AM, "Jukka Zitting" <[EMAIL PROTECTED]> wrote: > >> Hi, >> >> I noticed that both the Nutch metadata and the Lius lite code are >> using Java 5 features. >> >> Do you think we should require Java 5 in Tika, or should we support >> also Java 1.4? >> >> I believe there are a number of potential users (Jackrabbit included) >> that are still bound to Java 1.4, and since Java 1.4 will not reach >> end of life status any time soon (there isn't even a JSR for Java 7 >> yet) I personally think we should stick to 1.4 and remove the Java 5 >> features from Tika. >> >> BR, >> >> Jukka Zitting >
