W3C home > Mailing lists > Public > public-mobileok-checker@w3.org > October 2007

RE: Draft for the user manual

From: Jo Rabin <jrabin@mtld.mobi>
Date: Tue, 16 Oct 2007 14:35:09 +0100
Message-ID: <C8FFD98530207F40BD8D2CAD608B50B47D3E24@mtldsvr01.DotMobi.local>
To: "Sean Owen" <srowen@google.com>
Cc: "Ignacio Marin" <ignacio.marin@fundacionctic.org>, <public-mobileok-checker@w3.org>

> -----Original Message-----
> From: Sean Owen [mailto:srowen@google.com]
> Sent: 16 October 2007 14:32
> To: Jo Rabin
> Cc: Ignacio Marin; public-mobileok-checker@w3.org
> Subject: Re: Draft for the user manual
> On 10/16/07, Jo Rabin <jrabin@mtld.mobi> wrote:
> > (Actually, I guess the format of the command line has changed at
> point,
> > I recall being able to suppress moki output and results output as
> as
> > put them in a file - so there is some redundant code is Tester now -
> lines
> > 128 and 142 can't ever actually get executed?)
> I don't know if it's changed, but those two lines can still be
> executed. Specifying -m for examples suppresses System.out output, and
> writes to a file. But if no argument is supplied to -m either, nothing
> is output. This at least is how I remember it working in the past.
> > > Finally, the JAR did not seem to be there so we submitted it to
> CVS in
> > the root.
> >
> > Ah yes, I see it. Should it be in CVS or should it be somewhere else
> a
> > downloadable for people uninterested in the code?
> Here's the link to it from web CVS:
> 1.0-deploy.jar?rev=1.1&only_with_tag=HEAD
> It's buildable from code with the "build release" target but of course
> providing a direct download to the compiled binary is good, yes.

I guess I am thinking that we would only be building occasionally so how
often would the jar get updated - and wouldn't we have a download area
for different revisions?

Received on Tuesday, 16 October 2007 13:35:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:13:04 GMT