[Tinyos Core WG] TestSerial on telosB
Philip Levis
pal at cs.stanford.edu
Fri Oct 20 07:30:52 PDT 2006
On Oct 20, 2006, at 12:56 AM, Vlado Handziski wrote:
> On 10/20/06, Phil Buonadonna <pbuonadonna at archrock.com> wrote:
> > Why are we keeping the .jar in CVS? This just complicates
> > things. A better option is to have the .jar created during
> > the RPM building step.
> >
> I disagree. It make things a lot easier for those doing platform
> devel.
> that don't want to worry about the java cruft. The tests should be
> self-contained.... including the java jar. That's what it's there
> for.
>
>
> Then the tests should be done on the RPM/binary release. The main
> problem is that we don't have a mechanism to make sure that
> the .jar is always in sync with the rest of the code. We are not
> keeping the ELF files of the test apps in CVS why should we keep
> the .jars ?
>
The evidence -- my doing the TinyOS 1.0 release, David Gay doing 1.1,
2.0pre, and 2.0beta1, my doing 2.0beta2 -- is that this makes it
easier. It makes it easier for people who want to check out from CVS,
it makes it easier for people who have a JRE but not a JDK, it makes
it easier for developers who don't want to mess with Java, and it
makes it easier for people who want to just grab the jar (rather than
having to extract it from an RPM).
If you don't like having a jar in there, then you can set your
CLASSPATH to be TOSROOT/support/sdk/java rather than TOSROOT/support/
sdk/java/tinyos.jar.
Phil
More information about the Tinyos-2.0wg
mailing list