Finished 1.0.0 of libpit. Other housekeeping performed as well.

Moved issue for the PIT project to top-level.
Created top-level versioning properties and project properties for pit-cli
This commit is contained in:
Jonathan Bernard
2010-02-13 21:30:31 -06:00
parent f3f30237b2
commit bb56b706f8
21 changed files with 116 additions and 56 deletions

View File

@ -1,7 +1,25 @@
<project name="Personal Issue Tracker">
<property file="../version.properties"/>
<property file="project.properties"/>
<property environment="env"/>
<path id="groovy.libs">
<fileset dir="${env.GROOVY_HOME}/lib">
<include name="**/*.jar"/>
</fileset>
</path>
<path id="groovyc.classpath">
<path refid="groovy.libs"/>
<fileset dir="${lib.dir}">
<include name="**/*.jar"/>
</fileset>
</path>
<taskdef name="groovyc"
classname="org.codehaus.groovy.ant.Groovyc"
classpathref="groovy.libs"/>
<target name="init">
<fail
unless="env.GROOVY_HOME"
@ -9,38 +27,59 @@
<echo message="GROOVY_HOME: ${env.GROOVY_HOME}"/>
</target>
<path id="groovy.libs">
<fileset dir="${env.GROOVY_HOME}/lib">
<include name="**/*.jar"/>
</fileset>
</path>
<target name="increment-build-number" depends="init">
<!-- Check to see if the application version has changed.
If it has, reset the build number to 0 -->
<condition property="build.number.final"
value="${build.number}"
else="0" >
<equals
arg1="${application.version}"
arg2="${expected.application.version}"/>
</condition>
<path id="groovy.cp">
<path refid="groovy.libs"/>
<fileset dir="${lib.dir}"/>
</path>
<echo message="Version: ${application.version}"/>
<echo message="Build number: ${build.number.final}"/>
<taskdef name="groovyc"
classname="org.codehaus.groovy.ant.Groovyc"
classpathref="groovy.libs"/>
<!-- Write the actual application version and build number -->
<propertyfile file="project.properties">
<entry key="build.number" value="${build.number.final}"/>
<entry
key="expected.application.version"
value="${application.version}"/>
</propertyfile>
<!-- increment build number -->
<propertyfile file="project.properties">
<entry key="build.number" operation="+" type="int" default="0"/>
</propertyfile>
<property file="project.properties"/>
</target>
<target name="clean">
<delete dir="${build.dir}"/>
</target>
<target name="compile" depends="init">
<target name="compile" depends="init,increment-build-number">
<mkdir dir="${build.dir}/classes"/>
<groovyc
srcdir="${src.dir}"
destdir="${build.dir}/classes"
classpath="${groovyc.cp}"/>
classpathref="groovyc.classpath"/>
</target>
<target name="build" depends="compile">
<mkdir dir="${build.dir}/jar"/>
<jar
destfile="${build.dir}/jar/${build.jar}"
destfile="${build.dir}/jar/pit-${application.version}.${build.number.final}.jar"
basedir="${build.dir}/classes"
compress="on"/>
</target>
<target name="release" depends="build">
<delete dir="${release.dir}"/>
<mkdir dir="${release.dir}"/>
<copy file="${build.dir}/jar/pit-${application.version}.${build.number.final}.jar"
tofile="${release.dir}/${release.jar}"/>
</target>
</project>

View File

@ -1,4 +0,0 @@
Show full issue text with -v, --verbose
=======================================
Print the full issue when passed the verbose option.

View File

@ -1,6 +0,0 @@
Add the ability to change an issue's status
===========================================
The -l/--list options lists issues, add a set of options to reclassify
an issue from one category to another. The most common is CLOSED, but
other categories should also be supported.

View File

@ -1,4 +0,0 @@
Add the ability to re-prioritize a set of issues
================================================
Add a mode that changes the priority of a selection of issues.

View File

@ -1,2 +0,0 @@
Add the ability to enter new issues
===================================

View File

@ -1,4 +0,0 @@
Add unit tests for LIST operation
=================================
Add unit tests for listing issues with no filter.

View File

@ -1,4 +0,0 @@
Add unit tests for the PRIORITY filter
======================================
Add unit tests covering the priority selection criteria of the filter.

View File

@ -1,4 +0,0 @@
Add unit tests for the CATEGORIES filter
========================================
Add unit tests covering the categories filter criteria.

View File

@ -1,4 +0,0 @@
Add unit tests for the PROJECTS filter
======================================
Add unit tests covering the projects filter criteria.

View File

@ -1,4 +0,0 @@
Add unit tests for the RECURSE filter
=====================================
Add unit tests covering the subprojects filter criteria.

View File

@ -1,4 +0,0 @@
Add unit tests for the VERBOSE option
=====================================
Add unit tests covering the verbose option

View File

@ -1,5 +1,8 @@
app.version=1.0
build.dir=build
build.jar=pit-${app.version}.jar
lib.dir=../lib
#Sat Feb 13 21:25:03 CST 2010
expected.application.version=1.0.0
build.number=5
src.dir=src
release.dir=release
build.dir=build
lib.dir=lib
release.jar=pit-${application.version}.jar

Binary file not shown.

View File

@ -7,6 +7,8 @@ class Project {
Map<String, Project> projects = [:]
Project(File dir, Filter filter = null) {
this.name = dir.name
dir.eachFile { child ->
// add sub projects
@ -62,7 +64,7 @@ class Project {
each(options.filter) {
if (it instanceof Project) {
println "\n${options.offset}${it.name}"
println "${options.offset}${'-'.multiply(p.name.length())}"
println "${options.offset}${'-'.multiply(it.name.length())}"
} else {
println "${options.offset}${it.id}(${it.priority}): " +
"${it.category} ${it.title}"