Thomas, I am afraid I agree with Greg that the village source distribution needs a rebuild because the common subdirectory is missing. The rest is ok IMHO.
What I checked in detail: Source distribution (in ~tv/torque): Before testing I cleaned my maven 1 repository of RC3 stuff. I can confirm the village compile problems using maven 1.0.2. I can not confirm the generator compile problems (after adding the templates manually to the repository the generatorc builds fine. Manually installing the templates is not problematic because as plain text they are both source and binary). The runtime compiles fine after village is added manually to the manen repo. I used maven 1.0.2 (which is, by the way, still the recommended maven version according to the website). I did not check any ant builds because maven 1 is the primary build system. I ran the test project using mysql and postgresql with the built sources and it ran ok. I checked the test project uses the RC3 stuff, -------------------- binary distribution (in ~tv/torque and ~tv/torque/plugins) I re-cleaned the maven 1 repository and installed the jars from the binary tar.gz's and the plugin from ~tv/torque/plugins manually. Then I re-ran the test project for mysql and postgresql and it worked allright. ------------------- md5sums and signatures I checked a few random signatures and md5sums and all were ok. -------------------- maven 2 build (~tv/torque/m2-build): I replaced my org/apache/torque part of my m2 repository with the files in the above directory and ran the test project via maven 2. This runs fine for both mysql and postgresql after downgrading maven2 from 2.0.8 to 2.0.4 (2.0.8 complains that "Class org/codehaus/plexus/util/xml/Xpp3Dom violates loader constraints" which is a maven2 problem and not ours) ------------------ Thomas, if you need help fixing the village source distribution just tell me. Thomas -----"Greg Monroe" <[EMAIL PROTECTED]> schrieb: ----- >An: "Apache Torque Developers List" <[email protected]> >Von: "Greg Monroe" <[EMAIL PROTECTED]> >Datum: 03.01.2008 11:37PM >Thema: RE: 3.3RC3 > >I too am just getting back from a holiday break... I've started >doing some testing with RC3.3. I'll try to do some testing >against MS SQL and some other DB tomorrow. > >Here are some problems I've found with the source distros: > >Village-3.3-RC3-src.* distro: > >Missing the common directory so it will not compile with ant >or Maven 1.1 > >Compiles with both Ant and Maven 1.1 when this directory is >copied from the Runtime source). > >Torque-Gen-3.3-RC3-src.* distro: > >Missing the License.txt and NOTICE files in the common dir. So >it will not compile. > >Compiles with Ant and Maven 1.1 when these are added. > >Note: The Village jar has to be "installed" before Maven will >compile. But when it is released this should not be a problem. > >Also, the Ant build process failed to get various Avalon and >Maven jars from svn.apache.org (File not found errors). This >may or may not be a problem on a "clean" machine. (I suspect >it compiled with these failures because my local repository >already had the required files.) Probably not a show stopper, >but... > >> -----Original Message----- >> From: Thomas Vandahl [mailto:[EMAIL PROTECTED] >> Sent: Friday, December 28, 2007 5:33 PM >> To: Apache Torque Developers List >> Subject: Re: 3.3RC3 >> >> Ok, folks, here we go. >> >> Please check people.apache.org/~tv/torque/ for the results. >> The following has been done: >> >> - The whole Torque tree has been compiled off revision >> 607347, using JDK >> 1.4.2_16 (Apple). Maven would barf on 1.3.1. >> - Distributions have been created and signed >> - Maven-1-Jars and POMs have been created and signed (see >> directories jars, plugins, poms) >> - The site has been created (directory site) >> - The Maven-2-build has been created and signed (directory >m2-build) >> >> If nothing important is wrong with this set of artifacts I >> will call a formal vote on these later next week. SVN-tags >> will be set at this time. >> Your comments will be appreciated. >> >> 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
