Removing static antclick build skeleton - antville now has its own build system.

build/antclick/README.txt

@@ -1,143 +0,0 @@
-==============
-ABOUT ANTCLICK
-==============
-
-Antclick is an integrated Helma/Antville package. It comes with 
-integrated web server and SQL database. It should run out of the 
-box although you may have to modify the start script. 
-
-This version of Antclick contains Mckoi as the embedded database 
-and Jetty as the embedded web server.
-
-Although Antcklick comes preconfigured with the Mckoi database, it 
-can easily be set up to run with other databases such as MySQL and 
-Oracle. It is also possible to configure it to use a fully featured 
-web server instead of the built-in web server. 
-
-
-======================
-INSTALLING AND RUNNING 
-======================
-
-Simply uncompress the content of the archive file into any place on 
-your hard disk. Start Helma on Windows by opening the file hop.bat. 
-On Unix systems open a terminal window, change to the Antclick 
-directory and type ./hop.sh.
-
-If you manage to get it running you should be able to connect your
-browser to http://127.0.0.1:8080/ (port 8080, that is). Now you can
-set up and configure your antville site.
-
-
-==============
-ABOUT ANTVILLE
-==============
-
-Antville is an open source project aimed to the development of an
-"easy to maintain and use" weblog-hosting system. It is not limited
-to just one weblog, it can easily host up to several hundred or
-thousand weblogs (the number of weblogs is more limited by the site
-owner's choice and server power than software limitations).
-
-Antville is entirely written in JavaScript and based on the Helma
-Object Publisher, a powerful and fast scriptable open source web
-application server (which itself is written in Java). Antville works
-with a relational database in the backend.
-
-Check out http://project.antville.org/ for more information.
-
-===========
-ABOUT HELMA
-===========
-
-Helma is a scriptable platform for creating dynamic, database backed
-web sites.
-
-Helma provides an easy way to map relational database tables to objects.
-These objects are wrapped with a layer of scripts and skins that allow
-them to be presented and manipulated over the web. The clue here is that
-both functions and skins work in an object oriented manner and force
-a clear separation between content, functionality and presentation.
-Actions are special functions that are callable over the web. Macros are
-special functions that expose functionality to the presentation layer. 
-Skins are pieces of layout that do not contain any application logic,
-only macro tags as placeholders for parts that are dynamically provided
-by the application.
-
-In short, Helma provides a one stop framework to create web applications 
-with less code and in shorter time than most of the other software out 
-there.
-
-===================
-SYSTEM REQUIREMENTS
-===================
-
-You need a Java virtual machine 1.3 or higher to run Helma.
-
-For Windows, Linux and Solaris you can get a Java runtime or development 
-kit from http://java.sun.com/j2se/downloads.html.
-
-If you are on Mac OS X, you already have a Java runtime that will work 
-well with Helma.
-
-Unfortunately, there is no Java 2 interpreter for Mac OS Classic, so
-you can't use Helma on Mac OS 9.
-
-============================
-INSTALLING AND RUNNING HELMA
-============================
-
-Simply unzip or untar the contents of the archive file into any place
-on your hard disk. Start Helma by invoking hop.bat or hop.sh from the
-command line, depending on whether you are on Windows or
-Linux/Unix/MacOSX. If the java command is not found, try setting the
-JAVA_HOME variable in the start script to the location of your Java
-installation.
-
-You may also want to have a look at the start script for other settings.
-You can adjust server wide settings in the server.properties file. For
-example, you should set the smtp property to the name of the SMTP server
-that Helma should use to send Email. Applications can be started or
-stopped by editing the apps.properties file through the web interface
-using the Management application that is part of Helma.
-
-If you manage to get it running you should be able to connect your
-browser to http://localhost:8080/ or http://127.0.0.1:8080/
-(port 8080 on the local machine, that is).
-
-Helma comes with a version of Jetty, a lightweight yet industrial strenth
-web server developed by Mortbay Consulting. See http://jetty.mortbay.com/
-for more information. While Jetty works well for deploying real web sites,
-you may want to run Helma behind an existing web server. This is most
-easily done by running Helma with the AJPv13 listener which allows you to
-plug Helma into any web server using the Apache mod_jk module. See
-http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html for more
-information on mod_jk and AJPv13.
-
-Finally, Helma can be plugged into Servlet containers using Servlet
-classes that communicate with Helma either directly or via Java RMI.
-(Be warned that these options may be harder to set up and maintain though,
-since most of the recent development efforts have been geared towards the
-mod_jk/AJPv13 setup.)
-
-
-=====================================
-DOCUMENTATION AND FURTHER INFORMATION
-=====================================
-
-Currently, documentation-in-progress is available online at
-http://helma.org/. We know that it sucks and hope to do some substantial
-improvments within the coming weeks and months.
-
-Your input is highly welcome. There is a mailing-list to discuss Helma at
-http://helma.org/lists/listinfo/hop. Don't hesitate to voice any questions,
-proposals, complaints, praise you may have on the list. We know we have
-a lot to do and to learn, and we're open to suggestions.
-
-For questions, comments or suggestions also feel free to contact
-antville@helma.org.
-
-
---
-
-Last modified on December 5, 2002 by Hannes Wallnoefer <hannes@helma.at>

build/antclick/apps.properties

@@ -1,13 +0,0 @@
-# List of apps to start.
-
-# mount antville as root application
-antville
-antville.mountpoint = /
-antville.static = static
-antville.staticMountpoint = /static
-
-# mount antville as /managehop to avoid 
-# conflict with antville's manage.hac action
-manage
-manage.mountpoint = /manage/hop
-

build/antclick/apps/antville/db.properties

@@ -1,5 +0,0 @@
-# Properties of antville datasource
-antville.url=jdbc:mckoi:local://./db.conf
-antville.driver=com.mckoi.JDBCDriver
-antville.user=admin
-antville.password=entwil

build/antclick/db.conf

@@ -1,318 +0,0 @@
-
-#######################################################
-#
-# Configuration options for the Mckoi SQL Database.
-#
-# NOTE: Lines starting with '#' are comments.
-#
-#######################################################
-
-#
-# database_path - The path where the database data files
-#   are located.
-#   See the 'root_path' configuration property for the
-#   details of how the engine resolves this to an
-#   absolute path in your file system.
-
-database_path=./data
-
-#
-# log_path - The path the log files are written.
-#   See the 'root_path' configuration property for the
-#   details of how the engine resolves this to an
-#   absolute path in your file system.
-#   The log path must point to a writable directory.  If
-#   no log files are to be kept, then comment out (or
-#   remove) the 'log_path' variable.
-
-log_path=./log
-
-#
-# root_path - If this is set to 'jvm' then the root
-#   path of all database files is the root path of the
-#   JVM (Java virtual machine) running the database
-#   engine.  If this property is set to 'configuration'
-#   or if it is not present then the root path is the
-#   path of this configuration file.
-#   This property is useful if you are deploying a
-#   database and need this configuration file to be the
-#   root of the directory tree of the database files.
-
-root_path=configuration
-#root_path=jvm
-
-#
-# jdbc_server_port - The TCP/IP port on this host where
-#   the database server is mounted.  The default port
-#   of the Mckoi SQL Database server is '9157'
-
-jdbc_server_port=9157
-
-#
-# ignore_case_for_identifiers - If enabled all
-#   identifiers are compared case insensitive.  If
-#   disabled (the default) the case of the identifier
-#   is important.
-#   For example, if a table called 'MyTable' contains
-#   a column called 'my_column' and this property is
-#   enabled, the identifier 'MYTAble.MY_COlumN' will
-#   correctly reference the column of the table.  If
-#   this property is disable a not found error is
-#   generated.
-#   This property is intended for compatibility with
-#   other database managements systems where the case
-#   of identifiers is not important.
-
-ignore_case_for_identifiers=disabled
-
-#
-# socket_polling_frequency - Mckoi SQL maintains a pool
-#   of connections on the server to manage dispatching
-#   of commands to worker threads.  All connections on
-#   the jdbc port are polled frequently, and ping
-#   requests are sent to determine if the TCP
-#   connection has closed or not.  This value determines
-#   how frequently the connections are polled via the
-#   'available' method.
-#   The value is the number of milliseconds between each
-#   poll of the 'available' method of the connections
-#   input socket stream.  Different Java implementations
-#   will undoubtedly require this value to be tweaked.
-#   A value of '3' works great on the Sun NT Java 1.2.2
-#   and 1.3 Java runtimes.
-#
-#   NOTE: This 'socket polling' module is a horrible hack
-#   and will be removed at some point when the threading
-#   performance improves or there is an API for non-
-#   blocking IO.  I'll probably write an alternative
-#   version for use with the improved Java version.
-
-socket_polling_frequency=3
-
-
-
-# ----- PLUG-INS -----
-
-#
-# database_services - The services (as a Java class) that
-#   are registered at database boot time.  Each service
-#   class is separated by a semi-colon (;) character.
-#   A database service must extend
-#   com.mckoi.database.ServerService
-#
-#database_services=mypackage.MyService
-
-#
-# function_factories - Registers one or more FunctionFactory
-#   classes with the database at boot time.  A
-#   FunctionFactory allows user-defined functions to be
-#   incorporated into the SQL language.  Each factory class
-#   is separated by a semi-colon (;) character.
-#
-#function_factories=mypackage.MyFunctionFactory
-
-#
-# The Java regular expression library to use.  Currently
-# the engine supports the Apache Jakarta regular expression
-# library, and the GNU LGPL regular expression library.
-# These two regular expression libraries can be found at the
-# following web sites:
-#
-# GNU Regexp: http://www.cacas.org/~wes/java/
-# Apache Regexp: http://jakarta.apache.org/regexp/
-#
-# The libraries provide similar functionality, however they
-# are released under a different license.  The GNU library
-# is released under the LGPL and is compatible with GPL
-# distributions of the database.  The Apache Jakarta library
-# is released under the Apache Software License and must not
-# be linked into GPL distributions.
-#
-# Use 'regex_library=gnu.regexp' to use the GNU library, or
-# 'regex_library=org.apache.regexp' to use the Apache
-# library.
-#
-# NOTE: To use either library, you must include the
-#  respective .jar package in the Java classpath.
-
-regex_library=gnu.regexp
-
-
-
-
-# ----- PERFORMANCE -----
-
-#
-# data_cache_size - The maximum amount of memory (in bytes)
-#   to allow the memory cache to grow to.  If this is set
-#   to a value < 4096 then the internal cache is disabled.
-#   It is recommended that a database server should provide
-#   a cache of 4 Megabytes (4194304).  A stand alone
-#   database need not have such a large cache.
-
-# data_cache_size=4194304
-data_cache_size=0
-
-#
-# max_cache_entry_size - The maximum size of an element
-#   in the data cache.  This is available for tuning
-#   reasons and the value here is dependant on the type
-#   of data being stored.  If your data has more larger
-#   fields that would benefit from being stored in the
-#   cache then increase this value from its default of
-#   8192 (8k).
-
-max_cache_entry_size=8192
-
-#
-# lookup_comparison_list - When this is set to 'enabled'
-#   the database attempts to optimize sorting by generating
-#   an internal lookup table that enables the database to
-#   quickly calculate the order of a column without having
-#   to look at the data directly.  The column lookup
-#   tables are only generated under certain query
-#   conditions.  Set this to 'disabled' if the memory
-#   resources are slim.
-
-lookup_comparison_list=enabled
-
-#
-# lookup_comparison_cache_size - The maximum amount of
-#   memory (in bytes) to allow for column lookup tables.
-#   If the maximum amount of memory is reached, the lookup
-#   table is either cached to disk so that is may be
-#   reloaded later if necessary, or removed from memory
-#   entirely.  The decision is based on how long ago the
-#   table was last used.
-#
-#   This property only makes sense if the
-#   'lookup_comparison_list' property is enabled.
-#
-# NOTE: This property does nothing yet...
-
-lookup_comparison_cache_size=2097152
-
-#
-# index_cache_size - The maximum amount of memory (in
-#   bytes) to allow for the storage of column indices.
-#   If the number of column indices in memory reaches
-#   this memory threshold then the index blocks are
-#   cached to disk.
-#
-# ISSUE: This is really an implementation of internal
-#   memory page caching but in Java.  Is it necessary?
-#   Why not let the OS handle it with its page file?
-#
-# NOTE: This property does nothing yet...
-
-index_cache_size=2097152
-
-#
-# max_worker_threads - The maximum number of worker
-#   threads that can be spawned to handle incoming
-#   requests.  The higher this number, the more
-#   'multi-threaded' the database becomes.  The
-#   default setting is '4'.
-
-maximum_worker_threads=4
-
-#
-# soft_index_storage - If this is set to 'enabled', the
-#   database engine will keep all column indices behind a
-#   soft reference.  This enables the JVM garbage collector
-#   to reclaim memory used by the indexing system if the
-#   memory is needed.
-#
-#   This is useful for an embedded database where requests
-#   are rare.  When the database part is idle, the index 
-#   memory (that can take up significant space for large
-#   tables) is reclaimed for other uses.  For a dedicated
-#   database server it is recommended this is disabled.
-#
-#   Enable this if you need the engine to use less memory.
-#   I would recommend the config property
-#   'lookup_comparison_list' is disabled if this is enabled.
-#   The default setting is 'disabled'.
-
-soft_index_storage=disabled
-
-#
-# dont_synch_filesystem - If this is enabled, the engine
-#   will not synchronize the file handle when a table change
-#   is committed.  This will mean the data is not as
-#   safe but the 'commit' command will work faster.  If this
-#   is enabled, there is a chance that committed changes will
-#   not get a chance to flush to the file system if the
-#   system crashes.
-#
-#   It is recommended this property is left commented out.
-#
-#dont_synch_filesystem=enabled
-
-#
-# transaction_error_on_dirty_select - If this is disabled
-#   the 4th conflict (dirty read on modified table) will
-#   not be detected.  This has transactional consequences
-#   that will cause data modifications to sometimes be
-#   out of syncronization.  For example, one transaction
-#   adds an entry, and another concurrent transaction
-#   deletes all entries.  If this is disabled this
-#   conflict will not be detected.  The table will end up
-#   with the one entry added after commit.
-#
-#   It is recommended this property is left commented out.
-#
-#transaction_error_on_dirty_select=disabled
-
-
-
-
-
-
-# ----- SPECIAL -----
-
-#
-# read_only - If this is set to 'enabled' then the database
-#   is readable and not writable.  You may boot a database
-#   in read only mode from multiple VM's.  If the database
-#   data files are stored on a read only medium such as a
-#   CD, then the property must be enabled else it will not
-#   be possible to boot the database.
-#   ( Uncomment the line below for read only mode )
-#read_only=enabled
-
-
-
-
-# ----- DEBUGGING -----
-
-#
-# debug_log_file - The file that is used to log all debug
-#   information.  This file is stored in the 'log_path'
-#   path.
-
-debug_log_file=debug.log
-
-#
-# debug_level - The minimum debug level of messages that
-#   are written to the log file.  Reducing this number
-#   will cause more debug information to be written to
-#   the log.
-#     10 = INFORMATION
-#     20 = WARNINGS
-#     30 = ALERTS
-#     40 = ERRORS
-
-debug_level=20
-
-#
-# table_lock_check - If this is enabled, every time a
-#   table is accessed a check is performed to ensure that
-#   the table owns the correct locks.  If a lock assertion
-#   fails then an error is generated in the log file.
-#   This should not be enabled in a production system
-#   because the lock assertion check is expensive. However
-#   it should be used during testing because it helps to
-#   ensure locks are being made correctly.
-
-table_lock_check=disabled

build/antclick/db.properties

@@ -1,16 +0,0 @@
-# This is where you specify relational data sources to
-# map Helma types to relational databases.
-#
-# If you want to define a data source just for one
-# application, simply copy the db.properties file to
-# the application directory.
-#
-# The actual mapping of types is done in the
-# type.properties file in the prototype directories.
-# 
-
-# Properties of JDBC data sources
-myDataSource.url = jdbc:mysql://db.domain.com/space
-myDataSource.driver = org.gjt.mm.mysql.Driver
-myDataSource.user = username
-myDataSource.password = xyz

build/antclick/hop.bat

@@ -1,79 +0,0 @@
-@echo off
-rem Batch file for Starting Helma with a JDK-like virtual machine.
-
-rem To add jar files to the classpath, simply place them into the 
-rem lib/ext directory of this Helma installation.
-
-:: Initialize variables
-:: (don't touch this section)
-set JAVA_HOME=
-set HOP_HOME=
-set HTTP_PORT=
-set XMLRPC_PORT=
-set AJP13_PORT=
-set RMI_PORT=
-set OPTIONS=
-
-:: Set TCP ports for Helma servers
-:: (comment/uncomment to de/activate)
-set HTTP_PORT=8080
-rem set XMLRPC_PORT=8081
-rem set AJP13_PORT=8009
-rem set RMI_PORT=5050
-
-:: Uncomment to set HOP_HOME
-rem set HOP_HOME=c:\program files\helma
-
-:: Uncomment to set JAVA_HOME variable
-rem set JAVA_HOME=c:\program files\java
-
-:: Uncomment to pass options to the Java virtual machine
-rem set JAVA_OPTIONS=-server -Xmx128m
-
-:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
-:::::: No user configuration needed below this line :::::::
-:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
-
-:: Setting the script path
-set INSTALL_DIR=%~d0%~p0
-
-:: Using JAVA_HOME variable if defined. Otherwise,
-:: Java executable must be contained in PATH variable
-if "%JAVA_HOME%"=="" goto default
-   set JAVACMD=%JAVA_HOME%\bin\java
-   goto end
-:default
-   set JAVACMD=java
-:end
-
-:: Setting HOP_HOME to script path if undefined
-if "%HOP_HOME%"=="" (
-   set HOP_HOME=%INSTALL_DIR%
-)
-cd %HOP_HOME%
-
-
-:: Setting Helma server options
-if not "%HTTP_PORT%"=="" (
-   echo Starting HTTP server on port %HTTP_PORT%
-   set OPTIONS=%OPTIONS% -w %HTTP_PORT%
-)
-if not "%XMLRPC_PORT%"=="" (
-   echo Starting XML-RPC server on port %XMLRPC_PORT%
-   set OPTIONS=%OPTIONS% -x %XMLRPC_PORT%
-)
-if not "%AJP13_PORT%"=="" (
-   echo Starting AJP13 listener on port %AJP13_PORT%
-   set OPTIONS=%OPTIONS% -jk %AJP13_PORT%
-)
-if not "%RMI_PORT%"=="" (
-   echo Starting RMI server on port %RMI_PORT%
-   set OPTIONS=%OPTIONS% -p %RMI_PORT%
-)
-if not "%HOP_HOME%"=="" (
-   echo Serving applications from %HOP_HOME%
-   set OPTIONS=%OPTIONS% -h "%HOP_HOME%
-)
-
-:: Invoking the Java virtual machine
-%JAVACMD% %JAVA_OPTIONS% -jar "%INSTALL_DIR%\launcher.jar" %OPTIONS%

build/antclick/hop.sh

@@ -1,80 +0,0 @@
-#!/bin/sh
-# Shell script for starting Helma with a JDK-like virtual machine.
-
-# To add JAR files to the classpath, simply place them into the
-# lib/ext directory.
-
-# uncomment to set JAVA_HOME variable
-# JAVA_HOME=/usr/lib/java
-
-# uncomment to set HOP_HOME, otherwise we get it from the script path
-# HOP_HOME=/usr/local/helma
-
-# options to pass to the Java virtual machine
-# JAVA_OPTIONS="-server -Xmx128m"
-
-# Set TCP ports for Helma servers
-# (comment/uncomment to de/activate)
-HTTP_PORT=8080
-# XMLRPC_PORT=8081
-# AJP13_PORT=8009
-# RMI_PORT=5050
-
-###########################################################
-###### No user configuration needed below this line #######
-###########################################################
-
-# if JAVA_HOME variable is set, use it. Otherwise, Java executable
-# must be contained in PATH variable.
-if [ "$JAVA_HOME" ]; then
-   JAVACMD="$JAVA_HOME/bin/java"
-else
-   JAVACMD=java
-fi
-
-
-# If JAVA_HOME is set, check if java command is executable
-if [ $JAVA_HOME -a ! -x $JAVACMD ] ; then
-   echo "Warning: JAVA_HOME variable may be set incorrectly:"
-   echo "         No executable found at $JAVACMD"
-fi
-
-# Get the Helma installation directory
-INSTALL_DIR="${0%/*}"
-cd $INSTALL_DIR
-INSTALL_DIR=$PWD
-
-# get HOP_HOME variable if it isn't set
-if [ -z "$HOP_HOME" ]; then
-  # try to get HOP_HOME from script file and pwd
-  # strip everyting behind last slash
-  HOP_HOME="${0%/*}"
-  cd $HOP_HOME
-  HOP_HOME=$PWD
-else
-  cd $HOP_HOME
-fi
-echo "Starting Helma in directory $HOP_HOME"
-
-if [ "$HTTP_PORT" ]; then
-   SWITCHES="$SWITCHES -w $HTTP_PORT"
-   echo Starting HTTP server on port $HTTP_PORT
-fi
-if [ "$XMLRPC_PORT" ]; then
-   SWITCHES="$SWITCHES -x $XMLRPC_PORT"
-   echo Starting XML-RPC server on port $XMLRPC_PORT
-fi
-if [ "$AJP13_PORT" ]; then
-   SWITCHES="$SWITCHES -jk $AJP13_PORT"
-   echo Starting AJP13 listener on port $AJP13_PORT
-fi
-if [ "$RMI_PORT" ]; then
-   SWITCHES="$SWITCHES -p $RMI_PORT"
-   echo Starting RMI server on port $RMI_PORT
-fi
-if [ "$HOP_HOME" ]; then
-   SWITCHES="$SWITCHES -h $HOP_HOME"
-fi
-
-# Invoke the Java VM
-$JAVACMD $JAVA_OPTIONS -jar "$INSTALL_DIR/launcher.jar" $SWITCHES

build/antclick/license.txt

@@ -1,50 +0,0 @@
- Copyright (c) 1999-2001 Helma Project. All rights reserved.
-
- Redistribution and use in source and binary forms, with or without
- modification, are permitted provided that the following conditions
- are met:
-
- 1. Redistributions of source code must retain the above copyright
-    notice, this list of conditions and the following disclaimer.
-
- 2. Redistributions in binary form must reproduce the above copyright
-    notice, this list of conditions and the following disclaimer in
-    the documentation and/or other materials provided with the
-    distribution.
-
- 3. The end-user documentation included with the redistribution,
-    if any, must include the following acknowledgment:
-    "This product includes software developed by the Helma Project
-    for use in the Helma Object Publisher (http://www.helma.org/)."
-    Alternately, this acknowledgment may appear in the software itself,
-    if and wherever such third-party acknowledgments normally appear.
-
- 4. The names "Helma" and "Hop" must not be used to endorse or
-    promote products derived from this software without prior written
-    permission. For written permission, please contact
-    helma@helma.org.
-
- 5. Products derived from this software may not be called "Helma"
-    or "Hop", nor may "Helma" or "Hop" appear in their name, without
-    prior written permission of the Helma Project Group.
-
- 6. We ask you to give credit to the Helma Project for sites which build
-    upon Helma. This would normally consist of a text or graphic link
-    to http://helma.org/ with the line "Powered by Helma" somewhere on the
-    site. While it is not a breach of this license to omit this, it's a
-    great way for you to make help the Helma Project to continue
-    to flourish and grow.
-
-
- THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
- WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
- DISCLAIMED. IN NO EVENT SHALL THE HELMA PROJECT OR ITS
- CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
- SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
- NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
- LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
- HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
- STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
- ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
- OF THE POSSIBILITY OF SUCH DAMAGE.

build/antclick/server.properties

@@ -1,27 +0,0 @@
-# The SMTP server to use for sending mails. Set and
-# uncomment this line before trying to send mails from
-# Helma applications.
-#
-# smtp=mail.yourdomain.com
-
-
-# Some examples for server-wide locale settings
-# (please refer to http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html
-# for country codes, resp. http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt
-# for language codes).
-#
-# country = AT
-# language = de
-#
-# country = UK
-# language = en
-#
-# country = FR
-# language = fr
-#
-# country = CZ
-# language = cs
-
-# list ip addresses for admin-application here:
-allowAdmin=127.0.0.1, 192.168.0.1
-