Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
Re-licensed all stuff according to new rules
Removed trailing blanks
Updated licenses
move runtime in place
copy runtime
Added the possibility to divide the generated code in several packages. This is configured via the generator configuration properties, see the generator properties reference for details. This should have gone into rc1 and I thought I already committed it last monday morning, but it seems the changes got lost due to the hardware works on cvs.apache.org
missed one schema directory last time, changed another directory from /schema to /src/schema
copy test schema for runtimetest to the right directory
change output path for the datadtd task to the schema dir (where the datasql task looks for it)
use maven.repo.local to get the path for the jdbc driver
separate tests for ojb
more cleanup of the runtime test build
cleanup build for runtime tests
update rttest to use the generator
the runtime tests now include the generation of ojb stuff
o TRQS95: Junit tests for sql2xml task (SQLToAppDataTest) o create junit report for runtime tests in target/test-reports if you update the site you should run the runtimetests first (i will change the setup to run the truntimetests by default using axion sometimes ;-)
fix testbed after fixing TRQS86
Added the token APPLICATION_ROOT since the Torque.properties is now being generated straight from Torque.master.
Removed the rttest-specifc versions of Torque.properties and build-test.xml as I could see no significant differences between them and there more prominent defaults.
Part of the patch by Scott Eade <seade@backstagetech.com.au> to get build-torque.xml working again (requires maven.home to be set).
some property changes to allow the rttest's to work. PR: Obtained from: Submitted by: Reviewed by:
sql-test: Fix by Bill Schneider <bschneider@vecna.com> for the DATABASE_URL pre-processor token.
The new pool in commons-jdbc2pool was moved to dbcp. There is little reason to keep the sandbox project open for torque's pool, so I am putting it back into the torque source tree. It is a functional pool, but I would not recommend further development on it. Also reverted the log4j dependency as the new one was not in turbine/jars or turbine/jars2 and the build works with the older version. PR: Obtained from: Submitted by: Reviewed by:
patch by Stephen Haberman <stephenh@chase3000.com> Here's the patch with the deprecation of the project- targets and moving/renaming all of the taskdefs to the beginning of the file.
fix test environment
patch by Stephen Haberman <stephenh@chase3000.com>
A summary of the changes I made:
build-test.xml - removed all references to -classpath targets and
instead when test-classpath is called, initially set the
useClasspath=true, then execute test as normal.
src/conf/build.torque.xml - removed all the -classpath targets and added
useClasspath="${useClasspath}" to each of the corresponding
non-classpath targets.
src/conf/build.properties - added the useClasspath property, defaulted
to false, along with a description of what it does.
build.xml - small change in the description of the test-classpath
target.
xdocs/index.xml - removed the wording about the -classpath targets on
the home page.
merge of the JDBC2POOL branch. PR: Obtained from: Submitted by: Reviewed by:
add missing -classpath targets and a testbed using all -cp tasks
fix the old build system and the testbed
Updating Torque to use the separated JCS classes.
classes from commons-util have moved to commons-collections and commons-lang
Prevent the FileNotFoundException: bin/test/logs/jcs.log I have been getting. With this logs directory in place my tests of SapDB now succeed.
* add stratum to test environment * echo stratus.jar
switch to using the jaxp api. Lost the ability to have conditional validation, but that feature tended to lead to more questions from new users that were not validating. So I am not worried about losing it. If it is an issue we could possibly add a property to shut off validation. updating to xerces2, whose release is imminent. PR: Obtained from: Submitted by: Reviewed by:
add documentationTask to the testbed
fix settings for TorqueDataSqlTask and add it to the testbed thanks to Dan.Everton@Australia.Boeing.com
use velocity-1.3-dev and remove the requirement for logkit (velocity now uses log4j if logkit is not found :-))
- remove the fork from the process that executes the runtime tests (hopefully we can make a junit test of this soon) so that if the runtime tests fail for whatever reason that the testing process will stop so you can see what's going on when it fails. PR: Obtained from: Submitted by: Reviewed by:
- the runtime tests are now independent of the distribution
- added the start of an sql testbed for making sure the sql generated
for each supported database is correct. i will steal the testbed in
velocity that is uses to test generated output. so far i've found
problems with primary keys. these are not automated yet but the
base is there.
- all the test classes are now in the org.apache.torque.test package
- tried to get rid of most of the ${project} references but there
are still some in the standard build file. my changes got nuked
when we started the testbed. all the targets should use <filesets>
now and not individual files.
PR:
Obtained from:
Submitted by:
Reviewed by:
- change name of NOTES file to try and work around possible windows problem. PR: Obtained from: Submitted by: Reviewed by:
- excluding the type test schema from the main testing right now because it fails miserably. it will need quite a bit of work to pass the test. - cleaned out all the code in Torque.java for fudging the category to use for logging. log4j properties files have to used correctly and all classes in Torque now use the Category c = Category.getInstance(x) method now. PR: Obtained from: Submitted by: Reviewed by:
rttests: - fix settings for JDBCTransformTask - exclude DataSQLTask (not working yet)
add more test to the testbed
- adding filtering to the copying of the test schemas and config so that they conform to the profile being used for testing. PR: Obtained from: Submitted by: Reviewed by:
initialize idbroker values
add jdbc-driver jar to classpath for runtime test
smal fixes for runtime test
- move runtime tests to its own directory (to make rt and junit test independend) - change bookstore-schema to make it usefull for tests
profile setup
- adding more testing phases. we now have -> create sql -> create sql for database creation -> create database -> insert sql files into appropriate database -> create OM -> compile OM -> startup torque now i need to add some code to the TorqueRunner to save() and delete() objects. than i can test fedor's tasks when the database(s) have been populated by TorqueRunner. PR: Obtained from: Submitted by: Reviewed by:
- adding compile to the test-project-om target so that we can move to the next phase of using our generated classes in our little TorqueRunner. removing the scripts for testing as they are handled in the testbed now. PR: Obtained from: Submitted by: Reviewed by:
- more steps toward a complete test bed. PR: Obtained from: Submitted by: Reviewed by:
- added some notes about testing the sql generation. PR: Obtained from: Submitted by: Reviewed by:
- preparing for the long haul :-) PR: Obtained from: Submitted by: Reviewed by:
- start of the test harness for all of torque PR: Obtained from: Submitted by: Reviewed by:
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |