Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
Make sure the license is in the distribution.
Put LICENSE and NOTICE to the right place and make sure they are contained in the distribution.
Re-licensed all stuff according to new rules
Removed trailing blanks
Updated licenses
add a "dist.bundle" property which makes it possible to select the elements going into the binary distribution with a property in the POM, thus removing the necessity to hard code them in maven.xml
move runtime in place
we do not need all the plugins in the lib directory of the binary distribution
fix up runtime test references
copy only project.xml and project.properties from the common directory
- add default goal for maven 1.0.x - copy all files from common into src-distribution
copy runtime
add check for torque.testProfile to maven.xml
do not include src/maven-plugin directory in teh source distribution
copy test schema for runtimetest to the right directory
add failonerror=false to copying of src/conf because the directory does not exist in the maven plugin
specify the files to include from the conf directory in order to not include them in the generator build
include the contents of the conf directory in the binary release do not include the contents of the src/generator directory in the source release
moved default target from maven.xml to project.xml also released project-base.xml in source distribution to make its build work
Merged the TORQUE_3_1_Branch into HEAD. The 3_1_Branch was tagged before merging with TORQUE_3_1_BRANCH_BEFORE_MERGE the HEAD was tagged before merging with TORQUE_HEAD_BEFORE_MERGE_OF_3_1_BRANCH The basic idea was to take the generator from HEAD and the runtime and maven plugin from 3_1_BRANCH. Because quite a few changes have amounted, I changed the name of the current version to 3.2 A detailed changelog can be found at the developers mailing list, the title of the mail is changelog: merge of Torque_3_1_BRANCH with HEAD I checked that the runtimetest runs against a Oracle 9.2 database. Things which definitely need checking are - check postgresql and Derby support - The docs/changes.html page is not generated by "maven xdoc". No idea why, but it is also not generated in the 3_1_Branch. They also do not appear on the website... Although I tried to be very cautios, there are many changes and chances are that some bugs have sneaked in. PLEASE TEST THIS !!!!
ASL 2.0
java:jar is deprecated - use jar:jar instead.
Torque.master: set pool.validationQuery using a filter (replacing @VALIDATION_QUERY@) this allows to define the validationQuery in profiles and conf/database/xyz files (as the query depends on the used db this is needed to allow using the jdbc2pool as default) use jdbc2pool as default add validationQuery property to all profiles and conf/database/xyz files
separate tests for ojb
more cleanup of the runtime test build
prepare 3.1-alpha1
default.properites moved to the generator
update rttest to use the generator
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.
add dist:lite goal
update profiles - use torque. property names - remove properties taken from default.properties
Okay, the previous checkin wasn't what I added...the src/templates dir was included in the templates' paths in the jar, so fall back on the old way that worked.
Let maven copy the templates into the torque jar.
Maven automatically puts the torque jar in ${maven.dist.bin.assembly.dir}, so move it to lib instead. Avoids having duplicate torque jars in both the / and /lib dirs in the dist.
move loading of torque.testProfile to runtime:prepare so it only needs to be set if you want to run the testbed
make testbed work with maven-b5 maven buils a complete dist in /target/test/rttest and uses src/rttest/build-test.xml to run the tests the legacy build should do the same and the old build-test.xml should be removed there is one problem left to solve: test.datasql and test-jdbc don't work when called from maven if you run the testbed using ant from /target/test/rttest it works
include libs and other stuff to binary dists the dists can now be built using maven-b5 :-)
1. Fixed the maven-b5 build to cope over the default.properties file correctly. 2. Changed the managers so that the syntax to specify an alternate manager for a class uses the fully qualified classname. Old: torque.managers.FooManager.classname = org.company.FooManager New: torque.managed_class.org.company.Foo.manager = org.company.FooManager This change allows multiple OM classes with the same name (from several different legacy databases, for example) to use the managers without conflicting with one another.
Need to copy the templates into the torque jar as well.
o Add a maven.xml to set up a postGoal for the compile phase to copy the database.dtd into the right location. 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 |