[ 
https://issues.apache.org/jira/browse/TIKA-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991117#comment-13991117
 ] 

Ann Burgess commented on TIKA-1287:
-----------------------------------

I have modified my updates to the NetCDFparser to work with the current version 
of NetCDF on Maven Central.  Once the new NetCDF version is on Maven Central, I 
will update the code accordingly.  I have created a NetCDFParserPatch.patch 
file for review, but will start a new JIRA issue for that. 

> Update NetCDF .jar file on Maven Central
> ----------------------------------------
>
>                 Key: TIKA-1287
>                 URL: https://issues.apache.org/jira/browse/TIKA-1287
>             Project: Tika
>          Issue Type: Improvement
>    Affects Versions: 1.5
>            Reporter: Ann Burgess
>              Labels: jar, maven, netcdf, tika, unit-test, update
>
> I am working to update the NetCDFParser file.  When using the most-recent 
> .jar file available from http://www.unidata.ucar.edu/ at the command line I 
> receive a note about a depreciated API: 
> javac -classpath 
> ../../../../tika-core/target/tika-core-1.6-SNAPSHOT.jar:../../../../toolsUI-4.3.jar
>  org/apache/tika/parser/netcdf/NetCDFParser.java
> Note: org/apache/tika/parser/netcdf/NetCDFParser.java uses or overrides a 
> deprecated API.
> Note: Recompile with -Xlint:deprecation for details.
> After updating the NetCDFParser file with non-deprecated methods (e.x. 
> changing "dimension.getName()" to "dimension.getFullName()") however, I get 
> failed unit tests in maven, which I assume is because the Maven Central Repo 
> has the lapsed version of the .jar file needed for NetCDF files (
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22edu.ucar%22%20AND%20a%3A%22netcdf%22)
>  .
> Can anyone provide insight into how I get the updated .jar file into the 
> Maven Central Repository? Is there an alternative method to update Tika so I 
> can run my unit tests in Maven?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to