[RavenclawDev 210] [7] JavaTTY: moved to javaTTY
svetlana@edam.speech.cs.cmu.edu
svetlana at edam.speech.cs.cmu.edu
Sun Jan 14 11:39:35 EST 2007
An HTML attachment was scrubbed...
URL: http://mailman.srv.cs.cmu.edu/pipermail/ravenclaw-developers/attachments/20070114/f1e526f7/attachment.html
-------------- next part --------------
Deleted: .cvsignore
===================================================================
--- .cvsignore 2007-01-14 16:33:34 UTC (rev 6)
+++ .cvsignore 2007-01-14 16:39:35 UTC (rev 7)
@@ -1,2 +0,0 @@
-build
-dist
Copied: JavaTTY/bsh-core-2.0b4.jar (from rev 5, bsh-core-2.0b4.jar)
===================================================================
(Binary files differ)
Copied: JavaTTY/bsh-util-2.0b4.jar (from rev 5, bsh-util-2.0b4.jar)
===================================================================
(Binary files differ)
Copied: JavaTTY/build (from rev 5, build)
Copied: JavaTTY/build.xml (from rev 5, build.xml)
===================================================================
--- JavaTTY/build.xml (rev 0)
+++ JavaTTY/build.xml 2007-01-14 16:39:35 UTC (rev 7)
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!-- You may freely edit this file. See commented blocks below for -->
+<!-- some examples of how to customize the build. -->
+<!-- (If you delete it and reopen the project it will be recreated.) -->
+<project name="JavaTTY" default="default" basedir=".">
+ <description>Builds, tests, and runs the project JavaTTY.</description>
+ <import file="nbproject/build-impl.xml"/>
+ <!--
+
+ There exist several targets which are by default empty and which can be
+ used for execution of your tasks. These targets are usually executed
+ before and after some main targets. They are:
+
+ -pre-init: called before initialization of project properties
+ -post-init: called after initialization of project properties
+ -pre-compile: called before javac compilation
+ -post-compile: called after javac compilation
+ -pre-compile-single: called before javac compilation of single file
+ -post-compile-single: called after javac compilation of single file
+ -pre-compile-test: called before javac compilation of JUnit tests
+ -post-compile-test: called after javac compilation of JUnit tests
+ -pre-compile-test-single: called before javac compilation of single JUnit test
+ -post-compile-test-single: called after javac compilation of single JUunit test
+ -pre-jar: called before JAR building
+ -post-jar: called after JAR building
+ -post-clean: called after cleaning build products
+
+ (Targets beginning with '-' are not intended to be called on their own.)
+
+ Example of inserting an obfuscator after compilation could look like this:
+
+ <target name="-post-compile">
+ <obfuscate>
+ <fileset dir="${build.classes.dir}"/>
+ </obfuscate>
+ </target>
+
+ For list of available properties check the imported
+ nbproject/build-impl.xml file.
+
+
+ Another way to customize the build is by overriding existing main targets.
+ The targets of interest are:
+
+ -init-macrodef-javac: defines macro for javac compilation
+ -init-macrodef-junit: defines macro for junit execution
+ -init-macrodef-debug: defines macro for class debugging
+ -init-macrodef-java: defines macro for class execution
+ -do-jar-with-manifest: JAR building (if you are using a manifest)
+ -do-jar-without-manifest: JAR building (if you are not using a manifest)
+ run: execution of project
+ -javadoc-build: Javadoc generation
+ test-report: JUnit report generation
+
+ An example of overriding the target for project execution could look like this:
+
+ <target name="run" depends="JavaTTY-impl.jar">
+ <exec dir="bin" executable="launcher.exe">
+ <arg file="${dist.jar}"/>
+ </exec>
+ </target>
+
+ Notice that the overridden target depends on the jar target and not only on
+ the compile target as the regular run target does. Again, for a list of available
+ properties which you can use, check the target you are overriding in the
+ nbproject/build-impl.xml file.
+
+ -->
+</project>
Copied: JavaTTY/dist (from rev 5, dist)
Copied: JavaTTY/jiu.jar (from rev 5, jiu.jar)
===================================================================
(Binary files differ)
Copied: JavaTTY/nbproject (from rev 5, nbproject)
Copied: JavaTTY/run.sh (from rev 5, run.sh)
===================================================================
--- JavaTTY/run.sh (rev 0)
+++ JavaTTY/run.sh 2007-01-14 16:39:35 UTC (rev 7)
@@ -0,0 +1 @@
+java -classpath "dist/JavaTTY.jar;../../Libraries/Galaxy/jars/galaxy.jar;jiu.jar;bsh-core-2.0b4.jar;bsh-util-2.0b4.jar" edu.cmu.ravenclaw.javatty.JavaTTYServer -port 11002
\ No newline at end of file
Deleted: README
===================================================================
--- README 2007-01-14 16:33:34 UTC (rev 6)
+++ README 2007-01-14 16:39:35 UTC (rev 7)
@@ -1,4 +0,0 @@
-Original code taken from Xiaoping Jia's "Object Oriented Software
-Development using Java". Chapter 9. Iteration 4.
-http://se.cs.depaul.edu/Java/chap09.html
-
Deleted: Thumbs.db
===================================================================
(Binary files differ)
Deleted: botlocs.txt
===================================================================
--- botlocs.txt 2007-01-14 16:33:34 UTC (rev 6)
+++ botlocs.txt 2007-01-14 16:39:35 UTC (rev 7)
@@ -1 +0,0 @@
-pinky:-496.227:-541.485:1.61928
Deleted: bsh-core-2.0b4.jar
===================================================================
(Binary files differ)
Deleted: bsh-util-2.0b4.jar
===================================================================
(Binary files differ)
Deleted: build.xml
===================================================================
--- build.xml 2007-01-14 16:33:34 UTC (rev 6)
+++ build.xml 2007-01-14 16:39:35 UTC (rev 7)
@@ -1,69 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!-- You may freely edit this file. See commented blocks below for -->
-<!-- some examples of how to customize the build. -->
-<!-- (If you delete it and reopen the project it will be recreated.) -->
-<project name="JavaTTY" default="default" basedir=".">
- <description>Builds, tests, and runs the project JavaTTY.</description>
- <import file="nbproject/build-impl.xml"/>
- <!--
-
- There exist several targets which are by default empty and which can be
- used for execution of your tasks. These targets are usually executed
- before and after some main targets. They are:
-
- -pre-init: called before initialization of project properties
- -post-init: called after initialization of project properties
- -pre-compile: called before javac compilation
- -post-compile: called after javac compilation
- -pre-compile-single: called before javac compilation of single file
- -post-compile-single: called after javac compilation of single file
- -pre-compile-test: called before javac compilation of JUnit tests
- -post-compile-test: called after javac compilation of JUnit tests
- -pre-compile-test-single: called before javac compilation of single JUnit test
- -post-compile-test-single: called after javac compilation of single JUunit test
- -pre-jar: called before JAR building
- -post-jar: called after JAR building
- -post-clean: called after cleaning build products
-
- (Targets beginning with '-' are not intended to be called on their own.)
-
- Example of inserting an obfuscator after compilation could look like this:
-
- <target name="-post-compile">
- <obfuscate>
- <fileset dir="${build.classes.dir}"/>
- </obfuscate>
- </target>
-
- For list of available properties check the imported
- nbproject/build-impl.xml file.
-
-
- Another way to customize the build is by overriding existing main targets.
- The targets of interest are:
-
- -init-macrodef-javac: defines macro for javac compilation
- -init-macrodef-junit: defines macro for junit execution
- -init-macrodef-debug: defines macro for class debugging
- -init-macrodef-java: defines macro for class execution
- -do-jar-with-manifest: JAR building (if you are using a manifest)
- -do-jar-without-manifest: JAR building (if you are not using a manifest)
- run: execution of project
- -javadoc-build: Javadoc generation
- test-report: JUnit report generation
-
- An example of overriding the target for project execution could look like this:
-
- <target name="run" depends="JavaTTY-impl.jar">
- <exec dir="bin" executable="launcher.exe">
- <arg file="${dist.jar}"/>
- </exec>
- </target>
-
- Notice that the overridden target depends on the jar target and not only on
- the compile target as the regular run target does. Again, for a list of available
- properties which you can use, check the target you are overriding in the
- nbproject/build-impl.xml file.
-
- -->
-</project>
Deleted: jiu.jar
===================================================================
(Binary files differ)
Deleted: run.sh
===================================================================
--- run.sh 2007-01-14 16:33:34 UTC (rev 6)
+++ run.sh 2007-01-14 16:39:35 UTC (rev 7)
@@ -1 +0,0 @@
-java -classpath "dist/JavaTTY.jar;../../Libraries/Galaxy/jars/galaxy.jar;jiu.jar;bsh-core-2.0b4.jar;bsh-util-2.0b4.jar" edu.cmu.ravenclaw.javatty.JavaTTYServer -port 11002
\ No newline at end of file
More information about the Ravenclaw-developers
mailing list