search

strongback / strongback-java

A library for FIRST Robotics Competition robots that makes it easier to write and test your robot code.
MIT License
41 stars 38 forks source link

Creating a build system #4

Closed WawerOS closed 9 years ago

WawerOS commented 9 years ago

We need a build system to create artifact's. We should use ant as all FRC Java team's have to have it. The build.xml should generate a zip file of the following specifications strongback

rhauch commented 9 years ago

Our initial installation instructions proposes the following structure for the directories and files in the ZIP file:

strongback
   /java
       /ant
           build.properties
           build.xml
       /javadoc
           ...
       /lib
           strongback.jar
           strongback-sources.jar
       /lib-proc
           strongback-postprocess.jar
           strongback-postprocess-sources.jar
       /lib-tests
           strongback-testing.jar
           strongback-testing-sources.jar
           junit.jar
           junit-sources.jar
           metrics-core.jar
           metrics-core-sources.jar
       README.md
       CONTRIBUTORS.txt
       COPYRIGHT.txt
       LICENSE.txt
WawerOS commented 9 years ago

Ok, so a question, where is the post-process code in the project?

rhauch commented 9 years ago

It's not in there. It will be a separate project in the repository. It hasn't been ported from https://github.com/frc-4931/2015-Robot/tree/master/LogConverter

WawerOS commented 9 years ago

Thanks !

rhauch commented 9 years ago

Oh, see issues #6 and #7 to add executable scripts for data post-processing and minimal help.

rhauch commented 9 years ago

@WawerOS, are you working on this? If so, once you accept the invitation to join the Strongback organization on GitHub, we can assign you.

WawerOS commented 9 years ago

Yep I am.

Zabot commented 9 years ago

Its just semantics, but we should consider distributing strongback-log-processor.jar as an executable included with strongback, not as part of the library itself, since it's impossible to extend or use any other way then just executing it.

/strongback
    /bin
        strongback.sh
        strongback.bat
        strongback-log-processor.jar
    /java
        /lib
            strongback.jar
            strongback-sources.jar
        ...
rhauch commented 9 years ago

@Zabot, if the JAR is an executable, then yes we definitely can put it in the bin directory. However, if we do have a strongback executable (see #6) then users really would have no reason to execute the JAR directly. And if that's the case, then I'd still argue the separate strongback-processing.jar (or strongback-log-processing.jar if we prefer) should be kept out of the bin directory so that strongback process ... is the one way to post-process the log files.

rhauch commented 9 years ago

@WawerOS, have you been able to make progress on this? This is blocking us from releasing, so it'd be great if we could get something soon.

WawerOS commented 9 years ago

I'm sorry to ask can someone take this over school is revving up. I've pushed my changes to my repository if anyone wants to work off of that. The classpath has been giving me trouble.

rhauch commented 9 years ago

@WawerOS can you provide a URL to your repository and branch?

WawerOS commented 9 years ago

Right sorry, [https://github.com/WawerOS/strongback-java]()