db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From torque-...@db.apache.org
Subject [DB Torque Wiki] Updated: NextRelease
Date Tue, 27 Apr 2004 13:53:14 GMT
   Date: 2004-04-27T06:53:14
   Editor: ScottEade <seade@backstagetech.com.au>
   Wiki: DB Torque Wiki
   Page: NextRelease
   URL: http://wiki.apache.org/db-torque/NextRelease

   typo only

Change Log:

------------------------------------------------------------------------------
@@ -21,7 +21,7 @@
  * Correctly generate index and unique constraint names for PostgreSQL (see: ["PostgreSQLFAQ"])
  * Allow override of database name at generation time
    * If specified the torque.database.name property should be user rather than name attribute
of the database tag.  This would make it much easier to handle multiple instances of an application
on a single system, e.g. dev and test database instances being generated from a single schema.
- * Is it just me or are a number of the torque peoperties required to be declared outside
of the file referred to in torque.contextProperties?  Could the Torque Maven plugin read the
properties in as well, making it so that project.properties need only define torque.contextProperties?
 This would make it much easier to handle multiple application instances built from the same
environment (I run a number of filters across my properties file to customise it for the application/database
instance I am generating before I execute the generator).
+ * Is it just me or are a number of the torque properties required to be declared outside
of the file referred to in torque.contextProperties?  Could the Torque Maven plugin read the
properties in as well, making it so that project.properties need only define torque.contextProperties?
 This would make it much easier to handle multiple application instances built from the same
environment (I run a number of filters across my properties file to customise it for the application/database
instance I am generating before I execute the generator).
  * IMHO the Torque Maven plugin is very difficult to use due to varying versions of Maven
and Torque (I had to actually hack the plugin to get things working).  In particular I think
we really need to support:
    * Multiple versions of Torque.
    * The ability to add further versions outside of the Maven release cycle.

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message