To build Turbine you currently need maven b9, and I guess that would apply here as well. Apparently there are some fixes to the torque plugin in b9.
Eric -----Original Message----- From: Santiago Gala [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 19, 2003 4:30 PM To: Jetspeed Developers List Subject: Re: cvs commit: jakarta-jetspeed/xdocs changes.xml Mark Orciuch wrote: > Santiago, > > I already noticed/fixed issue with regexp and oro (see my latest commit). > Yes, I noticed. The cactus stuff I'm not sure it will work. > >>*and* copy the lib/uddi4j.jar and lib/stratum-1.0-b4-dev.jar to the >>maven repository like: >> >>[EMAIL PROTECTED] jakarta-jetspeed]$ cp lib/uddi4j.jar >>~/jakarta/maven-1.0-beta-8/repository/uddi4j/jars/uddi4j-1.0.jar >> > > > Yes, these do not exist in maven respository > (http://www.ibiblio.org/maven/). How do we get them there? > I fake maven by putting them in my *local* repository. I.E., I copy lib/uddi4j.jar to ~/jakarta/maven-1.0-beta-8/repository/uddi4j/jars/uddi4j-1.0.jar which is where maven looks for it. There *has* to be a better way (although for Sun files or other files maybe there isn't). > >>To get a clean build. This is because there is no uddi4j directory in >>maven's repository, neither version 1.0-b4-dev of stratum. I'm not sure >>if repeating the "cactus" id will work in an empty repository. (I had >>already the cactus files there). >> >>Also, I have not tested the build yet >> >>(...) >> >>> Index: build.xml >>> =================================================================== >>> RCS file: /home/cvs/jakarta-jetspeed/build/build.xml,v >>> retrieving revision 1.185 >>> retrieving revision 1.186 >>> diff -u -r1.185 -r1.186 >>> --- build.xml 12 Feb 2003 05:56:49 -0000 1.185 >>> +++ build.xml 18 Mar 2003 20:06:25 -0000 1.186 >>> @@ -731,15 +731,6 @@ >>> <war warfile="${build.dir}/${project.name}.war" >>> webxml="${webapp.dir}/WEB-INF/web.xml"> >>> >>> - <classes dir="${build.dest.dir}"> >>> - <!-- Do not include test files in the runtime jar --> >>> - <exclude name="**/Test*.*"/> >>> - <exclude name="**/test*.*"/> >>> - >>> - <!-- Also exclude the test cactus.properties file --> >>> - <exclude name="cactus.properties"/> >>> - </classes> >>> - >>> <lib dir="${lib.dir}"> >>> <include name="*.jar"/> >>> <exclude name="servlet*.jar"/> >>> >>> >>> >>Why was this needed? I built the jar (with ant) after the change, and it >>contains the Test classes (which are of no purpose in it). I think this >>change should be reverted. In other words, I'm -1 on this change unless >>you explain why it is needed. >> > > > I noticed that the .war file in the bin distribution contained both > jetspeed.jar and jetspeed .class files (see > http://issues.apache.org/bugzilla/show_bug.cgi?id=18121). > This is *not* doing this. What is preferred, jar or classes into the war? I'll take care of this one. I think the jar is cleaner for the war than the classes directory. > P.S. Didn't realize there was anybody else using the maven build :) The old > maven files were totally out of date. > I have been trying to patch the maven build, but today it is the first time I got it to work (after your patch). It will fail unless ant (or build.sh/bat) is used to build the torque java classes first. There is a patch and some questions in the list from mpoeschl (turbine-2 maintainer) about the issue. > Best regards, > > Mark Orciuch - [EMAIL PROTECTED] > Jakarta Jetspeed - Enterprise Portal in Java > http://jakarta.apache.org/jetspeed/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Santiago Gala High Sierra Technology, S.L. (http://hisitech.com) http://memojo.com?page=SantiagoGalaBlog --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
