nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lewis John McGibbney (Updated) (JIRA)" <>
Subject [jira] [Updated] (NUTCH-1273) Fix [deprecation] javac warnings
Date Fri, 02 Mar 2012 12:40:57 GMT


Lewis John McGibbney updated NUTCH-1273:

    Attachment: NUTCH-1273-v2-trunk.patch

This patch goes some length to address the issues described on user or dev list. I'm having
some problems with Exceptions, and tbh not really sure about the new API construction. I opted
to switch the MimeUtil#autoResolveContentType code to use a mimetype String as oppose to either
* Switch the code to use MediaType rather than MimeType, and call
 DefaultDetector directly (rather than using the Tika facade class)
* If we get back a String (not null) for the mimetype, create a MimeType
 object for it.

In all honesty, if the method I have used is not suitable then I think the latter of the above
alternatives would be better simply because we arwe not currently calling MediaType anywhere,
I've been trying to keeep with consistency when workin on this one.

If someone could have a look it would be greatly appreciated. Thanks 
> Fix [deprecation] javac warnings
> --------------------------------
>                 Key: NUTCH-1273
>                 URL:
>             Project: Nutch
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: nutchgora, 1.5
>            Reporter: Lewis John McGibbney
>            Priority: Minor
>             Fix For: nutchgora, 1.5
>         Attachments: NUTCH-1273-nutchgora.patch, NUTCH-1273-trunk.patch, NUTCH-1273-v2-trunk.patch
> As part of this task, these warnings should be resolved, however this particular strand
of warnings can either be resolved by adding
> {code}
> @SuppressWarnings("deprecation")
> {code}
> or by actually upgrading our class usage to rely upon non-deprecated classes. Which option
is more appropriate for the project?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message