forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-346) Set up Catalog Entity Resolver for other tools
Date Tue, 02 Nov 2004 18:09:38 GMT
The following comment has been added to this issue:

     Author: Dave Brondsema
    Created: Tue, 2 Nov 2004 12:09 PM
       Body:
Most XML editors should have their own documentation concerning using catalogs.  All you have
to do is follow that and point it at catalog or catalog.xcat (depending which format of catalogs
the editor supports).

Eclipse by itself does not support XML editing.  The Eclipse XMLBuddy plugin (last I checked)
did not support using catalogs at all.  I think the Eclipse WebTools project (http://eclipse.org/webtools/)
has an XML editor.  It had some bugginess when first available, but they now have a milestone
download available.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-346?page=comments#action_11751

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-346
    Summary: Set up Catalog Entity Resolver for other tools
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Forrest website

   Assignee: 
   Reporter: Clay Leeds

    Created: Tue, 2 Nov 2004 11:58 AM
    Updated: Tue, 2 Nov 2004 12:09 PM
Environment: all

Description:
Could someone who knows how (i.e., not me...) write up documentation on how to set up the
Catalog Entity Resolver for other tools (e.g., eclipse.org 2.x & 3.x, eclipse.org w/ XMLBuddy
& other plugins, BBEdit, SubEthaEdit, etc.). Thanks!


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