Importing 2014 RobotBuilder and (Java) program into 2015 toolchain

[s-taylor]

Has anyone successfully imported RobotBuilder and/or generated (Java) collateral from last year into this year's tools?

I used RobotBuilder v1.0 last year, and the new (v1.5) version refuses to load the yaml file. I'm wondering if anyone has figured out the right set of translations in the yaml to port the content.

Similarly for the generated JAVA code, I tried copying last year's folder into my Eclipse workspace and doing an import (Just as I have done for this year's project) but it isn't recognized as an available project to import. I'm not terribly surprised by this, but I would really love to be able to pull up code examples from last year in Eclipse to have students compare against for style/content. Maintaining parallel NetBeans and Eclipse windows is the obvious fallback, but it would be nice to have it all in one tool.

Thanks for any suggestions or pointers!
-Scott

[Jon Stratis]

I think we fell back to creating a new robot project in eclipse, then copying over the individual have files to the new project. A bit of a pain, and it'll give you a bunch of compilation errors due to small changes in the libraries, but those can be overcome pretty easily.

[Joe Ross]

Depending on how complicated your Robot Builder file is, you may be able to just change the version number at the top of the yml file. I was able to do this for a simple project. This didn't work for our 2014 project, however as robot builder would crash.

We used the same process as Jon for eclipse. It didn't take long to get everything to compile.