Batch processing methods generated by the build system should keep input, output, and constant parameters in their original order

[jjr8]

Currently, the batch processing code generates methods with parameters in a fixed order: input parameters followed by output parameters followed by constant parameters. This causes some parameters to be reordered in the batch method from the order specified in the non-batch method. For example, the CoastWatch tools have a cloudMaskFile parameter which appears in the middle of the optional masking parameters. In the batch version, this parameter gets moved up towards the front. This is not desired because the parameter is optional, and won't need to be specified most of the time, because most users will be working with CoastWatch HDF files.

[jjr8]

Fixed in MGET 0.3.