|
|
|
 Short answer, the GDC has ruled it legal explicitly through Q&A, implicitly through Q&A, and implicitly through the Manual. - EricH [more] |
 |
|
|||||||
|
||||||||
 |
| Thread Tools | Rate Thread | Display Modes |
|
|
|
| Short answer, the GDC has ruled it legal explicitly through Q&A, implicitly through Q&A, and implicitly through the Manual. - EricH [more] |
|
|
|||||||
|
||||||||
|
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Deploy Error
When deploying we get this error in the Drivers Station
ERROR Unhandled exception instantiating robot org.usfirst.frc.team2145.robot.Robot java.lang.ExceptionInInitializerError at [java.lang.Class.forName0(Native Method), java.lang.Class.forName(Class.java:259), edu.wpi.first.wpilibj.RobotBase.main(RobotBase.jav a:197)] The console in Eclipse says the code built successfully. Here is our code https://github.com/LakeFentonHazmats/2015Mule Any ideas? 
|
|
#2
31-01-2015, 19:02
|
||||||
|
||||||
|
Re: Deploy Error
There are many places where you are creating objects using I/O resources that are already allocated.
You'll get better stack traces if you create your subsystems in robotInit, like Robot Builder does. Using Robot Builder, or at least being more diligent in using RobotMap would make this a lot easier.
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
