+1 to move to 6 or 7. It seems to me that projects are on the move to 7 now anyways. I just upgraded DKPro Core trunk to Java 7 because we start having dependencies that are built with Java 7.
Personally, I'd suggest upgrading to the level that is necessary. E.g. if you need features from Java 6 but not from Java 7, then going just to 6 would imho be better. -- Richard On 10.01.2014, at 13:53, Martin Toepfer <[email protected]> wrote: > +1 to move to Java 6. We sometimes use Ruta without the Eclipse workbench in > applications. Java 7 would also be fine, however, I think we should not move > to Java 8 until required. > > -- Martin > >> + 1 to move to Java 6 or Java 7 (or Java 8, GA due in mid-March). >> >> Here's my rationale (which will probably expose some of my ignorance about >> the >> Ruta details :-) ): >> >> Ruta is an Eclispe workbench. This means that the way you use it is to run >> Eclipse, and then Ruta runs "within it". [If Ruta is a thing which is used >> via >> being embedded into other systems, then the argument doesn't apply]. >> >> So, forcing a dependency on Java 7 or 8 means you have to run just one app, >> namely, Eclipse, on that Java. And Eclipse runs fine on Java 8 (candidates) >> already :-). >> >> So it's unlikely that will be much of an issue for your customers. >> >> This is in contrast to other deployments of UIMA things, where they're more >> likely (possibly) integrated into other systems, and those systems would >> need (a >> lot of testing- investment) to move to more recent versions of Java. >> >> -Marshall >> On 1/10/2014 7:04 AM, Peter Klügl wrote: >>> I know we already have talked about the strategy of the required java >>> version, but I think I have seen that ducc depends on java 6. >>> >>> I would like to move ruta also to java 6 since I could really need some >>> methods only available in java 6. >>> >>> Opinions? >>> >>> Peter
