Build Plan's

[Waweros]

I was planning on creating a build.xml file for the project, but I can't find mention of any pre-processing code except on the installation wiki page. Can anyone tell me what is supposed to go into strongback-proc.jar? 

[Strongback]

That’d be great. We definitely need a way to build our artifact. Ant is definitely an option, and likely preferable since robot projects generated by (last year’s) WPILib plugins use Ant. (Maven is also an option, and while I use that at work, I do think it raises the bar for Strongback contributors.)

Do you want to create an issue on the GitHub repository at https://github.com/strongback/strongback-java/issues? It’d be great if the issue described what was needed and a detailed outline of the ZIP (including the directory structure).

IMO the primary Strongback download should be a ZIP file for teams that want to *use* Strongback, and would contain:

• strongback.jar (used by robot code and deployed to robot)
• strongback-testing.jar (used by robot unit tests, not deployed to robot) 
• strongback-sources.jar
• strongback-testing-sources.jar
• JavaDoc
• LICENSE.txt, README.md, and CONTRIBUTORS files
• example Eclipse-ready projects that a user could import, build, and possibly deploy

Did I miss anything important? Obviously the JARs correspond to the projects within the codebase, so it should be easier to create an assembly script. The ‘strongback-test’ project contains *our* unit tests, which IMO shouldn’t be needed by Strongback users and thus can be excluded from our ZIP. And I’m thinking we’d have another repository on GitHub for our test platform projects, so they’d be separate as well.

I’m not sure about others, but I thought it’d be convenient and easy to understand if our installation instructions had users unzip this file into the same folder that contains their WPILib installation.

Best regards,

Randall

[Randall Hauch]

This is now complete.