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/05/27 13:25:55 UTC

[JIRA] Updated: (FOR-508) "available-skins" command returns incorrect information

The following issue has been updated:

    Updater: Ross Gardler (mailto:ross@saafe.org)
       Date: Fri, 27 May 2005 6:25 AM
    Comment:
Reclassified to be fixed in the 0.7 release
    Changes:
             type changed from Task to Bug
             priority changed from Minor to Major
             Component changed to Skins (general issues)
             Fix Version changed to 0.7-dev
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-508
    Summary: "available-skins" command returns incorrect information
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Forrest
 Components: 
             Skins (general issues)
   Fix Fors:
             0.7-dev
   Versions:
             0.6

   Assignee: 
   Reporter: Maurice Lanselle

    Created: Fri, 27 May 2005 5:27 AM
    Updated: Fri, 27 May 2005 6:25 AM
Environment: Win XP (but I don't think that matters in this case).

Description:
"Forrest available-skins" command returns incorrect information, including a skin (crust) which no longer exists, and omitting some (plain-dev, leather-dev) which are available (but not fully supported).


---------------------------------------------------------------------
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