Hi Thomas.
Thomas DeWeese:
> Two of the security tests use the jar files from the
> repository (they fetch them via http from apache). What is
> really needed is a non-local http server but basically
> this is the easiest thing. One option would be to put
> them up on 'people.apache.org' or somewhere in our
> web site however this makes it a bit tricky if/when we
> need to update them.
Oh, sorry about that. I was trying to get rid of all of the unknown
files when doing a "svn status" after running the test suite. I noticed
that these two jars were created in build.xml so I thought they wouldn't
be needed in svn.
Incidentally, there's one test for an invalid filename in there that
creates a directory called "ZYZ::". Under Linux though this is a valid
filename, and it always used to perplex me as to why it was created
until I found the test that did it. :-)
> We could also create a 'test' directory in SVN
> as say a peer of tags/branches.
>
> However my preference would be to just re-add the jars
> to version control and perhaps improve the dependencies
> so it only builds them if they really need to be built (i.e.
> have them depend on the .java files not the .class
> files). I agree that this is a little hacky but I think
> from a practical perspective it works well...
That sounds ok. It will avoid the slight annoyance of those jars coming
up as modified when doing a commit.
Cameron
--
e-mail : cam (at) mcc.id.au icq : 26955922
web : http://mcc.id.au/ msn : cam-msn (at) aka.mcc.id.au
office : +61399055779 jabber : heycam (at) jabber.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
