Release Changes

Release History

VersionDateDescription
2.2.02011-02-08This is a maintenance release of the Validation Tool integrated with release 3.1.0 of the Product Tools Library.
2.1.02010-03-24This release of the Validation Tool addresses issues found during beta test for release 2.1.0-beta.
2.1.0-beta2010-02-05This release of the Validation Tool software is integrated with release 3.0.1 of the Product Tools Library.
2.0.12009-02-06The operational release of the Validation Tool software incorporating the Phase II capability supporting validation of catalog files.
2.0.02009-01-09This release of the Validation Tool software incorporates the Phase II capability supporting validation of catalog files and was released to the Technical Staff for beta testing.
1.2.02008-07-24This is a maintenance release of the Validation Tool, which includes an improved reporting capability to handle large validation runs and better message reporting of validation errors. Most of the changes in this release were implemented in the product-tools package and are detailed in the Release Changes page for that project.
1.1.02007-09-28This is a maintenance release of the Validation Tool including fixes and changes requested by the early adopters of the application. It is also the first release of the vtool project.
1.0.02007-05-04This release of the Validation Tool represents the operational release for the Phase I targeted capabilities. Although this release pertains to the product-tools project, its description has been retained here for completeness. Changes for previous releases can be viewed in the product-tools documentation.

Release 2.2.0 - 2011-02-08

TypeChangesBy
fixPDSEN-277 - Fix for valid value match with "_" replaced by " ". Will still issue a warning letting one know the value has been manipulated. Inherited from product-tools.pramirez
fixPDSEN-316 - Fixed truncation of file names in some of the log messages. Inherited from product-tools.pramirez
fixPDSEN-329 - Changed the way date/times were parsed to be simpler and cleaner. Also addressed a bug found in old parsing code. For the time being the invalid date messages may be less specific than in the past. Inherited from product-tools.merose, pramirez
fixPDSEN-335 - Updated messaging for min and max value checking to display the number as a string to stop rounding from occurring. Some extreme cases still round in messaging but min/max checks remain working as published. Inherited from product-tools.pramirez
fixFixed VTool to not follow pointers when the '-F' command-line flag option is set.mcayanan
fixFixed the Windows batch file, VTool.bat, to support Windows path names with spaces.mcayanan

Release 2.1.0 - 2010-03-24

TypeChangesBy
fixPDSEN-259 - Wrapping BufferedInputStream in a custom stream that returns EOF after the first non-whitespace character is found following the END statement. This was done in an effort to prevent memory overflow issues with large attached labels. Inherited from product-tools.jagander
fixPDSEN-290 - Fixed to throw an error message when referenced files for non include pointers are not found.mcayanan
fixPDSEN-297 - Fixed dictionary parser to support reading a default dictionary located inside the product tools jar file. This resolves an issue where VTool was crashing when validating a label without passing in a dictionary file. Inherited from product-tools.mcayanan
fixPDSEN-298 - Fixed dictionary parser to support dictionary definitions where the MAXIMUM attribute is set to UNK. Inherited from product-tools.mcayanan
fixPDSEN-299 - Fixed to capture dictionary errors in the report.mcayanan
fixPDSEN-300 - Fixed dictionary parser to support SPECIFIC_GROUP definitions. Inherited from product-tools.mcayanan
fixPDSEN-303 - Fixed parser to correctly throw the referenced file name when it cannot be found. This bug only occurred in pointer statements that contained multiple referenced files (Example: ^DATA_SET_CATALOG = {"L0_DS.CAT", "L1B_DS.CAT"}). Inherited from product-tools.mcayanan
fixPDSEN-304 - Fixed to support proper checking of required/optional nested objects with descriptor names. Inherited from product-tools.mcayanan
fixPDSEN-306 - Getting attached data start byte from custom input stream instead of lexer due to tokenization and error recovery issues skipping until start of next line when encountering non-parseable binary data. Inherited from product-tools.jagander
updatePDSEN-307 - Update to truncate long values for error messages generated for exceeding the acceptable maximum length of an element definition. Inherited from product-tools.mcayanan
fixPDSEN-310 - Fixed to capture problems if errors occurred in a nested fragment file. Inherited from product-tools.mcayanan
updateFiles that do not contain a PDS_VERSION_ID are reported as warnings instead of errors.mcayanan

Release 2.1.0-beta - 2010-02-05

TypeChangesBy
fixPDSEN-158 - VTool validation does not examine END statement. Inherited from product-tools.pramirez, jagander
addAdded the capability to report line lengths greater than 80 characters (78 + CR/LF). Inherited from product-tools.pramirez
addAdded the capability to report lines that don’t end in CR/LF. Inherited from product-tools.pramirez
addAdded the capability to combine attribute value lists of two identical dictionary definitions together instead of one overwriting the other when two dictionaries are merged (i.e. STANDARD_VALUE_SET, REQUIRED_ELEMENT_SET, OPTIONAL_ELEMENT_SET, etc.). Inherited from product-tools.pramirez
updateModified the project to utilize the upgraded Product Tools Library.pramirez, mcayanan
updateRewrote reports as the product tools library was shifted from a log. Consistency with old reports was maintained where possible. Some underlying messages have changed from the Product Tools Library but generally they should be much clearer.pramirez

Release 2.0.1 - 2009-02-06

TypeChangesBy
updateModified how catalog pointers are handled to not include referenced content but to validate the existence of the referenced file. Added check for valid catalog pointer names.pramirez

Release 2.0.0 - 2009-01-09

TypeChangesBy
fixPDSEN-107 - Inconsistent validation of values with quotation marks based on the associated element's general data type. The issue related to quoted date/time strings has been resolved. The issue related to quoted variables was determined to be a LTDTool issue and a new issue was created and assigned to that component. Inherited from product-tools.pramirez
addPDSEN-116 - Support validation of catalog files. Inherited from product-tools.pramarez
fixPDSEN-147 - VTool exits ungracefully when validating a catalog directory in a GCJ environment. This is believed to be associated with the limitation in catalog file support (PDSEN-116) as opposed to the GCJ environment so it should also be resolved in this release. Inherited from product-tools.pramirez
fixFix spacing issue of the validation report. Seen on the Mac platform.mcayanan

Release 1.2.0 - 2008-07-24

TypeChangesBy
updatePDSEN-108 - Command-line arguments with multiple values should use commas instead of spaces for valid separators.mcayanan
updatePDSEN-111 - Generate a warning message regarding semantic checking being skipped when a dictionary is not provided.mcayanan
fixPDSEN-118 - Specifying a target in the configuration file is not recognized.mcayanan

Release 1.1.0 - 2007-09-28

TypeChangesBy
addThe Validation Tool application has been split out from the product-tools project in order to provide more specific documentation and to turn the product-tools project into a library of classes that can be included by other projects. The following files or directories were moved to this project: src/java/gov/nasa/pds/tools/VTool.java, src/java/gov/nasa/pds/tools/flags/VToolFlags.java, src/java/gov/nasa/pds/tools/config/, src/java/gov/nasa/pds/tools/status/, src/resources/scripts/, xdocs/install/ and xdocs/user/.shardman
addAdded a README file to be included with the binary distribution package. The README file points the user to the documentation provided with the package.shardman
updateUpdated VTool to return additional exit values. See the Operation section for the list of values.mcayanan
updateRefactored the VTool class.mcayanan
fixChanged the jarpath settings in the shell scripts to a more generic value ('vtool-X.X.X' instead of 'vtool-1.0.0').mcayanan

Release 1.0.0 - 2007-05-04

TypeChangesBy
addAdded support for validation of label fragments.pramirez
addAdded the capability to return an appropriate exit status value based on validation results or tool application failure.mcayanan
addCreated batch and shell scripts for simpler execution of VTool.mcayanan
addAdded the capability for targets to be specified implicitly.mcayanan
addAdded -f or --force flag option to perform standalone label fragment validation.mcayanan
updateValidation of units is now performed against the master list of unit values. This comparison is case sensitive.pramirez
updateFile names referenced by pointers may be in any case and still be discoverable by the tool. File names in mixed case will generate a warning message.pramirez
updateCleaned up reporting including replacing SEVERE with ERROR in all instances and properly representing fragment messages when they are included in a label validation.pramirez
updateImplemented new log file behavior to allow logs to be written to memory. This allows generation of reports without the need of explicitly specifying the log file flag option.mcayanan
updateChanged the log file flag (-l or --log) option to optionally allow a file specification. See Use and Operation guide for log generation details.mcayanan
updateAdded time and date of tool execution in final reports.mcayanan
updateEnhanced user guide with more details regarding command-line flag options, report examples, etc.mcayanan
fixFixed support for UNC pathnames.mcayanan
fixFixed the minimal report stylesheet to work correctly on the Linux platform.mcayanan