[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xindice-dev
Subject:    [Xindice Wiki] Updated:  AntXindice
From:       xindice-cvs () xml ! apache ! org
Date:       2004-02-21 9:59:20
Message-ID: 200402210959.i1L9xKU2017950 () mailer ! progressive-comp ! com
[Download RAW message or body]

   Date: 2004-02-21T01:59:30
   Editor: 213.122.194.80 <>
   Wiki: Xindice Wiki
   Page: AntXindice
   URL: http://wiki.apache.org/xindice/AntXindice

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,30 +1,34 @@
 There are a few methods of using Ant with Xindice;
 
 = XindiceDeploymentTask =
-''jim.fuller@ruminate.co.uk''
+''by jim.fuller@ruminate.co.uk''
 
 Fortunately Xindice ships with its own Ant task called DeploymentTask. To use it in \
your ant build scripts you will first need to declare a TaskDef statement.  
 1) place the following before your target definitions
 
+{{{
   <taskdef name="xindice" classname="org.apache.xindice.tools.DeploymentTask"/>
+}}}
 
 2) here are some examples of using the Ant task
 
-export
+'''export'''
 {{{
 <xindice home="E:\java\xindice" Collection="xmldb:xindice://127.0.0.1:8080/db/log/" 
 Activity="export" Path="c:\test\"/>
 }}}
 
-import
+'''import'''
+{{{
 <xindice home="E:\java\xindice" \
Collection="xmldb:xindice://127.0.0.1:8080/db/somecollection/"   Activity="import" \
                Path="c:\test\"/>
-
+}}}
 Check out the commands.xml file contained in /config directory, which lists all the \
available commands for this task.   
 Here is an example ant build.xml file which uses the useful Macrodef task to create \
xindice tasks.  
+{{{
 <?xml version="1.0"?>
 <project name="test xindice deployment task" default="test" basedir=".">
 <description>
@@ -71,7 +75,7 @@
 </target>
 
 </project>
-
+}}}
 
 
 = Xindice Ant Task v.1alpha =
@@ -84,13 +88,16 @@
 usage:
 
 1) add com.example.XindiceAntTask using taskdef to make it available to Ant
+{{{
 <taskdef classpath="${java.class.path}" name="xindice" \
classname="com.example.XindiceAntTask" /> +}}}
 
 There is no reason you need to keep the namespace, all classes are in \
com.example....possibly with a better version this Xindice Task may find itself \
within Xindice or Ant optional.  
 
 2) The following target  is an example of the syntax used when adding and removing \
documents and collections  
+{{{
     <target name="test-xindice-ant-task" description="test XindiceAntTask">
 
 	    <taskdef classpath="${java.class.path}" name="xindice" \
classname="com.epinx.xindice.XindiceAntTask"/> @@ -112,6 +119,7 @@
 	    </xindice>
 
     </target>
+}}}
 
 Feel free to take this code and make better, but please post back to either here or \
the Xindice list.   


[prev in list] [next in list] [prev in thread] [next in thread]