You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xmlbeans-dev@xml.apache.org by David Remy <dr...@bea.com> on 2004/06/08 22:24:56 UTC

big tests check-in

I just committed a significant restructuring of the tests in V2
contributed by Yana, Raju, and Fatema.  Essentially this was just moving
in a bunch tests that we still had running at BEA but we needed to move
in to Apache for all committers to take advantage of.  

>From a use perspective it is straightforward.  From the main build file
you can run checkin tests by running:

ant checkin

Before checking in any code in V2 these checkin tests should be run and
pass 100%.

There are also 'detailed' tests which will run a more elaborate test bed
(see the doc links below).  

There is documentation on the test structure, how to add your own tests,
etc at:

Overall test readme.txt
http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/readme.txt?view=m
arkup

Building and Running Tests:
http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/BuildingAndR
unningTests.txt?view=markup

Information on how the tests are organized and other background info at:
http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/TestOrganiza
tion.txt?view=markup

rem




- ---------------------------------------------------------------------
To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/


Re: big tests check-in

Posted by Scott Ziegler <zi...@bea.com>.
It seems a jdk 1.5 dependency has crept in.  Can we make sure that 
everything still works under 1.4.2?  Also, IMO checkintest should
run the build first, similar to how ant drt used to work.

build.test.tools:
    [javac] Compiling 23 source files to /home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
    [javac] javac: invalid flag: -Xlint:deprecation
    [javac] Usage: javac <options> <source files>
    [javac] where possible options include:
    [javac]   -g                        Generate all debugging info
    [javac]   -g:none                   Generate no debugging info
    [javac]   -g:{lines,vars,source}    Generate only some debugging info
    [javac]   -nowarn                   Generate no warnings
    [javac]   -verbose                  Output messages about what the compiler is doing
    [javac]   -deprecation              Output source locations where deprecated APIs are used
    [javac]   -classpath <path>         Specify where to find user class files
    [javac]   -sourcepath <path>        Specify where to find input source files
    [javac]   -bootclasspath <path>     Override location of bootstrap class files
    [javac]   -extdirs <dirs>           Override location of installed extensions
    [javac]   -d <directory>            Specify where to place generated class files
    [javac]   -encoding <encoding>      Specify character encoding used by source files
    [javac]   -source <release>         Provide source compatibility with specified release
    [javac]   -target <release>         Generate class files for specific VM version
    [javac]   -help                     Print a synopsis of standard options


BUILD FAILED
/home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following error occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following error occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile failed; see the compiler error output for details


--Scott

On Tuesday 08 June 2004 13:24, David Remy wrote:
> I just committed a significant restructuring of the tests in V2
> contributed by Yana, Raju, and Fatema.  Essentially this was just moving
> in a bunch tests that we still had running at BEA but we needed to move
> in to Apache for all committers to take advantage of.
>
> From a use perspective it is straightforward.  From the main build file
> you can run checkin tests by running:
>
> ant checkin
>
> Before checking in any code in V2 these checkin tests should be run and
> pass 100%.
>
> There are also 'detailed' tests which will run a more elaborate test bed
> (see the doc links below).
>
> There is documentation on the test structure, how to add your own tests,
> etc at:
>
> Overall test readme.txt
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/readme.txt?view=m
> arkup
>
> Building and Running Tests:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/BuildingAndR
> unningTests.txt?view=markup
>
> Information on how the tests are organized and other background info at:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/TestOrganiza
> tion.txt?view=markup
>
> rem
>
>
>
>
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
> Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/

- ---------------------------------------------------------------------
To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/


Re: big tests check-in

Posted by Scott Ziegler <zi...@bea.com>.
More 1.5 issues:

build.test.tools:
    [javac] Compiling 23 source files to
/home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
    [javac]
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/JUnitXTask.java:195: cannot resolve symbol
    [javac] symbol  : method contains (java.lang.String)
    [javac] location: class java.lang.String
    [javac]                     if (! pathname.contains("$"))
    [javac]                                   ^
    [javac]
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/XmlResultFormatter.java:225: cannot resolve symbol
    [javac] symbol  : method contains (java.lang.String)
    [javac] location: class java.lang.String
    [javac]         if (t.toString().contains("ClassNotFoundException"))
    [javac]                       ^
    [javac]
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/XmlResultFormatterImpl.java:193: cannot resolve symbol
    [javac] symbol  : method contains (java.lang.String)
    [javac] location: class java.lang.String
    [javac]         if (t.toString().contains("ClassNotFoundException"))
    [javac]                       ^
    [javac] Note:
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/JUnitXTask.java uses or overrides a deprecated API.
    [javac] Note: Recompile with -deprecation for details.
    [javac] 3 errors

BUILD FAILED
/home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile failed;
see the compiler error output for details.


On Tue, 2004-06-08 at 14:52, Scott Ziegler wrote:

> It seems a jdk 1.5 dependency has crept in...
> 
> build.test.tools:
>     [javac] Compiling 23 source files to
> /home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
>     [javac] javac: invalid flag: -Xlint:deprecation
>     [javac] Usage: javac <options> <source files>
>     [javac] where possible options include:
>     [javac]   -g                        Generate all debugging info
>     [javac]   -g:none                   Generate no debugging info
>     [javac]   -g:{lines,vars,source}    Generate only some debugging
> info
>     [javac]   -nowarn                   Generate no warnings
>     [javac]   -verbose                  Output messages about what the
> compiler is doing
>     [javac]   -deprecation              Output source locations where
> deprecated APIs are used
>     [javac]   -classpath <path>         Specify where to find user
> class files
>     [javac]   -sourcepath <path>        Specify where to find input
> source files
>     [javac]   -bootclasspath <path>     Override location of bootstrap
> class files
>     [javac]   -extdirs <dirs>           Override location of installed
> extensions
>     [javac]   -d <directory>            Specify where to place
> generated class files
>     [javac]   -encoding <encoding>      Specify character encoding
> used by source files
>     [javac]   -source <release>         Provide source compatibility
> with specified release
>     [javac]   -target <release>         Generate class files for
> specific VM version
>     [javac]   -help                     Print a synopsis of standard
> options
> 
> 
> BUILD FAILED
> /home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error
> occured while executing this line
> /home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following
> error occured while executing this line
> /home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following
> error occured while executing this line
> /home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile
> failed; see the compiler error output for details
> 
> Can we make sure everything still works in jdk 1.4.2?  
> 
> Also, IMO "ant checkintest" should build if needed like "ant drt" used
> to.
> 
> --Scott
> 
> On Tue, 2004-06-08 at 13:24, David Remy wrote: 
> 
> > I just committed a significant restructuring of the tests in V2
> > contributed by Yana, Raju, and Fatema.  Essentially this was just moving
> > in a bunch tests that we still had running at BEA but we needed to move
> > in to Apache for all committers to take advantage of.  
> > 
> > >From a use perspective it is straightforward.  From the main build file
> > you can run checkin tests by running:
> > 
> > ant checkin
> > 
> > Before checking in any code in V2 these checkin tests should be run and
> > pass 100%.
> > 
> > There are also 'detailed' tests which will run a more elaborate test bed
> > (see the doc links below).  
> > 
> > There is documentation on the test structure, how to add your own tests,
> > etc at:
> > 
> > Overall test readme.txt
> > http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/readme.txt?view=m
> > arkup
> > 
> > Building and Running Tests:
> > http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/BuildingAndR
> > unningTests.txt?view=markup
> > 
> > Information on how the tests are organized and other background info at:
> > http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/TestOrganiza
> > tion.txt?view=markup
> > 
> > rem
> > 
> > 
> > 
> > 
> > - ---------------------------------------------------------------------
> > To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
> > Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
> > 

Re: big tests check-in

Posted by Scott Ziegler <zi...@bea.com>.
More 1.5 issues:

build.test.tools:
    [javac] Compiling 23 source files to
/home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
    [javac]
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/JUnitXTask.java:195: cannot resolve symbol
    [javac] symbol  : method contains (java.lang.String)
    [javac] location: class java.lang.String
    [javac]                     if (! pathname.contains("$"))
    [javac]                                   ^
    [javac]
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/XmlResultFormatter.java:225: cannot resolve symbol
    [javac] symbol  : method contains (java.lang.String)
    [javac] location: class java.lang.String
    [javac]         if (t.toString().contains("ClassNotFoundException"))
    [javac]                       ^
    [javac]
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/XmlResultFormatterImpl.java:193: cannot resolve symbol
    [javac] symbol  : method contains (java.lang.String)
    [javac] location: class java.lang.String
    [javac]         if (t.toString().contains("ClassNotFoundException"))
    [javac]                       ^
    [javac] Note:
/home/zieg/apache_cvs/xml-xmlbeans/v2/test/tools/src/tools/JUnit/JUnitXTask.java uses or overrides a deprecated API.
    [javac] Note: Recompile with -deprecation for details.
    [javac] 3 errors

BUILD FAILED
/home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile failed;
see the compiler error output for details.


On Tue, 2004-06-08 at 14:52, Scott Ziegler wrote:

> It seems a jdk 1.5 dependency has crept in...
> 
> build.test.tools:
>     [javac] Compiling 23 source files to
> /home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
>     [javac] javac: invalid flag: -Xlint:deprecation
>     [javac] Usage: javac <options> <source files>
>     [javac] where possible options include:
>     [javac]   -g                        Generate all debugging info
>     [javac]   -g:none                   Generate no debugging info
>     [javac]   -g:{lines,vars,source}    Generate only some debugging
> info
>     [javac]   -nowarn                   Generate no warnings
>     [javac]   -verbose                  Output messages about what the
> compiler is doing
>     [javac]   -deprecation              Output source locations where
> deprecated APIs are used
>     [javac]   -classpath <path>         Specify where to find user
> class files
>     [javac]   -sourcepath <path>        Specify where to find input
> source files
>     [javac]   -bootclasspath <path>     Override location of bootstrap
> class files
>     [javac]   -extdirs <dirs>           Override location of installed
> extensions
>     [javac]   -d <directory>            Specify where to place
> generated class files
>     [javac]   -encoding <encoding>      Specify character encoding
> used by source files
>     [javac]   -source <release>         Provide source compatibility
> with specified release
>     [javac]   -target <release>         Generate class files for
> specific VM version
>     [javac]   -help                     Print a synopsis of standard
> options
> 
> 
> BUILD FAILED
> /home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error
> occured while executing this line
> /home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following
> error occured while executing this line
> /home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following
> error occured while executing this line
> /home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile
> failed; see the compiler error output for details
> 
> Can we make sure everything still works in jdk 1.4.2?  
> 
> Also, IMO "ant checkintest" should build if needed like "ant drt" used
> to.
> 
> --Scott
> 
> On Tue, 2004-06-08 at 13:24, David Remy wrote: 
> 
> > I just committed a significant restructuring of the tests in V2
> > contributed by Yana, Raju, and Fatema.  Essentially this was just moving
> > in a bunch tests that we still had running at BEA but we needed to move
> > in to Apache for all committers to take advantage of.  
> > 
> > >From a use perspective it is straightforward.  From the main build file
> > you can run checkin tests by running:
> > 
> > ant checkin
> > 
> > Before checking in any code in V2 these checkin tests should be run and
> > pass 100%.
> > 
> > There are also 'detailed' tests which will run a more elaborate test bed
> > (see the doc links below).  
> > 
> > There is documentation on the test structure, how to add your own tests,
> > etc at:
> > 
> > Overall test readme.txt
> > http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/readme.txt?view=m
> > arkup
> > 
> > Building and Running Tests:
> > http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/BuildingAndR
> > unningTests.txt?view=markup
> > 
> > Information on how the tests are organized and other background info at:
> > http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/TestOrganiza
> > tion.txt?view=markup
> > 
> > rem
> > 
> > 
> > 
> > 
> > - ---------------------------------------------------------------------
> > To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
> > For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
> > Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
> > 

Re: big tests check-in

Posted by Scott Ziegler <zi...@bea.com>.
It seems a jdk 1.5 dependency has crept in...

build.test.tools:
    [javac] Compiling 23 source files to
/home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
    [javac] javac: invalid flag: -Xlint:deprecation
    [javac] Usage: javac <options> <source files>
    [javac] where possible options include:
    [javac]   -g                        Generate all debugging info
    [javac]   -g:none                   Generate no debugging info
    [javac]   -g:{lines,vars,source}    Generate only some debugging
info
    [javac]   -nowarn                   Generate no warnings
    [javac]   -verbose                  Output messages about what the
compiler is doing
    [javac]   -deprecation              Output source locations where
deprecated APIs are used
    [javac]   -classpath <path>         Specify where to find user class
files
    [javac]   -sourcepath <path>        Specify where to find input
source files
    [javac]   -bootclasspath <path>     Override location of bootstrap
class files
    [javac]   -extdirs <dirs>           Override location of installed
extensions
    [javac]   -d <directory>            Specify where to place generated
class files
    [javac]   -encoding <encoding>      Specify character encoding used
by source files
    [javac]   -source <release>         Provide source compatibility
with specified release
    [javac]   -target <release>         Generate class files for
specific VM version
    [javac]   -help                     Print a synopsis of standard
options


BUILD FAILED
/home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile failed;
see the compiler error output for details

Can we make sure everything still works in jdk 1.4.2?  

Also, IMO "ant checkintest" should build if needed like "ant drt" used
to.

--Scott

On Tue, 2004-06-08 at 13:24, David Remy wrote:

> I just committed a significant restructuring of the tests in V2
> contributed by Yana, Raju, and Fatema.  Essentially this was just moving
> in a bunch tests that we still had running at BEA but we needed to move
> in to Apache for all committers to take advantage of.  
> 
> From a use perspective it is straightforward.  From the main build file
> you can run checkin tests by running:
> 
> ant checkin
> 
> Before checking in any code in V2 these checkin tests should be run and
> pass 100%.
> 
> There are also 'detailed' tests which will run a more elaborate test bed
> (see the doc links below).  
> 
> There is documentation on the test structure, how to add your own tests,
> etc at:
> 
> Overall test readme.txt
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/readme.txt?view=m
> arkup
> 
> Building and Running Tests:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/BuildingAndR
> unningTests.txt?view=markup
> 
> Information on how the tests are organized and other background info at:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/TestOrganiza
> tion.txt?view=markup
> 
> rem
> 
> 
> 
> 
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
> Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
> 

Re: big tests check-in

Posted by Scott Ziegler <zi...@bea.com>.
It seems a jdk 1.5 dependency has crept in...

build.test.tools:
    [javac] Compiling 23 source files to
/home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
    [javac] javac: invalid flag: -Xlint:deprecation
    [javac] Usage: javac <options> <source files>
    [javac] where possible options include:
    [javac]   -g                        Generate all debugging info
    [javac]   -g:none                   Generate no debugging info
    [javac]   -g:{lines,vars,source}    Generate only some debugging
info
    [javac]   -nowarn                   Generate no warnings
    [javac]   -verbose                  Output messages about what the
compiler is doing
    [javac]   -deprecation              Output source locations where
deprecated APIs are used
    [javac]   -classpath <path>         Specify where to find user class
files
    [javac]   -sourcepath <path>        Specify where to find input
source files
    [javac]   -bootclasspath <path>     Override location of bootstrap
class files
    [javac]   -extdirs <dirs>           Override location of installed
extensions
    [javac]   -d <directory>            Specify where to place generated
class files
    [javac]   -encoding <encoding>      Specify character encoding used
by source files
    [javac]   -source <release>         Provide source compatibility
with specified release
    [javac]   -target <release>         Generate class files for
specific VM version
    [javac]   -help                     Print a synopsis of standard
options


BUILD FAILED
/home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following error
occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile failed;
see the compiler error output for details

Can we make sure everything still works in jdk 1.4.2?  

Also, IMO "ant checkintest" should build if needed like "ant drt" used
to.

--Scott

On Tue, 2004-06-08 at 13:24, David Remy wrote:

> I just committed a significant restructuring of the tests in V2
> contributed by Yana, Raju, and Fatema.  Essentially this was just moving
> in a bunch tests that we still had running at BEA but we needed to move
> in to Apache for all committers to take advantage of.  
> 
> From a use perspective it is straightforward.  From the main build file
> you can run checkin tests by running:
> 
> ant checkin
> 
> Before checking in any code in V2 these checkin tests should be run and
> pass 100%.
> 
> There are also 'detailed' tests which will run a more elaborate test bed
> (see the doc links below).  
> 
> There is documentation on the test structure, how to add your own tests,
> etc at:
> 
> Overall test readme.txt
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/readme.txt?view=m
> arkup
> 
> Building and Running Tests:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/BuildingAndR
> unningTests.txt?view=markup
> 
> Information on how the tests are organized and other background info at:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/TestOrganiza
> tion.txt?view=markup
> 
> rem
> 
> 
> 
> 
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
> Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/
> 

Re: big tests check-in

Posted by Scott Ziegler <zi...@bea.com>.
It seems a jdk 1.5 dependency has crept in.  Can we make sure that 
everything still works under 1.4.2?  Also, IMO checkintest should
run the build first, similar to how ant drt used to work.

build.test.tools:
    [javac] Compiling 23 source files to /home/zieg/apache_cvs/xml-xmlbeans/v2/build/test/tools
    [javac] javac: invalid flag: -Xlint:deprecation
    [javac] Usage: javac <options> <source files>
    [javac] where possible options include:
    [javac]   -g                        Generate all debugging info
    [javac]   -g:none                   Generate no debugging info
    [javac]   -g:{lines,vars,source}    Generate only some debugging info
    [javac]   -nowarn                   Generate no warnings
    [javac]   -verbose                  Output messages about what the compiler is doing
    [javac]   -deprecation              Output source locations where deprecated APIs are used
    [javac]   -classpath <path>         Specify where to find user class files
    [javac]   -sourcepath <path>        Specify where to find input source files
    [javac]   -bootclasspath <path>     Override location of bootstrap class files
    [javac]   -extdirs <dirs>           Override location of installed extensions
    [javac]   -d <directory>            Specify where to place generated class files
    [javac]   -encoding <encoding>      Specify character encoding used by source files
    [javac]   -source <release>         Provide source compatibility with specified release
    [javac]   -target <release>         Generate class files for specific VM version
    [javac]   -help                     Print a synopsis of standard options


BUILD FAILED
/home/zieg/apache_cvs/xml-xmlbeans/v2/build.xml:823: Following error occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:650: Following error occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:403: Following error occured while executing this line
/home/zieg/apache_cvs/xml-xmlbeans/v2/testbuild.xml:426: Compile failed; see the compiler error output for details


--Scott

On Tuesday 08 June 2004 13:24, David Remy wrote:
> I just committed a significant restructuring of the tests in V2
> contributed by Yana, Raju, and Fatema.  Essentially this was just moving
> in a bunch tests that we still had running at BEA but we needed to move
> in to Apache for all committers to take advantage of.
>
> From a use perspective it is straightforward.  From the main build file
> you can run checkin tests by running:
>
> ant checkin
>
> Before checking in any code in V2 these checkin tests should be run and
> pass 100%.
>
> There are also 'detailed' tests which will run a more elaborate test bed
> (see the doc links below).
>
> There is documentation on the test structure, how to add your own tests,
> etc at:
>
> Overall test readme.txt
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/readme.txt?view=m
> arkup
>
> Building and Running Tests:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/BuildingAndR
> unningTests.txt?view=markup
>
> Information on how the tests are organized and other background info at:
> http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v2/test/docs/TestOrganiza
> tion.txt?view=markup
>
> rem
>
>
>
>
> - ---------------------------------------------------------------------
> To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
> For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
> Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/

- ---------------------------------------------------------------------
To unsubscribe, e-mail:   xmlbeans-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xmlbeans-dev-help@xml.apache.org
Apache XMLBeans Project -- URL: http://xml.apache.org/xmlbeans/