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.