[Junit-devel] CVS: junit-ant-tests .classpath, NONE, 1.1 .project, NONE, 1.1 a.txt, NONE, 1.1 a, NONE, 1.1 todo.txt, NONE, 1.1

[David S. <ds...@us...>]

Update of /cvsroot/junit/junit-ant-tests
In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv3239

Added Files:
	.classpath .project a.txt a todo.txt 
Log Message:
initial check-in

--- NEW FILE: .classpath ---
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<classpathentry kind="src" path="src"/>
	<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
	<classpathentry kind="lib" path="lib/ant.jar" sourcepath="C:/bin/apache-ant-1.7.0/apache-ant-1.7.0-src.zip"/>
	<classpathentry kind="lib" path="lib/ant-launcher.jar"/>
	<classpathentry kind="lib" path="lib/popper-0.6.jar"/>
	<classpathentry kind="lib" path="lib/junit-4.4-snapshot-20070728-1307.jar"/>
	<classpathentry kind="lib" path="lib/hamcrest-all-SNAPSHOT.jar"/>
	<classpathentry kind="output" path="bin"/>
</classpath>

--- NEW FILE: .project ---
<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>junit-ant-tests</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.jdt.core.javabuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.jdt.core.javanature</nature>
	</natures>
</projectDescription>

--- NEW FILE: a.txt ---

--- NEW FILE: a ---

--- NEW FILE: todo.txt ---
- junit.properties are recreated in JUnitBuildXmlTest JUnitBuildTarget
- build file location is hard-coded
- Currently, we have to run with a special classpath entry to get javac.
  Can we avoid this?  Bake it in to the project?
- Bring other features from the junitbuild macro into JUnitBuildTarget