FWIW, I've used Torque with Ant & Eclipse for years and have only recently started using Maven (to test the code I've been submitting recently ;-) ). So, even though Maven makes it easier, it's not a requirement.. (All the Maven-ites groan because I'm getting up on my Torque with Ant/Eclipse soapbox...8P )
Here's a link to a quick start on how to use Torque with Ant only e-mail I sent out a while back in response to a similar question. http://www.mail-archive.com/torque-user@db.apache.org/msg04509.html To integrate with Eclipse, I just add Ant as a project builder (make sure to specify "refresh" in the options). Oh, and FWIW, I generally have a "Shared Libs" project with all the required Jars / Source Jars that my apps need (and matches the libs on our production servers. This project exports all of them and I add it as a required project to all my sub projects. As to the larger question of there being a torque build tool, e.g. "java torque-generate...". This might be nice if it simpified what people needed to know to get started. But I'm not sure if it's REALLY that much different than doing ant -f torque-build.xml target. IMHO, a large part of the setup problems comes from just getting all the required Jars, etc, into your classpath. (Which Maven makes simple :-) ). A torque build tool would still have to have all these installed as well (including ant). On the other hand, if you packaged it like ant with all things needed included, it might be nice to be able to have a command line "torque" tool. Feel free to put one together and submit it 8-).. maybe build a GUI for setting options/creating properties files.. lol. -----Original Message----- From: Matthias Klein [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 1:33 PM To: torque-user@db.apache.org Subject: Re: Is Maven really necessary? Okay, I tried this: 1. Installing maven 2. writing the two schema xml files and the project.properties 3. invoked the generator with "maven torque" It all worked perfectly fine so far. Since I executed all this in my project directory, the classes are even where they are supposed to be. After a "refresh" even my IDE knows about them. As you suggested, now I would like to do the "rest" with my IDE (until I use maven for my project, too) Question 1: Is that even possible to now keep going with "developing as usual"? Of course, the list of dependencies will have to be resolved first. But Question 2: Is all I need to do add all required jars and plugins in my /lib folder? Question 3: Is there no one single dependecies file that I can download and unpack it into my /lib ? (Doing this one by one is way too cumbersome - and might force me to start using maven NOW :-) Thanks Matt Am Mi, 24.05.2006, 18:00, schrieb Matthias Klein: >>> Shouldn't it be sufficient to generate them into a source directory >>> Eclipse knows about? >>> > > That's what I hoped for. I am currently trying this approach (still > writing my project-schema.xml, though :-) So I should know soon > > > > Am Mi, 24.05.2006, 17:42, schrieb Thomas Vandahl: > >> Matthias Klein wrote: >> >> >>> I am familiar with Ant and still would like to do this ad-hoc type >>> development in a simpler fashion. However, since all of you here >>> seem to disagree, I assume my best bet is to wrap my head around >>> maven to be able to appreciate its advantages. Hey, may be I will >>> even like that tool once I am done with it. Who knows. Oh well. May >>> be maven is the way to go then... >> >> You may have a look at Mevenide or the ANT integration of Eclipse. >> Especially the Maven integration is very useful. >> >> >> >> BTW, why do you have to compile the Torque classes using Maven? >> Shouldn't it be sufficient to generate them into a source directory >> Eclipse knows about? >> >> >> >> >> Bye, Thomas. >> >> >> >> --------------------------------------------------------------------- >> 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] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
