>>>>> On Tue, 17 Feb 2004 06:36:23 -0600, Steve Cohen <[EMAIL PROTECTED]> said:
> Good, Jeff. I've long thought I was hampered by not having actual
> sites to test against. It's quite possible something slipped as VMS
> underwent heavier changes than any of the others.
> Would it be possible to run the functional test against an earlier
> version of the package? That might help to quickly verify where the
> problem lies.
Maybe, skipping methods that were added. I really wanted to use the
new methods you added and just that exploring in the form of
functional testing. You maybe on to something, it may have never
worked.
> On Monday 16 February 2004 11:07 pm, you wrote:
>> Sorry to take so long to reply to this vote. I wanted to explore
>> the api a bit and did so by writing a test case that we can use for
>> functionally testing FTPClient wrt to listings. The test is data
>> driven so in the suite() method there is an array of string arrays
>> holding information about each site to test. For each entry the
>> test case is run. Currently I have a public unix and windows site
>> being tested. I did find one public vms ftp server at HP, but
>> there is a problem with it. The listings aren't quite the same as
>> I've seen before, the files permissions/groups aren't terminated
>> with a closing ']'. I've tried to run this test against some of
>> our internal vms sites, but also ran into trouble ( although I
>> haven't had much time to figure it out ).
>>
>> Since this test shouldn't be run at each build, I have it excluded
>> like the telnet functional test. I also added a test:functional
>> goal to our maven.xml so we can run these tests.
>>
>> maven test:functional
>>
>> The above command will run any test case that has a name like:
>> *FunctionalTest.java
>>
>> I'm leaning towards a -1 until we can verify the vms case. I think
>> it may be my test or the public site, but I'm just not sure. I
>> know it is an obscure case, but we do use it and I'd like to know
>> the parsers do work. This functional suite, although it is slow,
>> should provide us with some end-to-end regression along with the
>> currenly growing set of programmer tests.
>>
>> >>>>> On Fri, 30 Jan 2004 16:21:10 -0600, Steve Cohen >>>>>
>> <[EMAIL PROTECTED]> said:
>> >
>> > I am now proposing for a formal vote, releasing
>> commons-net.1.2.0. > The proposal is to release the current HEAD
>> branch, as last amended > by me over a week ago.
>> >
>> > I know there are other patches that have been submitted but no
>> one > seems to have the time to evaluate them. The current version
>> of the > code contributes autodetection of system type with manual
>> override > capability for any ListParser and accomplishes
>> substantial > refactoring, reducing the confusion level in this
>> part of the > system. These are important changes and will enable
>> better > interface with Ant.
>> >
>> > This plan does NOT encompass the release of the 1.1.1 branch as
>> the > last JDK1.1 compatible version. Although the code now in
>> that > branch compiles and runs if jakarta-oro-2.0.1.jar is
>> substituted for > 2.0.7, it throws JIT errors which probably have
>> more to do with my > execution environment or some configuration
>> mistake in this ancient > JDK and I'm stumped. I recommend doing
>> this release later (CVS tag > is there, waiting to be handled) when
>> more time may be available to > look at these issues. If anyone is
>> familiar with JIT errors in > JDK1.1 perhaps they can weigh in on
>> what error messages in my > previous emails mean.
>> >
>> > My vote, of course: +1
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> [EMAIL PROTECTED] > For additional
>> commands, e-mail: [EMAIL PROTECTED]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
