You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by bo...@apache.org on 2003/10/24 09:29:53 UTC

cvs commit: jakarta-gump gumpytest.sh

bodewig     2003/10/24 00:29:53

  Modified:    .        gumpytest.sh
  Log:
  Dummy commit to make myself owner of the file so I can change its permissions
  
  Revision  Changes    Path
  1.3       +1 -1      jakarta-gump/gumpytest.sh
  
  Index: gumpytest.sh
  ===================================================================
  RCS file: /home/cvs/jakarta-gump/gumpytest.sh,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  
  
  

Re: cvs commit: jakarta-gump gumpytest.sh

Posted by "Adam R. B. Jack" <aj...@trysybase.com>.

> gumpytest.sh didn't have the executable bit set so gump-test failed for
> me.
>
> I've changed the permissions on cvs.apache.org (and had to become the
> owner to be able to do it).  The permission bit should become set with
> the next cvs update for all Gump installations.

That Stefan, I appreciate the assist.

I am just testing this out, to see if it is a good idea or not. Gump needs
self-test (clearly, the CLASSPATH inherit algorithm is driving me nuts, I
might soon ask for help) but what is the value of an overall gump run if
gump doesn't run clean? Ought it be a project like other projects, or
something Gump does prior to doing the rest of the work. I don't know the
answer, so might try a things.

regards

Adam


Re: cvs commit: jakarta-gump gumpytest.sh

Posted by Stefan Bodewig <bo...@apache.org>.
gumpytest.sh didn't have the executable bit set so gump-test failed for
me.

I've changed the permissions on cvs.apache.org (and had to become the
owner to be able to do it).  The permission bit should become set with
the next cvs update for all Gump installations.

Stefan