Generating preverified jars

[fovea1959]

Something I've been toying with is using microlog to take care of our logging needs (replacing System.out.println). I have had good success integrating microlog into a robot if I include (stripped-down) source code, but now I want keep microlog as a separate jar and include that jar into the robot build.

Does anyone have an example of a build.xml to generate a preverified jar, ready to include in a Robot?

[Spaghetti]

Hey there, we recently had the exact same problem with shared jars. What we ended up doing was copying the build.xml from the wpilib project (which builds a pre-verified library .jar) and then run the target 'dist'.

Would be interested in your results with using microlog if you get it going. We've been rolling our own logging solution from scratch each year.

[joelg236]

I'm not so much interested in the logging part, but want to know how exactly you can include other jars when building. If someone figures it out, can you post specifics of how to do it?

[alexhenning]

If you look in the ~/sunspotfrcsdk directory, you can see how team's code is preverified.

Specifically, looking at ~/sunspotfrcsdk/build.xml and ~/sunspotfrcsdk/ant/preverify.jar will show you how to preverify with ant. Once you've preverified it, you can look into adding to the classpath in ~/sunspotfrcsdk/ant/classpath.xml. Unfortunately, the process of adding libraries isn't straightforward.

Hopefully this helps get you started.

[Spaghetti]

We'll try to post up our off-season code soon and I'll put a link here. It'll have an end-to-end example of a separate project .jar getting pre-verified and included in a robot project.

[JohnGilb]

Following up on Spaghetti:

https://github.com/Team488/Shared

There are 3 projects in there:
-Core
-Test
-ActualRobot

Core gets preverified so it can be included in ActualRobot.