Hey Travis,
I actually do my settings a bit differently than Henning does, so I'll tell you how I do it and you can see which method works best for you... I simply make all Torque generated code a member of the package torque and check all of it in. Nine times out of ten I'm not working with those classes, so it soon becomes a royal pain in the ass to wait for Torque to rebuild those classes if you don't need for them to be. All you need to do is include the property "torque.targetPackage = torque" in your project.properties.
Also, it makes for interesting diffs when you rebuild those classes with different versions of torque. For me it gives a nice comparison on how the different versions actually effect my code. For your case, Table.java should remain intact anyway.
Not as slick as the method as Henning uses, but quite workable.
Davin Atkins
Travis Stevens wrote:
Hello.
The maven-torque-plugin is fantastic. However, I am having trouble managing the source. Torque generates Base classes and blank Subclasses of those for developers to add functionality for both Peer and Bean-like objects. For one table I end up with BaseTable.java, BaseTablePeer.java, Table.java and TablePeer.java. I then modify Table.java for various reason.
In this scenario, I would think that the best way to manage source code is to check only Table.java into CVS. That, along with the -schema.xml files, I am able to easily regenerate the state. However, this becomes very messy because the generated classes are in the src directory.
Anyone have any suggestions on how to handle this?
I also use Axis wsdl2java maven plugin. The axis plugin generates code into the target directory which makes sense. I would suggest Torque move to this model. If Table.java is not in the src directory, create it in the target directory. If a developer wishes to modify Table.java, then it is their job to move it into the source directory.
-Trav
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
