mirror of
https://github.com/wpilibsuite/allwpilib
synced 2026-06-19 00:41:43 +00:00
26419ec209
While final would seem to make sense for RobotMap values (as these values should be constant at runtime), RobotMap values are often not truly final in the Java sense of the word, as on real robots they often change between project builds (e.g. they often can and will be changed by teams as wiring changes on the physical robot). Unfortunately, incremental compilation in Eclipse follows Java rules, and doesn't track cross-module dependencies on final variable values, resulting in very non-intuitive behavior when a final variable's value is changed: other (unchanged) Java modules using the final variable are NOT recompiled (as is necessary to pick up the new value), and there is no easy way to force recompilation of every Java file in the project. Change-Id: I75b13aaf4f4a687698f853d5e11eef5f904716ea