1.2.2

Patch release that adds better error handling for various conditions, including when the WPILib directory does not yet exist due to the Eclipse plugins not being used properly install the WPILib libraries. See the change log for details.

1.2.1

Patch release that fixes the behavior of the --overwrite flag for the new-project command when the project directory already exists, and fixes the error handling behavior when the flag is not provided to better capture which file prevented the command from running. See the change log for details.

1.2.0

The Strongback CLI client now shows information about 3rd party libraries and whether the versions included in a particular Strongback Java Library version are the same as what is currently installed into the WPILib user library folder. This will hopefully make it more clear whether the WPILib and its user libraries have been upgraded to match a particular Strongback Java Library version.

A few other minor fixes and improvements were made to improve the behavior when certain local files and directories do not yet exist.

1.1.0

When the Strongback CLI installs a version of the Strongback Java library, it will now automatically copy the Strongback JAR and any JARs for runtime dependencies into the ~/wpilib/user/java/lib directory. The 2017 WPILib Ant scripts find these user libraries and automatically deploy them to the robot, and the 2017 WPILib Eclipse plugins automatically add these user library JARs to the classpath of any Eclipse robot projects.

By default, existing 3rd party JARs found in the WPILib user library are left untouched. This ensures that if the user has already added several JARs as WPILib user libraries, the Strongback CLI will not replace these unless the user explicitly uses strongback install --userlib ... to force the replacement of the WPILib user library JARs with those included in the new Strongback version.

This new feature works very seamlessly when upgrading to a newer version of Strongback. However, when the CLI does not remove any JARs from the WPILib user library directory. That means that when uninstalling or downgrading to an older version of the Strongback Java library with fewer 3rd party dependencies, those dependencies will be left inside the WPILib's user library directory. Currently, the user is responsible for removing these.

Versions 1.x of the Strongback Java library do not currently have any runtime dependencies, so this change has no affect when installing these older versions.

1.0.1

Minor fixes to the Strongback CLI tool's output of the team number.

1.0.0

Initial release of the Strongback CLI, which can be used to install, manage, and upgrade any version of the Strongback Java Library.