|
Maven, managing source code.: msg#00016jakarta.turbine.torque.user
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 |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: How to save / load LOBs in Postgres with Torque: 00016, Saravana Krishnan |
|---|---|
| Next by Date: | Re: Schema.xml alter, not overwrite: 00016, Henning P. Schmiedehausen |
| Previous by Thread: | How to save / load LOBs in Postgres with Torquei: 00016, Robert Bowen |
| Next by Thread: | Re: Maven, managing source code.: 00016, Henning P. Schmiedehausen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |