hackystat eclipse projects and a fix for an issue

i noticed that there must have been a decision to use jar files to handle eclipse dependencies. i'm not too sure i like that move. anyway, i suppose we can just attach the source. i tried that in eclipse and it didn't work... hmm. i thought i was an eclipse expert.

it took me a little while, to figure out that i was attaching the wrong source directory. haha. sheesh, what a noob. so, in eclipse if you have the source directory all you have to do is point to the source directory. anway, i think we still should be creating a jar with the source. something like the following target:

<target name="jar-source" description="Create the source in sensorbase.jar">
<!-- Define the directories and distribution name -->
<mkdir dir="${tmp.dir}" />
<copy todir="${tmp.dir}">
<fileset dir="${src.dir}"/>
</copy>

<jar destfile="${basedir}/sensorbase.source.jar" basedir="${tmp.dir}">
<manifest>
 <attribute name="Main-Class" value="org.hackystat.sensorbase.server.Server"/>
 <attribute name="Implementation-Title" value="Hackystat SensorBase-UH"/>
 <attribute name="Implementation-Version" value="${version}"/>
 <attribute name="Implementation-Vendor" value="Collaborative Software Development Laboratory, University of Hawaii"/>
</manifest>
</jar>
<delete dir="${tmp.dir}" />
</target>

dev work
i also worked on a bug that i found, issue 3


dev process thoughts

um... where is the freshStart? what ant targets do i have to run to ensure that everything is all good. actually, i know the answer, but will other people. woah... verify.build.xml is the answer to this one. on another note where is the continuous integration?

also, i would suggest that our goal should be to tighten up the checkstyle errors now. that means check for brace placements, whitespace, parentheses, etc. i propose, that we create two checkstyle configurations one strict and one with our current checks. the goal would be to convert to the strict one.