Commit Graph

6 Commits

Author SHA1 Message Date
Fredric Silberberg
1e4e0bacde Gradle Build
This adds gradle support for building wpilibj and wpilibc. At this
point, both of these libraries should be fully ready to go.

Gradle should give us a number of improvements, including less
dependencies for getting building up and running, and MUCH faster build
times. I'm noticing significantly faster build times already compared to
Maven, with neither system building the plugins. The changes here should
be pretty straight forward. The basic command for gradle is './gradlew'.
This is the gradle wrapper, and it will find and download the correct
gradle executable for your system. There is no need to install anything
yourself. To see every task available, run './gradlew tasks'. The
important tasks for us are listed under the WPILib header when the tasks
command is run. To generate unit test binaries, the
fRCUserProgramExecutable command will create the C++ tester, and the
wpilibjIntegrationTestJar command will create the Java tester. The Jenkins
deploy scripts have been modified to know the difference between maven
generated and gradle generated jars with an environment variable. Creating
the eclipse plugins still requires Maven, but gradle will handle calling
it correctly and generating the proper dependencies for it. Create the
plugins by calling ./gradlew eclipsePlugins.

Jenkins can now be modified to support the new build system. Unit tests
are run with ./gradlew test. Generating the integration tests uses the
above two commands, and then process proceeds exactly as it did before.
For publishing documentation, a new task has been created, ./gradlew
publishDocs, which handles putting the documentation where Jenkins expects
for publishing.

Change-Id: I9a260d391984f98ef9170993efe933e4026161dc
2015-05-20 16:22:17 -04:00
Evin Ugur
d2c1bc174f updted licesne strings in eclipse plugins
Change-Id: I9593e4dda3e8db8f1fd3d847285932affffcfd51
2014-10-09 19:33:10 -04:00
Jonathan Leitschuh
85b0a46fdb Adds maven configuration information to use m2e
This also removes all of the .project and .classpath files generated by
eclipse

Change-Id: Ieedf3166a3194040704133909cc7d71755009714

Removes the .project and .classpath files from the project as the .gitignore should have
2014-05-15 19:27:32 -04:00
thomasclark
6e01adaa57 Revert "Modifies maven files to work with m2e"
This commit causes Eclipse to give a vaugue error message when creating a new Robot Java Project or Robot C++ Project.

This reverts commit 36241b0d6c.

Change-Id: I47b66c53604f07b6e40c0db6aa250b977d9ae903
2014-05-14 14:28:04 -04:00
Jonathan Leitschuh
36241b0d6c Modifies maven files to work with m2e
Change-Id: I3f0cccbdd406f48bcb430af89e77d6b74627918a
2014-05-13 09:44:35 -04:00
Brad Miller
3178911eef Initial checkin of unified hierarchy of WPILib 2015 2013-12-15 18:30:16 -05:00