forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-617) Forrest DOAP file
Date Tue, 28 Nov 2006 07:52:21 GMT
    [ http://issues.apache.org/jira/browse/FOR-617?page=comments#action_12453818 ] 
            
Gavin commented on FOR-617:
---------------------------

It looks to me like it should crawl the feed every now and again, but only if the feed url
was provided in the first place, so maybe the feed they have is from the wrong location.

Yesterday I submitted the correct URL for our doap.xml feed, no update yet.
(via http://www.codezoo.com/cs/user/create/doap_feedback?component_id=2845)
I also yesterday sent an email regarding the update, no answer yet.



> Forrest DOAP file
> -----------------
>
>                 Key: FOR-617
>                 URL: http://issues.apache.org/jira/browse/FOR-617
>             Project: Forrest
>          Issue Type: Improvement
>          Components: Documentation and website
>    Affects Versions: 0.8-dev
>            Reporter: Diwaker Gupta
>            Priority: Trivial
>         Attachments: doap.xml
>
>
> See http://thread.gmane.org/gmane.text.xml.forrest.devel/15097 for background.
> I've created an initial DOAP file for Forrest. Its easy to do this manually at each release.
I wasn't sure how to publish it, so I thought I'd let it burn on JIRA for a while. What do
people think?
> Its a regular XML file, but we want it published as-is, without any processing from Forrest.
Will putting an <exclude> directive for doap.xml in cli.xconf be enough?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message