forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-450) Input plugins broken
Date Thu, 31 Mar 2005 17:18:18 GMT
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Thu, 31 Mar 2005 11:17 AM
       Body:
I'm a bit lost with this one.

It is almost certainly the sourcetype action that is causing the problem because only the
simplified-docbook plugin and another plugin I have locally that uses sourcetype is failing.

However, I don't think it can be the actuall java code since it works for sourcetype matches
in core.

Similarly I don't think it is anything to do with the plugins because they were working and
neither are showing any changes other than the unification of the catalog in the docbook plugin

Does anyone have any idea what is going on? I think I'm going blind to the real problem.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-450?page=comments#action_12194

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-450
    Summary: Input plugins broken
       Type: Bug

     Status: Unassigned
   Priority: Blocker

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

   Assignee: 
   Reporter: Ross Gardler

    Created: Mon, 28 Feb 2005 4:34 PM
    Updated: Thu, 31 Mar 2005 11:17 AM

Description:
Input plugins are not working in Head. Unfortunately I do not have the time to find the cause
right now. What I can say is that r153977 works fine.


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


Mime
View raw message