Hi Sam,

> -----Original Message-----
> From: Sam Ruby [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, 10 March 2001 1:12 pm
> To: [EMAIL PROTECTED]
> Subject: RE: Off topic (in part)
>
>
> John Morrison wrote:
> >
> > Ha, OK.  Will look more closely at this.  I've made the alteration
> > on my own system (obviously) and have only seen the desired change
> > in system functionality.  Could you tell me where to look for the
> > flaw?  I assume it's in the resulting html?
>
> /workspace/@logdir doesn't exist in $SOURCE
>
> /workspace/@logdir does exist in work/merge.xml, but other things are
> different.

True, however a (quick) work around is to duplicate the logic from merge.xsl
into bash.xsl (and win2k).  This prob should be extracted into a file which
merge, bash and win2k share with only the appropriate translate being used
in the win2k version.  But for the moment - I think this fixes it.

> With your change, the puball.sh generated by gen.sh does not appear to be
> workable.
>
> > PS Sam, any ideas why I'm getting the problem with JUnit? (see
> > previous posting)
>
> I'm looking into it, but nothing as of yet.  The JUnit build process is
> still a bit of a puzzle to me.  If I try building it without any special
> parameters, the zip file is placed into a directory which is to
> be included
> in the zip, resulting in a bit of nasty recursion.  I also have never
> figured out how to get the unit test of JUnit to run.  But neither appear
> to be the problem that you are seeing.  If I figure something out, I will
> let you know.

The only thing that has occured to me is that I'm running on w2k using Sun
JDK1.3, you are running on (a variation of) unix (?) with (?) JDK1(.x)?  And
that int(255) equiv byte(-1) so maybe it boils down to a OS/JDK dependency
somewhere?  I've got some time today to experiment - will try and find my
way around the JUnit source...

John.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to