You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Julien Nioche (JIRA)" <ji...@apache.org> on 2010/08/16 10:48:16 UTC

[jira] Created: (NUTCH-888) Remove parse-rss

Remove parse-rss
----------------

                 Key: NUTCH-888
                 URL: https://issues.apache.org/jira/browse/NUTCH-888
             Project: Nutch
          Issue Type: Task
          Components: parser
    Affects Versions: 2.0
            Reporter: Julien Nioche
            Assignee: Julien Nioche
             Fix For: 2.0


See https://issues.apache.org/jira/browse/NUTCH-887

{quote}
CM : I wrote parse-rss back in 2005, and used commons-feedparser from Kevin Burton and his crew. At the time it was well developed, and a little more flexible and easier for me to pick up than Rome. Since then however, its development has really become stagnant and it is no longer maintained.

In terms of real differences in terms of functionality, they are roughly equivalent so there isn't much difference.
{quote}

Already +1 from Andrzej and Chris. Will remove it tomorrow if there aren't any objections in the meantime 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (NUTCH-888) Remove parse-rss

Posted by "Julien Nioche (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/NUTCH-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899342#action_12899342 ] 

Julien Nioche commented on NUTCH-888:
-------------------------------------

Let's wait a bit before we remove it. The feed parsing that I've recently added to Tika won't be available until Tika 0.8 is released and the feed parser has not been ported to the new API yet as it requires the support for compound documents in Nutch 2.0. We won't have anything to parse feeds if we remove parse-rss now.

> Remove parse-rss
> ----------------
>
>                 Key: NUTCH-888
>                 URL: https://issues.apache.org/jira/browse/NUTCH-888
>             Project: Nutch
>          Issue Type: Task
>          Components: parser
>    Affects Versions: 2.0
>            Reporter: Julien Nioche
>            Assignee: Julien Nioche
>             Fix For: 2.0
>
>
> See https://issues.apache.org/jira/browse/NUTCH-887
> {quote}
> CM : I wrote parse-rss back in 2005, and used commons-feedparser from Kevin Burton and his crew. At the time it was well developed, and a little more flexible and easier for me to pick up than Rome. Since then however, its development has really become stagnant and it is no longer maintained.
> In terms of real differences in terms of functionality, they are roughly equivalent so there isn't much difference.
> {quote}
> Already +1 from Andrzej and Chris. Will remove it tomorrow if there aren't any objections in the meantime 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (NUTCH-888) Remove parse-rss

Posted by "Doğacan Güney (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/NUTCH-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898828#action_12898828 ] 

Doğacan Güney commented on NUTCH-888:
-------------------------------------

+1

> Remove parse-rss
> ----------------
>
>                 Key: NUTCH-888
>                 URL: https://issues.apache.org/jira/browse/NUTCH-888
>             Project: Nutch
>          Issue Type: Task
>          Components: parser
>    Affects Versions: 2.0
>            Reporter: Julien Nioche
>            Assignee: Julien Nioche
>             Fix For: 2.0
>
>
> See https://issues.apache.org/jira/browse/NUTCH-887
> {quote}
> CM : I wrote parse-rss back in 2005, and used commons-feedparser from Kevin Burton and his crew. At the time it was well developed, and a little more flexible and easier for me to pick up than Rome. Since then however, its development has really become stagnant and it is no longer maintained.
> In terms of real differences in terms of functionality, they are roughly equivalent so there isn't much difference.
> {quote}
> Already +1 from Andrzej and Chris. Will remove it tomorrow if there aren't any objections in the meantime 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.