Hello Stephen, I wanted to try out this patch but I have a few questions about it.
We've found it combersome to try and use Torque in our projects from a configuration standpoint. We've had to make application specific versions of build-torque.xml file to use it in our apps. Ideally We would only work with a build.properties file and within that file we would specify the necessary directories such as the torque home directory, ouput directories for sql and OM java files, etc... I know that some of these properties can already be specified, but not to the point that they are independent of torque-build.xml. The application would then only contain the torque-build.properties file. Does this patch address these issues? Thanks, Byron Stephen Haberman wrote: > Okay, for some stupid reason I assumed that the last standalone patch I > posted would work because it worked for my maven project. I ran into > some misc. problems today and in the process realized the patch probably > never worked for either non-classpath or non-maven project. > > I've now tested it with/without maven and with/without the -classpath > targets. I'm humbly resubmitting it to the list if anyone like to try it > again (or for the first time). > > If I'm not approaching it the right way, am missing something, or should > just stop trying altogether, let me know. > > (Btw, rather than having targets for both classpath and non-classpath > tasks, wouldn't it be a heck of a lot easier to just have it be a > property in the build.properties and get rid of all the duplicate > targets?) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
