aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--build.xml69
-rw-r--r--manifest.mf3
-rw-r--r--www/index.html45
3 files changed, 0 insertions, 117 deletions
diff --git a/build.xml b/build.xml
deleted file mode 100644
index 9e27c9a..0000000
--- a/build.xml
+++ /dev/null
@@ -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="typecast" default="default" basedir=".">
- <description>Builds, tests, and runs the project typecast.</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="typecast-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>
diff --git a/manifest.mf b/manifest.mf
deleted file mode 100644
index 328e8e5..0000000
--- a/manifest.mf
+++ /dev/null
@@ -1,3 +0,0 @@
-Manifest-Version: 1.0
-X-COMMENT: Main-Class will be added automatically by build
-
diff --git a/www/index.html b/www/index.html
deleted file mode 100644
index 6a80a18..0000000
--- a/www/index.html
+++ /dev/null
@@ -1,45 +0,0 @@
-<html>
-<head>
-<title>Project Home Page</title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-<body bgcolor="#FFFFFF" text="#000000">
-<h1>Default project home page </h1>
-<p>Congratulations on your new java.net project! </p>
-<p>This page is the home page for your new project. This content is appearing
- because you have selected the option <b>Use project index.html</b>. To edit
- the information displayed on this page, just use CVS to check out your project's
- CVS repository and edit index.html in directory www. You can get more information
- on how to set-up your local CVS client, click on <b>Version Control</b> on the
- left nav bar. </p>
-<p>If you don't want to use CVS to manage your home page, click on the <b>Edit
- project</b> link on this page and unclick the option <b>Use project index.html</b>.
- Your project home page contents will be generated from the <b>Edit project</b>
- field <b>Description</b>. Edit the text on that field to change your home page
- contents. Click on <b>Submit changes</b> to save your edits. </p>
-<p>If you are looking for <a href="https://java-net.dev.java.net/ProjectPages.html#templates">sample
- home page templates</a>, check out the <a href="https://java-net.dev.java.net/ProjectPages.html">java.net
- Project Starter Kit</a>. Copy either of the templates into your project's html
- to get started on your project's home page. </p>
-<p>You can find lots of helpful information in the Starter Kit to get your project
- started. Some of the things you will find in there include:</p>
-<ul>
- <li>Hints on how to <a href="https://java-net.dev.java.net/ProjectPages.html#pages">set-up
- your project's</a> home page</li>
- <li>Ideas on how to <a href="https://java-net.dev.java.net/ProjectPages.html#publicity">publicize
- your project</a> including RSS feeds</li>
- <li>Hints on <a href="https://java-net.dev.java.net/pagedesign.html">project
- page HTML</a></li>
- <li>Setting up project <a href="https://java-net.dev.java.net/ProjectPages.html#wiki">wiki
- pages</a></li>
- <li>And places to go if <a href="https://java-net.dev.java.net/ProjectPages.html#feedback">you
- have questions</a>.</li>
-</ul>
-<p>Remember that you will attract more new members and your project team will
- work more effectively if you, as the project owner, supply sufficient information
- about your project for visitors to your project space. Good luck with your new
- project! </p>
-</body>
-</html>
-