There's a quirk with Taglib. For Taglib, you need to either: a) create a build.properties file under current/tangle that points to a local copy of tomcat
or
b) add a property to the build.properties under your user home (if you are used to doing that for other projects)
or
c) comment out the maven cactus report in current/taglib/project.xml (near the bottom)
If you choose either a or b: The entry should look like this (changed for your local of course):
cactus.home.tomcat5x = D:/cygwin/home/jmitchell/apache_home/jakarta-tomcat-5.0.28
Once you've done that successfully, you can "maven dist" any single subproject to test your local changes. The exception for this is sandbox and shale.
The reason you have to do this is because I build nightlies with maven that get uploaded along with the build log and I want the taglib tests to run as part of the nightly build. Currently there is no way for me to force cactus to create the report, but not force others to do the same without having local (not checked into svn) changes in one of the maven config files. I just don't want to do this.
Currently there is only one file that I have locally that is not in svn. That would be the shell script that I use to kick off the nightly build via a cron job. However, I do provide a copy of what I currently use called "maven-nightly.sh.current" (I know, how original ;)
Also, make sure you have the el dependencies in your local maven repository. Look in current/el/project.xml to see which ones are needed.
-- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc. 678.910.8017 AIM: jmitchtx Yahoo: jmitchtx MSN: [EMAIL PROTECTED]
----- Original Message ----- From: "Bob Arnott" <[EMAIL PROTECTED]>
To: "'Struts Developers List'" <dev@struts.apache.org>
Sent: Wednesday, March 30, 2005 4:50 AM
Subject: RE: Struts EL build broken
Niall Pemberton wrote:Bob,
It works fine for me when I run "$maven build-all" following what James outlined here...
http://www.mail-archive.com/dev@struts.apache.org/msg07192.html
I changed both ELJavascriptValidatorTag and JavascriptValidatorTag yesteday - but it looks like when you build EL its not picking up the latest version of JavascriptValidatorTag. The way the new maven build works, if you try to build el - then it downloads the dependencies (e.g. struts-core, struts-taglib) from your local maven repository, so for EL to work then it things like struts-taglib need to have been built and the repository updated - using "$maven build-all" does this. Sounds like that hasn't happended for struts-taglib in your case. What maven goal/target did you try to run?
Ah, I must admit that I'm not really a Maven user, so I don't have much of a clue about how to use it. I was just going into the master build folder and typing "maven".
Just tried it with "maven build-all" and it looked like to went fine. But there's still no EL jar file in the nightlies folder and when I run "maven" or "maven build-all" in the el folder it doesn't create a new jar file for me in the target folder.
I'm obviously doing something wrong, but I haven't a clue what.
Cheers,
-- Bob Arnott
--------------------------------------------------------------------- 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]
