James,
I tried adding all your code back. After i patched TestJavaUtils for the underscore
changes, i am
getting a failure in test.wsdl.addrNoImplSEI. I don't know how to proceed further, I
was wasted
one full day on this....i give up.
Thanks,
dims
[java] compile:
[java] [echo] Compiling test.wsdl.addrNoImplSEI
[java] [wsdl2java] WSDL2Java
D:\JAKARTA\xml-axis\java/test/wsdl/addrNoImplSEI/AddressBook.wsdl
[java] [copy] Copying 3 files to
D:\JAKARTA\xml-axis\java\build\work\test\wsdl\addrNoImplSEI
[java] [javac] Compiling 8 source files to
D:\JAKARTA\xml-axis\java\build\classes
[java] [java2wsdl] Java2WSDL
test.wsdl.addrNoImplSEI.AddressBookNoImplSEISoapBindingImpl
[java] [delete] Deleting directory
D:\JAKARTA\xml-axis\java\build\classes\test\wsdl\addrNoImplSEI
[java] [delete] Deleting 10 files from
D:\JAKARTA\xml-axis\java\build\work\test\wsdl\addrNoImplSEI
[java] [wsdl2java] WSDL2Java
D:\JAKARTA\xml-axis\java/build/work/test/wsdl/addrNoImplSEI/AddressBook.wsdl
[java] [copy] Copying 3 files to
D:\JAKARTA\xml-axis\java\build\work\test\wsdl\addrNoImplSEI
[java] [javac] Compiling 10 source files to
D:\JAKARTA\xml-axis\java\build\classes
[java] [foreach]
D:\JAKARTA\xml-axis\java\build\work\test\wsdl\addrNoImplSEI\Main.java:76:
cannot resolve symbol
[java] [foreach] symbol : class Phone
[java] [foreach] location: class test.wsdl.addrNoImplSEI.Main
[java] [foreach] static Phone phone1;
[java] [foreach] ^
[java] [foreach]
D:\JAKARTA\xml-axis\java\build\work\test\wsdl\addrNoImplSEI\Main.java:81:
cannot resolve symbol
[java] [foreach] symbol : class Phone
[java] [foreach] location: class test.wsdl.addrNoImplSEI.Main
[java] [foreach] phone1 = new Phone();
[java] [foreach] ^
[java] [foreach]
D:\JAKARTA\xml-axis\java\build\work\test\wsdl\addrNoImplSEI\Main.java:102:
cannot resolve symbol
[java] [foreach] symbol : class Phone
[java] [foreach] location: class test.wsdl.addrNoImplSEI.Main
[java] [foreach] Phone ph = ad.getPhone();
[java] [foreach] ^
[java] [foreach] 3 errors
--- James M Snell <[EMAIL PROTECTED]> wrote:
> Tell ya what... how about we set a rule that the people who are actually
> doing the work to try to fix the bugs get to determine the process. I'm
> being sarcastic of course, but my point should be clear... if y'all are
> concerned about making sure the build works, please be just as concerned
> about making sure the list of outstanding bugs is being taken care of.
> Successfully building buggy code ain't exactly a useful endeavor. I'd
> rather the builds fail for a few days and know that the bug list is
> getting addressed than have the build be succeeding while the bug list is
> ignored.
>
> - James Snell
> IBM Emerging Technologies
> [EMAIL PROTECTED]
> (559) 587-1233 (office)
> (700) 544-9035 (t/l)
> Programming Web Services With SOAP
> O'Reilly & Associates, ISBN 0596000952
>
> Have I not commanded you? Be strong and courageous.
> Do not be terrified, do not be discouraged, for the Lord your
> God will be with you whereever you go. - Joshua 1:9
>
>
>
> Glen Daniels <[EMAIL PROTECTED]>
> 02/28/2003 10:18 AM
> Please respond to axis-dev
>
>
> To
> Doug Davis/Raleigh/[EMAIL PROTECTED], "'[EMAIL PROTECTED] '"
> <[EMAIL PROTECTED]>
> cc
>
> bcc
>
> Subject
> RE: Check-in's till 1.1 Final Release...
>
>
>
>
> +1, Dug.
>
> Mistakes are gonna happen, that's to be expected, but let's all try to
> keep to this guideline. And if the build breaks, either fix it or roll
> back your changes ASAP.
>
> --Glen
>
> -----Original Message-----
> From: Doug Davis
> To: [EMAIL PROTECTED]
> Sent: 2/28/2003 10:08 AM
> Subject: Re: Check-in's till 1.1 Final Release...
>
>
>
>
>
>
> I would actually suggest that if someone adds code and it exposes a bad
> test then they should be required to fix the testcase as well _before_
> they
> commit the entire lot. "ant clean all-tests" should _always_ work.
> -Dug
>
>
> James M Snell/Fresno/[EMAIL PROTECTED] on 02/28/2003 01:03:51 PM
>
> Please respond to [EMAIL PROTECTED]
>
> To: [EMAIL PROTECTED]
> cc: [EMAIL PROTECTED]
> Subject: Re: Check-in's till 1.1 Final Release...
>
>
> -1 to all automatic roll backs based on a run clean all-tests failure.
> In
> order to respect the work other people are doing to actually shrink the
> buglist, folks should take the time to first see if it's a problem in
> the
> test case that's causing the failure rather than a problem with the
> fixed
> code. If a test fails, please take the time to figure out why.
>
> - James Snell
> IBM Emerging Technologies
> [EMAIL PROTECTED]
> (559) 587-1233 (office)
> (700) 544-9035 (t/l)
> Programming Web Services With SOAP
> O'Reilly & Associates, ISBN 0596000952
>
> Have I not commanded you? Be strong and courageous.
> Do not be terrified, do not be discouraged, for the Lord your
> God will be with you whereever you go. - Joshua 1:9
>
>
>
> Davanum Srinivas <[EMAIL PROTECTED]>
> 02/28/2003 09:43 AM
> Please respond to axis-dev
>
>
> To
> [EMAIL PROTECTED]
> cc
>
> bcc
>
> Subject
> Check-in's till 1.1 Final Release...
>
>
>
> Folks,
>
> PLEASE RUN "ant clean all-tests" before checking things in. If anything
> breaks Gump build ("ant
> clean all-tests") that qualifies for an automatic -1 from me. Also,
> BEFORE
> you run "ant clean
> all-tests", GET the latest sources from CVS...ALSO, PLEASE don't
> introduce
> JDK1.4 specific code.
> It's TOO late in the game to check-in code and expect others to fix
> problems that were introduced.
>
>
> Thanks,
> dims
>
> =====
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Tax Center - forms, calculators, tips, more
> http://taxes.yahoo.com/
>
>
>
>
=====
Davanum Srinivas - http://webservices.apache.org/~dims/
__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/
