FWIW, I'm -0.25 on integrating it into the Runtime jar for this version. Mostly because of possible support issues around having an old version of Village in the classpath with new code in the Torque jar. This probably won't be a developer problem because Maven, et al, handle the dependencies. But I can see it happening on established production servers where removing old jars are often forgotten.
Now that we "own" the code, we're going to be able to put in misc "patches" for various problems. So I can see issues coming up due to jar miss-matches with classes in two places. IHMO, it seems much cleaner to keep it as a separate jar until it's totally re-packaged into the org.apache.torque (or some such) package. Doing this would require a lot of testing. > -----Original Message----- > From: Thomas Vandahl [mailto:[EMAIL PROTECTED] > Sent: Saturday, October 13, 2007 10:36 AM > To: Apache Torque Developers List > Subject: Re: torque 3.3 schedule > > Thomas Fischer wrote: > > how do you plan to integrate village anyway ? Into the > runtime or as > > separate jar ? (Personally I'd prefer a separate jar.) > > My preference was to integrate it directly into the runtime > jar with the option of building it as a separate artifact, if > someone so desires. > > Bye, Thomas. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > DukeCE 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]
