It looks like the "last 50 lines" logic works. Furthermore, it seems quite useful. Thanks Glenn for the suggestion!
You've also seen a very recent example where a component that taglibs depends on is making an incompatible change in what they consider a private API, and how identifying this information in a timely fashion can cause the right discussion to happen well before projects get released and are discovered by end users and are more difficult to resolve. Now I'd like to float the idea of going the next step - having the taglibs developers participate more directly in this process. I'd like to suggest two specific, and relatively straightforward, tasks. The first is simply to follow up on the rhino discussion that I started. You've now got the contacts, and it will affect *YOUR* user base so don't let this drop. Secondly, take a look at the following XML and see who can first guess the one line solution to the attached problem and post it to [EMAIL PROTECTED] http://cvs.apache.org/viewcvs/~checkout~/jakarta-alexandria/proposal/gump/project/jakarta-taglibs.xml To help bootstrap this process, you can find the relevant documentation here: http://jakarta.apache.org/gump/ant.html - Sam Ruby Ted Husted <[EMAIL PROTECTED]> on 02/12/2002 09:04:46 AM Please respond to "Tag Libraries Developers List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: [GUMP] Build Failure - Taglibs ---------------------------------------------------- This email is autogenerated from the output from: <http://jakarta.apache.org/builds/gump/2002-02-12/jakarta-taglibs.html> ---------------------------------------------------- Build results exceed maximum length. Please see URL above for details. Last 50 lines of build output follows. default.post: compile-examples: examples: default.pre: [copy] Copying 1 file to /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples/WEB-INF [copy] Copying 2 files to /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples [copy] Copying 1 file to /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples/WEB-INF/lib [copy] Copying 1 file to /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples examples.html: [copy] Copying 1 file to /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples [style] DEPRECATED - the style attribute should be relative to the project's [style] basedir, not the tasks's basedir. [style] Transforming into /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples [style] Processing /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples/string.txt to /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples/string.html [style] Loading stylesheet /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples/_tmp_examples.xsl [delete] Deleting 2 files from /home/rubys/jakarta/jakarta-taglibs/build/string/string-examples default.post: examples-dist: default.pre: [jar] DEPRECATED - The jarfile attribute is deprecated. Use destfile attribute instead. [jar] Building jar: /home/rubys/jakarta/jakarta-taglibs/dist/string/string-examples.war default.post: dist: default.pre: default.post: jmstags: checkRequirements: checkRequirements.pre: checkRequiredFile: checkRequired.fail: BUILD FAILED /home/rubys/jakarta/jakarta-taglibs/jmstags/build.xml:277: a jar file containing the commons-messenger classes is required to compile the jms taglib. please define the property commons-messenger.jar in your build.properties file and ensure that the file exists Total time: 15 minutes 13 seconds -- To unsubscribe, e-mail: < mailto:[EMAIL PROTECTED]> For additional commands, e-mail: < mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
