search

google-code-export / uimafit

Automatically exported from code.google.com/p/uimafit
2 stars 1 forks source link

upgrade to Java 6 #84

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
We should consider upgrading UimaFIT to Java 6. Java 5 reached its End of 
Service Life (EOSL) on November 3, 2009.

The main reason I bring this up is that there's no real way to get a Java 5 on 
Mac OS X 10.6 (Snow Leopard) - only JDK 6 is supported. All the hacks posted on 
the web that I've tried didn't work. So I'm constantly getting the following 
warning for all UimaFIT projects:

Build path specifies execution environment J2SE-1.5. There are no JREs 
installed in the workspace that are strictly compatible with this environment.

Original issue reported on code.google.com by steven.b...@gmail.com on 15 Apr 2011 at 8:20

GoogleCodeExporter commented 9 years ago 
I also have the warnings, but I never even noticed them.

As far as I can see, UIMA trunk still sticks to Java 1.5. For that reason I 
lean towards doing that too, although that would mean that I have to at least 
configure my Linux Jenkins to compile using JDK 1.5 in order to detect 
incompatibilities, because my workstation is also OS X 10.6.

Original comment by richard.eckart on 15 Apr 2011 at 9:24

GoogleCodeExporter commented 9 years ago 
Yeah, it would probably be good to have someone, somewhere compiling UimaFIT 
regularly with Java 1.6 to make sure we're not using new methods, etc.

It does probably make sense to wait until UIMA upgrades on this one. Perhaps 
that will come when Java 7 is released (estimated at 2011/07/28 on 
http://openjdk.java.net/projects/jdk7/ ).

Original comment by steven.b...@gmail.com on 15 Apr 2011 at 9:30

GoogleCodeExporter commented 9 years ago 
Jenkins is configured to build with JDK 1.5.0_22 and Maven 3.0.3 now. Seems to 
work.

Original comment by richard.eckart on 15 Apr 2011 at 9:32

GoogleCodeExporter commented 9 years ago 
I ran through the developer setup instructions and found a compiler warning 
that reminded me that we haven't closed this issue yet.  I didn't understand 
comment #3 above.  Is there any reason not to move to 1.6 at this point?  

The compiler warning is on 
org.uimafit.factory.locator.JndiResourceLocator.initialize(ResourceSpecifier, 
Map).  The message is "Type safety: The expression of type Map needs unchecked 
conversion to conform to Map<String,Object>" and can be resolved by adding 
"unchecked" to the @SuppressWarnings annotation.

Original comment by philip.o...@oracle.com on 8 May 2012 at 10:30

GoogleCodeExporter commented 9 years ago 
I vote +1 for upgrading to 1.6.

Original comment by richard.eckart on 8 May 2012 at 10:32

GoogleCodeExporter commented 9 years ago 
Some dependencies are now Java 6 with the latest update of the uimaFIT 
dependencies. Thus, uimaFIT can no longer build on a Java 5 system. I am 
upgrading the target version to 1.6 now.

Original comment by richard.eckart on 20 Aug 2012 at 8:19

GoogleCodeExporter commented 9 years ago 
uimaFIT 2.0.0 has been changed to be compatible with Java 1.5 again just as the 
rest of the UIMA framework.

Original comment by richard.eckart on 20 Jul 2013 at 9:05