jdb/pit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
pit/libpit/project.properties

14 lines
266 B
Properties
Raw Normal View History

Multiple sort criteria to filters, bugfix, and cleanup. * Fixed a bug in the common build. This bug is fixed in version 1.9, but I am patching this bug locally in 1.6 until I have evaluated 1.9 with this project. * Moved `ExtendedPropertyHelp` to `com.jdbernard.pit` from `com.jdbernard.pit.file`. * Added a number of property types to `ExtendedPropertyHelp`. New additions are: * `java.util.Calendar` *object -> string value only* * `java.util.Date` *object -> string value only* * `java.lang.Long` *this replaces `java.util.Integer`* * `java.lang.Float` *object -> string value only* * `java.lang.Double` * Cleaned up the `matches(String)` and `matches(Class)` functions of `ExtendedPropertyHelp` * Modified `Filter` sorter behaviours. The `issueSorter` and `projectSorter` fields are now allowed to be either a closure or a list of closures. A single closure works as it did before. The list of closures allows the caller to specify multiple sort criteria. The individual criteria closures are applied in reverse order, so that the first item in the sorter list is the most significant criteria. For example, if the caller set the sorter to `[{it.category},{it.priority}]` then the issues would be sorted first by priority and then sorted again by category, meaning that the resulting data would be ordered first by the category of the issue and then by the priority for issues that share the same category. * Modified the methods in `Project` that use `Filter` objects to conform to the above behavior regarding sorting. It may be a better idea though to move the sort code all into `Filter` so that it is in one place. * Cleaned up the code in `Status` for matching status based on given symbols or partial status names.
2011-12-07 18:01:18 -06:00
#Wed, 07 Dec 2011 17:53:14 -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
Multiple sort criteria to filters, bugfix, and cleanup. * Fixed a bug in the common build. This bug is fixed in version 1.9, but I am patching this bug locally in 1.6 until I have evaluated 1.9 with this project. * Moved `ExtendedPropertyHelp` to `com.jdbernard.pit` from `com.jdbernard.pit.file`. * Added a number of property types to `ExtendedPropertyHelp`. New additions are: * `java.util.Calendar` *object -> string value only* * `java.util.Date` *object -> string value only* * `java.lang.Long` *this replaces `java.util.Integer`* * `java.lang.Float` *object -> string value only* * `java.lang.Double` * Cleaned up the `matches(String)` and `matches(Class)` functions of `ExtendedPropertyHelp` * Modified `Filter` sorter behaviours. The `issueSorter` and `projectSorter` fields are now allowed to be either a closure or a list of closures. A single closure works as it did before. The list of closures allows the caller to specify multiple sort criteria. The individual criteria closures are applied in reverse order, so that the first item in the sorter list is the most significant criteria. For example, if the caller set the sorter to `[{it.category},{it.priority}]` then the issues would be sorted first by priority and then sorted again by category, meaning that the resulting data would be ordered first by the category of the issue and then by the priority for issues that share the same category. * Modified the methods in `Project` that use `Filter` objects to conform to the above behavior regarding sorting. It may be a better idea though to move the sort code all into `Filter` so that it is in one place. * Cleaned up the code in `Status` for matching status based on given symbols or partial status names.
2011-12-07 18:01:18 -06:00
build.number=8
version=3.1.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
Reference in New Issue Copy Permalink