You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2005/01/07 01:05:05 UTC

[JIRA] Created: (FOR-416) input/output formats documented

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-416

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-416
    Summary: input/output formats documented
       Type: Task

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Documentation and website

   Assignee: 
   Reporter: Dave Brondsema

    Created: Thu, 6 Jan 2005 6:04 PM
    Updated: Thu, 6 Jan 2005 6:04 PM

Description:
Clearly document all possible input and output formats, and any advantages and disadvantages of them.  IMHO, I envision this as a new, short page, rather than letting it get lost in any existing page (although it would be good also to modifying the front page's quick steps and Using Forrest to show there are more options than XML for source).


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[JIRA] Updated: (FOR-416) input/output formats documented

Posted by is...@cocoondev.org.
The following issue has been updated:

    Updater: David Crossley (mailto:crossley@apache.org)
       Date: Thu, 17 Mar 2005 12:18 AM
    Changes:
             Version changed to HEAD
             Fix Version changed to 0.7
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org//browse/FOR-416?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-416

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-416
    Summary: input/output formats documented
       Type: Task

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Documentation and website
   Fix Fors:
             0.7
   Versions:
             HEAD

   Assignee: 
   Reporter: Dave Brondsema

    Created: Thu, 6 Jan 2005 6:04 PM
    Updated: Thu, 17 Mar 2005 12:18 AM

Description:
Clearly document all possible input and output formats, and any advantages and disadvantages of them.  IMHO, I envision this as a new, short page, rather than letting it get lost in any existing page (although it would be good also to modifying the front page's quick steps and Using Forrest to show there are more options than XML for source).


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[JIRA] Commented: (FOR-416) input/output formats documented

Posted by is...@cocoondev.org.
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Thu, 6 Jan 2005 7:03 PM
       Body:
http://issues.cocoondev.org/browse/FOR-340 includes the need to have plugins generate their documentation and publish it to the website. I have this (almost) working on my hard drive, some problems with inconsitent line endings that I have not had time to track down fully. Once this is done then full documentation will be generated when a plugin is deployed.

However, we also need a simple page with summary information as this issue suggests. Perhaps this information could be included in the plugins.xml and aggregated with a document that describes the internal formats.

---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-416?page=comments#action_11967

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-416

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-416
    Summary: input/output formats documented
       Type: Task

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Documentation and website

   Assignee: 
   Reporter: Dave Brondsema

    Created: Thu, 6 Jan 2005 6:04 PM
    Updated: Thu, 6 Jan 2005 7:03 PM

Description:
Clearly document all possible input and output formats, and any advantages and disadvantages of them.  IMHO, I envision this as a new, short page, rather than letting it get lost in any existing page (although it would be good also to modifying the front page's quick steps and Using Forrest to show there are more options than XML for source).


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[JIRA] Closed: (FOR-416) input/output formats documented

Posted by is...@cocoondev.org.
Message:

   The following issue has been closed.

   Resolver: Ross Gardler
       Date: Thu, 5 May 2005 10:16 AM

There is an up-to-date index file at http://forrest.apache.org/0.7/docs/plugins/index.html

This will be automatically generated and updated when a plugin is deployed (new buildfile not yet committed due to some problems with plugin docs, however this is another issue on the tracker so closing this one).
---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-416

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-416
    Summary: input/output formats documented
       Type: Task

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Forrest
 Components: 
             Documentation and website
   Fix Fors:
             0.7-dev
   Versions:
             0.7-dev

   Assignee: Ross Gardler
   Reporter: Dave Brondsema

    Created: Thu, 6 Jan 2005 6:04 PM
    Updated: Thu, 5 May 2005 10:16 AM

Description:
Clearly document all possible input and output formats, and any advantages and disadvantages of them.  IMHO, I envision this as a new, short page, rather than letting it get lost in any existing page (although it would be good also to modifying the front page's quick steps and Using Forrest to show there are more options than XML for source).


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira