pit/libpit/project.properties

#Thu, 08 Dec 2011 14:35:45 -0600
#Sat Apr 24 17:08:00 CDT 2010
build.dir=build
src.dir=src
lib.shared.dir=../shared-libs
test.dir=test
build.number=10
version=3.2.0
name=libpit
lib.dir=lib
lib.local=true
release.dir=release
release.jar=pit-${application.version}.jar
Filter and FileProject support for extended properties. * Added support for extended properties to `Filter`. Unlike the basic properties, which allow the caller to specify a list of acceptable values, the extended properties only supports a map of properties, all of which must be available on the issue and match the given value. * Made `Issue` a concrete class. There was no reason it could not be a concrete object. The main difference is that the extending classes all add some sort of persistence to the issue, but having an in-memory `Issue` in its most basic form can be useful and should be allowed. * Changed the default priority for new issues from 9 to 5. * Bug fix on `FileIssue.formatIssue()`. If was not properly returning its result leading to failure if no extended properties were given. * Reworked `FileIssue.formatIssue()` to only print the horizontal rule seperating the issue text from the extended properties if there are extended properties to print as well. * Changed the `FileProject.createNewIssue()` to handle extended properties and handle the basic properties in a manner more consistent with `Issue`. It is now creating an `Issue` object and using the `FileIssue.formatIssue()` function to write that to a new issue file, then loading that file back in as a `FileIssue`. This cuts down on code duplication and makes it so that the options map that `FileProject.createNewIssue()` expects is the same as the options to the `Issue` constructor. 2011-12-08 14:38:24 -06:00			`#Thu, 08 Dec 2011 14:35:45 -0600`
Added FlatProjectView. Used it to create an 'All Issues' project in pit-swing. Solves issue #11: pit-swing: Add a default, "all-projects" view. 2010-04-24 18:10:19 -05:00			`#Sat Apr 24 17:08:00 CDT 2010`
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 2010-02-13 21:30:31 -06:00			`build.dir=build`
Finished libpit 1.1.0. Added change operations (priority, category, etc) Began unit testing of libpit. Made most of the changes to pit-cli needed to incorporate the new libpit features. 2010-02-18 11:02:20 -06:00			`src.dir=src`
			`lib.shared.dir=../shared-libs`
			`test.dir=test`
Filter and FileProject support for extended properties. * Added support for extended properties to `Filter`. Unlike the basic properties, which allow the caller to specify a list of acceptable values, the extended properties only supports a map of properties, all of which must be available on the issue and match the given value. * Made `Issue` a concrete class. There was no reason it could not be a concrete object. The main difference is that the extending classes all add some sort of persistence to the issue, but having an in-memory `Issue` in its most basic form can be useful and should be allowed. * Changed the default priority for new issues from 9 to 5. * Bug fix on `FileIssue.formatIssue()`. If was not properly returning its result leading to failure if no extended properties were given. * Reworked `FileIssue.formatIssue()` to only print the horizontal rule seperating the issue text from the extended properties if there are extended properties to print as well. * Changed the `FileProject.createNewIssue()` to handle extended properties and handle the basic properties in a manner more consistent with `Issue`. It is now creating an `Issue` object and using the `FileIssue.formatIssue()` function to write that to a new issue file, then loading that file back in as a `FileIssue`. This cuts down on code duplication and makes it so that the options map that `FileProject.createNewIssue()` expects is the same as the options to the `Issue` constructor. 2011-12-08 14:38:24 -06:00			`build.number=10`
			`version=3.2.0`
Refactored pit-cli build process to work with JDB common build. 2011-11-21 03:03:52 -06:00			`name=libpit`
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 2010-02-13 21:30:31 -06:00			`lib.dir=lib`
Moved to JDB common build structure. 2011-11-20 21:00:53 -06:00			`lib.local=true`
Finished libpit 1.1.0. Added change operations (priority, category, etc) Began unit testing of libpit. Made most of the changes to pit-cli needed to incorporate the new libpit features. 2010-02-18 11:02:20 -06:00			`release.dir=release`
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 2010-02-13 21:30:31 -06:00			`release.jar=pit-${application.version}.jar`