You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Diwaker Gupta (JIRA)" <ji...@apache.org> on 2005/08/10 09:02:04 UTC
[jira] Created: (FOR-617) Forrest DOAP file
Forrest DOAP file
-----------------
Key: FOR-617
URL: http://issues.apache.org/jira/browse/FOR-617
Project: Forrest
Type: Improvement
Components: Documentation and website
Versions: 0.8-dev
Reporter: Diwaker Gupta
Assigned to: Diwaker Gupta
Priority: Trivial
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
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
David Crossley wrote:
> Ross Gardler wrote:
> > Diwaker Gupta wrote:
> > >David Crossley wrote:
> > >
> > >>The new http://projects.apache.org/ is now
> > >>available. Forrest is not yet listed.
> > >>
> > >>Do we need to change our DOAP file [1]
> > >>or maybe transform into a different syntax?
> > >>[1] http://forrest.apache.org/doap.xml
> > >>
> > >>Will it still serve the existing purpose
> > >>or do we need to maintain two files?
> > >
> > >I had created the aforementioned file to facilitate indexing in O'Reilly's
> > >CodeZoo [2]. The current doap.xml is not really a DOAP file -- its
> > >actually an ATOM feed, that contains an embedded DOAP spec as an entry. My
> > >bad in not naming it appropriately.
> > [2] http://codezoo.com/
> >
> > I've not looked at the final code for projects.a.o but the original code
> > acepted the DOAP as either a DOAP or an ATOM feed of a DOAP. I hope that
> > this feature has been kept.
>
> I noticed yesterday that David Reid added [1] to
> the list of descriptors. Now we show up and our page
> has the basic info. So your hope is satisfied.
>
> We should try adding some of the ASF-specific info.
I have done some of that over the last few weeks.
See the current result at:
http://projects.apache.org/projects/forrest.html
Would Forrest developers please review the
categories that i have assigned:
build-management, database, graphics, http,
network-client, network-server, web-framework, xml
The idea of categories is to create linkages
between projects.
The definitions are at:
http://projects.apache.org/categories.html
One thing that is not yet done, is to define
the standards that we implement. See Apache FOP
for example.
http://projects.apache.org/guidelines.html
http://projects.apache.org/doap-extensions.html
How do we modify the one at O'Reilly CodeZoo [2] above.
I thought that it automatically picked up our changes
but evidently not.
-David
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
Ross Gardler wrote:
> Diwaker Gupta wrote:
> >David Crossley wrote:
> >
> >>The new http://projects.apache.org/ is now
> >>available. Forrest is not yet listed.
> >>
> >>Do we need to change our DOAP file [1]
> >>or maybe transform into a different syntax?
> >>[1] http://forrest.apache.org/doap.xml
> >>
> >>Will it still serve the existing purpose
> >>or do we need to maintain two files?
> >
> >I had created the aforementioned file to facilitate indexing in O'Reilly's
> >CodeZoo [2]. The current doap.xml is not really a DOAP file -- its
> >actually an ATOM feed, that contains an embedded DOAP spec as an entry. My
> >bad in not naming it appropriately.
>
> I've not looked at the final code for projects.a.o but the original code
> acepted the DOAP as either a DOAP or an ATOM feed of a DOAP. I hope that
> this feature has been kept.
I noticed yesterday that David Reid added [1] to
the list of descriptors. Now we show up and our page
has the basic info. So your hope is satisfied.
We should try adding some of the ASF-specific info.
-David
> >So what we need to do is:
> >
> >o create a proper DOAP file for Forrest. There's even a web-based form to
> >help creating/updating it [3]
>
> May not be necessary, see above, but also see below.
>
> There are also a number of RDF additions to the DOAP format in the file
> requried by projects.a.o. So we need to add those, hopefully they have
> been documented at projects.a.o (not had time to look yet). If not then
> I guess a look over the httpd DOAP will show the full range of
> additional info since David Reid (who wrote the scripts for this) is an
> HTTPD dev.
>
> >o make sure the embedded DOAP in the Atom feed (rename the current
> >doap.xml to atom.xml?) remains in sync with the actual DOAP.
>
> If it is necessary then we should add a pipeline to the projectinfo
> plugin that creates the Atom feed from the DOAP file.
>
> In fact, it may be a good idea to do it this way anyway, then we are
> able to provide both formats. Maybe we should ewven think about
> providing a pattern that strips out all the additional rdf info just in
> case it messes with external applications (I don't think it wil though).
>
> Ross
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by Ross Gardler <rg...@apache.org>.
Diwaker Gupta wrote:
> On Tuesday 24 January 2006 4:09 pm, David Crossley wrote:
>
>>The new http://projects.apache.org/ is now
>>available. Forrest is not yet listed.
>>
>>Do we need to change our DOAP file [1]
>>or maybe transform into a different syntax?
>>[1] http://forrest.apache.org/doap.xml
>>
>>Will it still serve the existing purpose
>>or do we need to maintain two files?
>
>
> I had created the aforementioned file to facilitate indexing in O'Reilly's
> CodeZoo [2]. The current doap.xml is not really a DOAP file -- its actually
> an ATOM feed, that contains an embedded DOAP spec as an entry. My bad in not
> naming it appropriately.
I've not looked at the final code for projects.a.o but the original code
acepted the DOAP as either a DOAP or an ATOM feed of a DOAP. I hope that
this feature has been kept.
> So what we need to do is:
>
> o create a proper DOAP file for Forrest. There's even a web-based form to help
> creating/updating it [3]
May not be necessary, see above, but also see below.
There are also a number of RDF additions to the DOAP format in the file
requried by projects.a.o. So we need to add those, hopefully they have
been documented at projects.a.o (not had time to look yet). If not then
I guess a look over the httpd DOAP will show the full range of
additional info since David Reid (who wrote the scripts for this) is an
HTTPD dev.
> o make sure the embedded DOAP in the Atom feed (rename the current doap.xml to
> atom.xml?) remains in sync with the actual DOAP.
If it is necessary then we should add a pipeline to the projectinfo
plugin that creates the Atom feed from the DOAP file.
In fact, it may be a good idea to do it this way anyway, then we are
able to provide both formats. Maybe we should ewven think about
providing a pattern that strips out all the additional rdf info just in
case it messes with external applications (I don't think it wil though).
Ross
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by Diwaker Gupta <di...@apache.org>.
On Tuesday 24 January 2006 4:09 pm, David Crossley wrote:
> The new http://projects.apache.org/ is now
> available. Forrest is not yet listed.
>
> Do we need to change our DOAP file [1]
> or maybe transform into a different syntax?
> [1] http://forrest.apache.org/doap.xml
>
> Will it still serve the existing purpose
> or do we need to maintain two files?
I had created the aforementioned file to facilitate indexing in O'Reilly's
CodeZoo [2]. The current doap.xml is not really a DOAP file -- its actually
an ATOM feed, that contains an embedded DOAP spec as an entry. My bad in not
naming it appropriately.
So what we need to do is:
o create a proper DOAP file for Forrest. There's even a web-based form to help
creating/updating it [3]
o make sure the embedded DOAP in the Atom feed (rename the current doap.xml to
atom.xml?) remains in sync with the actual DOAP.
[2] http://codezoo.com
[3] http://projects.apache.org/create.html
Diwaker
--
Web/Blog/Gallery: http://floatingsun.net
On Apache: http://people.apache.org/~diwaker
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
The new http://projects.apache.org/ is now
available. Forrest is not yet listed.
Do we need to change our DOAP file [1]
or maybe transform into a different syntax?
[1] http://forrest.apache.org/doap.xml
Will it still serve the existing purpose
or do we need to maintain two files?
There are some guidelines at the site.
See some example DOAP RDF at each project
listing.
When it is ready, then Ross or i can add
it to the list in the "site-tools' SVN.
infrastructure/site-tools/trunk/projects/files.xml
-David
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by Diwaker Gupta <di...@apache.org>.
On Thursday 11 August 2005 1:40 am, David Crossley wrote:
> Aha, i see that you have been misunderstanding
> something fundamental. It needs to be published
> via our normal document publishing, just like
> any other document.
Thanks a ton for clearing that up! All this while I had been under the
impression that everything on Forrest's website had to go through a Forrest
publishing process. Completely forgot about the .htaccess! :-)
I have added the doap.xml file both to Forrest trunk and site. Right now I've
just synced them manually, and its not linked from anywhere within site.xml
yet. That will probably change as we figure out the best way of publishing
this info.
> To publish the website manually, do the following.
> It is good to get a feel for how it all happens,
> then use the forrestbot most times after that.
This was very useful, thanks again!
> Or use the forrestbot as described in
> trunk/etc/publishing_our_site.txt
> which you already did sucessfully recently.
I sure did.
Diwaker
--
Web/Blog/Gallery: http://floatingsun.net
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
Diwaker Gupta wrote:
> David Crossley wrote:
> > It would be better to have it in our SVN.
> > In that way, if you are absent at the time that we do
> > the next release, then we will still be able to update it.
> > No rush with that part of course, but that would be preferable.
>
> I can put it in SVN, thats not a problem. But it still needs to be published
> *somewhere* -- that was my main concern. Is there a way to host it under
> forrest.apache.org somehow?
Aha, i see that you have been misunderstanding
something fundamental. It needs to be published
via our normal document publishing, just like
any other document.
We have other files there too, e.g. mirrors.cgi
and .htaccess file, and raw files linked from some
pages, e.g. there are some pre-prepared dtdx/*.pdf
There are various ways of delivering raw files. See FAQ.
Just linking to daof.xml seems to work.
Maybe you do understand the mechanism for
publishing our website, but i will describe
it anyway. One day i will put it into a howto.
The source files go in our site-author
and then after one of us generates the site then
we would 'svn commit' to the separate "site" repository,
which gets automatically 'svn up' on the server to
form our website.
So we have these two repositories (and more):
https://svn.apache.org/repos/asf/forrest/trunk ... forrest-trunk
https://svn.apache.org/repos/asf/forrest/site ... forrest-site
To publish the website manually, do the following.
It is good to get a feel for how it all happens,
then use the forrestbot most times after that.
svn update forrest-trunk
svn update forrest-site
cd forrest-trunk/site-author
svn add content/whatever (adding entries to site.xml etc.)
forrest site
diff -rq build/site ../../forrest-site | grep -v "\.svn"
... Ensure that the differences are what you expect.
cp -Rf build/site ../../forrest-site
... Now do the usual stuff in your forrest-site working copy:
'svn update' 'svn status' 'svn add' 'svn diff' 'svn commit'
Or use the forrestbot as described in
trunk/etc/publishing_our_site.txt
which you already did sucessfully recently.
If the doaf.xml file was not going to be linked anywhere
then could take a shortcut and not do 'forrest site'.
Can keep the two files synchronised manually.
The same as what happens with the .htaccess file.
The source is at forrest-trunk/site-author/content/.htaccess
and the "generated" file is at forrest-site/.htaccess
-David
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by Diwaker Gupta <di...@apache.org>.
On Wednesday 10 August 2005 11:34 pm, David Crossley wrote:
> It would be better to have it in our SVN.
> In that way, if you are absent at the time that we do
> the next release, then we will still be able to update it.
> No rush with that part of course, but that would be preferable.
I can put it in SVN, thats not a problem. But it still needs to be published
*somewhere* -- that was my main concern. Is there a way to host it under
forrest.apache.org somehow?
Diwaker
--
Web/Blog/Gallery: http://floatingsun.net
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
Diwaker Gupta wrote:
> David Crossley wrote:
> > How about just linking to it from one of our pages
> > or as a menu item in the Project tab.
>
> Sounds fine. I've put the file up at [1] and I will maintain it there till we
> need a better solution. I'll get this information into Codezoo asap.
It would be better to have it in our SVN.
In that way, if you are absent at the time that we do
the next release, then we will still be able to update it.
No rush with that part of course, but that would be preferable.
Also i noticed a few things in your example which should be
changed. If it was in our SVN, then i could fix that.
...
It specifies the "user" mailing list as the maintainer.
Should be dev.
Substitute "Team" with "Project".
Can "programming-language" be Java and XML?
> > That works for me. However, i needed to adjust your
> > xml file because nothing is allowed before the
> > xml declaration.
>
> Yep, I noticed. I fixed that. Do you have this file online somewhere too? We
> just need a single copy.
No, i just got it from your Jira issue and did a local test.
Many thanks for getting this started.
-David
> [1] http://people.apache.org/~diwaker/doap.xml
>
> --
> Web/Blog/Gallery: http://floatingsun.net
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by Diwaker Gupta <di...@apache.org>.
On Wednesday 10 August 2005 1:04 am, David Crossley wrote:
> How about just linking to it from one of our pages
> or as a menu item in the Project tab.
Sounds fine. I've put the file up at [1] and I will maintain it there till we
need a better solution. I'll get this information into Codezoo asap.
> That works for me. However, i needed to adjust your
> xml file because nothing is allowed before the
> xml declaration.
Yep, I noticed. I fixed that. Do you have this file online somewhere too? We
just need a single copy.
[1] http://people.apache.org/~diwaker/doap.xml
--
Web/Blog/Gallery: http://floatingsun.net
Re: [jira] Updated: (FOR-617) Forrest DOAP file
Posted by David Crossley <cr...@apache.org>.
Diwaker Gupta (JIRA) wrote:
>
> Diwaker Gupta updated FOR-617:
> ------------------------------
>
> Attachment: doap.xml
>
> Initial version of the DOAP file for Forrest
>
> > Forrest DOAP file
> > -----------------
> >
> > Key: FOR-617
> > URL: http://issues.apache.org/jira/browse/FOR-617
> > Project: Forrest
> > Type: Improvement
> > Components: Documentation and website
> > Versions: 0.8-dev
> > Reporter: Diwaker Gupta
> > Assignee: 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?
How about just linking to it from one of our pages
or as a menu item in the Project tab.
That works for me. However, i needed to adjust your
xml file because nothing is allowed before the
xml declaration.
-David
[jira] Updated: (FOR-617) Forrest DOAP file
Posted by "Diwaker Gupta (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-617?page=all ]
Diwaker Gupta updated FOR-617:
------------------------------
Attachment: doap.xml
Initial version of the DOAP file for Forrest
> Forrest DOAP file
> -----------------
>
> Key: FOR-617
> URL: http://issues.apache.org/jira/browse/FOR-617
> Project: Forrest
> Type: Improvement
> Components: Documentation and website
> Versions: 0.8-dev
> Reporter: Diwaker Gupta
> Assignee: 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
[jira] Reopened: (FOR-617) Forrest DOAP file
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-617?page=all ]
David Crossley reopened FOR-617:
--------------------------------
Assignee: (was: Diwaker Gupta)
The codezoo is not up-to-date. Is it using our published DOAP descriptor?
See discussion here.
http://thread.gmane.org/gmane.text.xml.forrest.devel/15194/focus=15270
We are also now using this same file for projects.a.o
> 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
[jira] Commented: (FOR-617) Forrest DOAP file
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ 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
[jira] Closed: (FOR-617) Forrest DOAP file
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ross Gardler closed FOR-617.
----------------------------
Resolution: Fixed
Closed as recommended by Carlos Tejo
> Forrest DOAP file
> -----------------
>
> Key: FOR-617
> URL: https://issues.apache.org/jira/browse/FOR-617
> Project: Forrest
> Issue Type: Improvement
> Components: Documentation and website
> Affects Versions: 0.8
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FOR-617) Forrest DOAP file
Posted by "Carlos Tejo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622131#action_12622131 ]
Carlos Tejo commented on FOR-617:
---------------------------------
As far as codezoo is closed, maybe this issue could be close
> Forrest DOAP file
> -----------------
>
> Key: FOR-617
> URL: https://issues.apache.org/jira/browse/FOR-617
> Project: Forrest
> Issue Type: Improvement
> Components: Documentation and website
> Affects Versions: 0.8
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FOR-617) Forrest DOAP file
Posted by "Diwaker Gupta (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-617?page=all ]
Diwaker Gupta resolved FOR-617:
-------------------------------
Fix Version: 0.8-dev
Resolution: Fixed
The DOAP file is available at http://forrest.apache.org/doap.xml
I've heard from Mark Hedlund at O'Reilly:
"Thanks for creating the feed. We currently have a bug in the feed
parser, which we're working out shortly. Once that's fixed, new
version of Forrest will appear in CodeZoo very quickly."
> Forrest DOAP file
> -----------------
>
> Key: FOR-617
> URL: http://issues.apache.org/jira/browse/FOR-617
> Project: Forrest
> Type: Improvement
> Components: Documentation and website
> Versions: 0.8-dev
> Reporter: Diwaker Gupta
> Assignee: Diwaker Gupta
> Priority: Trivial
> Fix For: 0.8-dev
> 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
[jira] Commented: (FOR-617) Forrest DOAP file
Posted by "Gavin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FOR-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496270 ]
Gavin commented on FOR-617:
---------------------------
I submitted it yet again.
I emailed them yet again.
> Forrest DOAP file
> -----------------
>
> Key: FOR-617
> URL: https://issues.apache.org/jira/browse/FOR-617
> Project: Forrest
> Issue Type: Improvement
> Components: Documentation and website
> Affects Versions: 0.8
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (FOR-617) Forrest DOAP file
Posted by "David Crossley (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-617?page=all ]
David Crossley updated FOR-617:
-------------------------------
Fix Version/s: (was: 0.8-dev)
> 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