Fwd: [GUMP@vmgump]: Project tomcat-taglibs-standard (in module tomcat-taglibs) failed
Sorry for cluelessness on my part, but I'm wondering what the best way
is to turn this off/fix this? Afaict the issue is because Gump is
building with a newer version of Java than that which JSTL is designed
for.
Hen
[Not on the list, so please keep me cc'd]
-- Forwarded message --
From: Gump bay...@apache.org
Date: Tue, Nov 27, 2012 at 11:56 PM
Subject: [GUMP@vmgump]: Project tomcat-taglibs-standard (in module
tomcat-taglibs) failed
To: d...@tomcat.apache.org
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project tomcat-taglibs-standard has an issue affecting its community
integration.
This issue affects 2 projects,
and has been outstanding for 210 runs.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- tomcat-taglibs-standard : Standard Taglib
- tomcat-taglibs-standard-install : JSP Taglibs
Full details are available at:
http://vmgump.apache.org/gump/public/tomcat-taglibs/tomcat-taglibs-standard/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages)
were provided:
-INFO- Optional dependency httpunit failed with reason build failed
-DEBUG- (Apache Gump generated) Apache Maven Settings in:
/srv/gump/public/workspace/tomcat-taglibs/standard/gump_mvn_settings.xml
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/tomcat-taglibs/standard/pom.xml
-INFO- Failed to extract fallback artifacts from Gump Repository
The following work was performed:
http://vmgump.apache.org/gump/public/tomcat-taglibs/tomcat-taglibs-standard/gump_work/build_tomcat-taglibs_tomcat-taglibs-standard.html
Work Name: build_tomcat-taglibs_tomcat-taglibs-standard (Type: Build)
Work ended in a state of : Failed
Elapsed: 22 secs
Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true
--settings
/srv/gump/public/workspace/tomcat-taglibs/standard/gump_mvn_settings.xml
install
[Working Directory: /srv/gump/public/workspace/tomcat-taglibs/standard]
M2_HOME: /opt/maven2
-
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[debug] execute contextualize
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/srv/gump/public/workspace/tomcat-taglibs/standard/spec/src/test/resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/srv/gump/public/workspace/tomcat-taglibs/standard/spec/target/taglibs-standard-spec-1.2-SNAPSHOT.jar
to
/srv/gump/public/workspace/mvnlocalrepo/shared/org/apache/taglibs/taglibs-standard-spec/1.2-SNAPSHOT/taglibs-standard-spec-1.2-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing
file:/srv/gump/public/workspace/mvnlocalrepo/shared/repository.xml
[INFO] Installing
org/apache/taglibs/taglibs-standard-spec/1.2-SNAPSHOT/taglibs-standard-spec-1.2-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO]
[INFO] Building JSTL Implementation
[INFO]task-segment: [install]
[INFO]
[INFO] [remote-resources:process {execution: default}]
[INFO] snapshot org.apache.taglibs:taglibs-standard-spec:1.2-SNAPSHOT:
checking for updates from apache.snapshots
[debug] execute contextualize
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 14 resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 96 source files to
/srv/gump/public/workspace/tomcat-taglibs/standard/impl/target/classes
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR]
/srv/gump/public/workspace/tomcat-taglibs/standard/impl/src/main/java/org/apache/taglibs/standard/tag/common/sql/DataSourceWrapper.java:[38,7]
error: DataSourceWrapper is not abstract and does not override
abstract method getParentLogger() in CommonDataSource
[INFO] 1 error
[INFO] -
[INFO]
[ERROR] BUILD FAILURE
[INFO]
Re: [g...@vmgump]: Project jakarta-taglibs-standard (in module jakarta-taglibs) failed
It's also interesting that the build is failing in the examples section now. I've never paid that any attention, so entirely likely there's something weird in there. I'll dig into it tomorrow night. Hen On Tue, Jan 6, 2009 at 1:26 AM, Stefan Bodewig bode...@apache.org wrote: On 2009-01-03, Henri Yandell flame...@gmail.com wrote: Repeating as I suspect the gump email got stuck in moderation. sorry, I took a few days without email over christmas and between the years and when I came back I couldn't moderate in the post because it had already expired. The same seems to have happened to the rest of the moderators (there are three of us IIRC). After Bill's changes it seems as if the build now fails to find the classes created during the build (the javax.servlet.jsp.jstl.core is supposed to be part of the standard taglib and not of anything provided by Tomcat, right?). If so, adding back the work elements should help and I'll just go ahead and do that. Once/if you switch to mvn, the work entries can be removed since they are irrelevant there. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: [g...@vmgump]: Project jakarta-taglibs-standard (in module jakarta-taglibs) failed
Repeating as I suspect the gump email got stuck in moderation. Any idea on the gump side? I'm not sure how things appear in bootclasspath and then not in classpath. There's a debug that it's decided not to include tomcat6 for the jsp21/servlet25 properties, but that doesn't seem to imply it's going to forget them all together. Hen On Tue, Dec 23, 2008 at 2:08 PM, Henri Yandell flame...@gmail.com wrote: [cc'ing gene...@gump.apache.org] Any ideas why this is failing? servlet-api and jsp-api appear in the bootclasspath debug, but then are absent from the CLASSPATH debug. Hen On Tue, Dec 23, 2008 at 3:20 AM, Martin Cooper mart...@apache.org wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project jakarta-taglibs-standard has an issue affecting its community integration. This issue affects 45 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly : Commons Jelly - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-antlr : Commons Jelly - commons-jelly-tags-avalon : Commons Jelly - commons-jelly-tags-bean : Commons Jelly - commons-jelly-tags-beanshell : Commons Jelly - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-bsf : Commons Jelly - commons-jelly-tags-define : Commons Jelly - commons-jelly-tags-define-test : Commons Jelly - commons-jelly-tags-dynabean : Commons Jelly - commons-jelly-tags-email : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-fmt-test : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-http : Commons Jelly - commons-jelly-tags-interaction : Commons Jelly - commons-jelly-tags-jaxme : Commons Jelly - commons-jelly-tags-jetty : Commons Jelly - commons-jelly-tags-jface : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-jmx : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-jsl-test : Commons Jelly - commons-jelly-tags-junit : Commons Jelly - commons-jelly-tags-log : Commons Jelly - commons-jelly-tags-memory : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-jelly-tags-regexp : Commons Jelly - commons-jelly-tags-soap : Commons Jelly - commons-jelly-tags-sql : Commons Jelly - commons-jelly-tags-swing : Commons Jelly - commons-jelly-tags-swt : Commons Jelly - commons-jelly-tags-threads : Commons Jelly - commons-jelly-tags-util : Commons Jelly - commons-jelly-tags-validate : Commons Jelly - commons-jelly-tags-velocity : Commons Jelly - commons-jelly-tags-xml : Commons Jelly - commons-jelly-tags-xml-test : Commons Jelly - commons-jelly-tags-xmlunit : Commons Jelly - commons-jelly-test : Commons Jelly - htmlunit : A tool for testing web based applications - jakarta-taglibs-standard : Standard Taglib - maven : Project Management Tools - maven-bootstrap : Project Management Tools Full details are available at: http://vmgump.apache.org/gump/public/jakarta-taglibs/jakarta-taglibs-standard/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on jaxp exists, no need to add for property jaxp-api.jar. -DEBUG- Dependency on jaxp exists, no need to add for property sax.jar. -DEBUG- Dependency on tomcat-tc6 exists, no need to add for property jsp21.jar. -DEBUG- Dependency on tomcat-tc6 exists, no need to add for property servlet25.jar. -DEBUG- Dependency on xalan exists, no need to add for property xalan.jar. -DEBUG- Dependency on xml-xerces exists, no need to add for property xercesImpl.jar. -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/jakarta-taglibs/jakarta-taglibs-standard/gump_work/build_jakarta-taglibs_jakarta-taglibs-standard.html Work Name: build_jakarta-taglibs_jakarta-taglibs-standard (Type: Build) Work ended in a state of : Failed Elapsed: 8 secs Command Line: /usr/lib/jvm/java-1.5.0-sun/bin/java -Djava.awt.headless=true -Xbootclasspath/p:/srv/gump/public/workspace/xml-xalan/build/serializer.jar:/srv/gump/public/workspace/xml-xalan/build/xalan-unbundled.jar:/srv/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/srv/gump/public/workspace/xml-xerces2/build/xercesImpl.jar:/srv/gump/packages/jaxp-1_3/dom.jar org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml
Re: [g...@vmgump]: Project jakarta-taglibs-standard (in module jakarta-taglibs) failed
Thanks Bill. Apologies for being clueless on gump. The Standard taglib isn't on mvn btw, though I am moving them all over slowly. Standard will probably be the last as it's dependent on my figuring out how to setup Cactus + Tomcat6 or Jetty for testing in mvn2. Hen On Sat, Jan 3, 2009 at 5:20 PM, Bill Barker wbar...@wilshire.com wrote: Henri Yandell flame...@gmail.com wrote in message news:31cc37360901030022r2f0f7e0dw7f06f8a6b6555...@mail.gmail.com... Repeating as I suspect the gump email got stuck in moderation. Any idea on the gump side? I'm not sure how things appear in bootclasspath and then not in classpath. There's a debug that it's decided not to include tomcat6 for the jsp21/servlet25 properties, but that doesn't seem to imply it's going to forget them all together. It's not on the bootclasspath (or on the classpath). What you are seeing is the -Dservlet25.jar=blah on the command line. If taken the liberty of commenting out the work ... / references to the produced artifacts to see if that lets gump at least build the classpath correctly. It looks like it is quitting in the middle of building it. I need to go back and see how to set up the fake MVN repository before I can actually debug the gump code. Hen On Tue, Dec 23, 2008 at 2:08 PM, Henri Yandell flame...@gmail.com wrote: [cc'ing gene...@gump.apache.org] Any ideas why this is failing? servlet-api and jsp-api appear in the bootclasspath debug, but then are absent from the CLASSPATH debug. Hen On Tue, Dec 23, 2008 at 3:20 AM, Martin Cooper mart...@apache.org wrote: To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project jakarta-taglibs-standard has an issue affecting its community integration. This issue affects 45 projects, and has been outstanding for 4 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - commons-jelly : Commons Jelly - commons-jelly-tags-ant : Commons Jelly - commons-jelly-tags-antlr : Commons Jelly - commons-jelly-tags-avalon : Commons Jelly - commons-jelly-tags-bean : Commons Jelly - commons-jelly-tags-beanshell : Commons Jelly - commons-jelly-tags-betwixt : Commons Jelly - commons-jelly-tags-bsf : Commons Jelly - commons-jelly-tags-define : Commons Jelly - commons-jelly-tags-define-test : Commons Jelly - commons-jelly-tags-dynabean : Commons Jelly - commons-jelly-tags-email : Commons Jelly - commons-jelly-tags-fmt : Commons Jelly - commons-jelly-tags-fmt-test : Commons Jelly - commons-jelly-tags-html : Commons Jelly - commons-jelly-tags-http : Commons Jelly - commons-jelly-tags-interaction : Commons Jelly - commons-jelly-tags-jaxme : Commons Jelly - commons-jelly-tags-jetty : Commons Jelly - commons-jelly-tags-jface : Commons Jelly - commons-jelly-tags-jms : Commons Jelly - commons-jelly-tags-jmx : Commons Jelly - commons-jelly-tags-jsl : Commons Jelly - commons-jelly-tags-jsl-test : Commons Jelly - commons-jelly-tags-junit : Commons Jelly - commons-jelly-tags-log : Commons Jelly - commons-jelly-tags-memory : Commons Jelly - commons-jelly-tags-quartz : Commons Jelly - commons-jelly-tags-regexp : Commons Jelly - commons-jelly-tags-soap : Commons Jelly - commons-jelly-tags-sql : Commons Jelly - commons-jelly-tags-swing : Commons Jelly - commons-jelly-tags-swt : Commons Jelly - commons-jelly-tags-threads : Commons Jelly - commons-jelly-tags-util : Commons Jelly - commons-jelly-tags-validate : Commons Jelly - commons-jelly-tags-velocity : Commons Jelly - commons-jelly-tags-xml : Commons Jelly - commons-jelly-tags-xml-test : Commons Jelly - commons-jelly-tags-xmlunit : Commons Jelly - commons-jelly-test : Commons Jelly - htmlunit : A tool for testing web based applications - jakarta-taglibs-standard : Standard Taglib - maven : Project Management Tools - maven-bootstrap : Project Management Tools Full details are available at: http://vmgump.apache.org/gump/public/jakarta-taglibs/jakarta-taglibs-standard/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Dependency on jaxp exists, no need to add for property jaxp-api.jar. -DEBUG- Dependency on jaxp exists, no need to add for property sax.jar. -DEBUG- Dependency on tomcat-tc6 exists, no need to add for property jsp21.jar. -DEBUG- Dependency on tomcat-tc6 exists, no need to add for property servlet25.jar. -DEBUG- Dependency on xalan exists, no need to add for property xalan.jar. -DEBUG- Dependency on xml-xerces exists, no need
Re: Adding external projects
Btw, added it all, now just trying to convince the friend who admins the svn server to create a new SSL cert so gump won't complain about it being out of date :) Just so you know I've not immediately gone inactive. Hen On 9/6/05, Stefan Bodewig [EMAIL PROTECTED] wrote: On Sun, 4 Sep 2005, Brett Porter [EMAIL PROTECTED] wrote: I think it's the more the merrier as long as there is someone actively looking after it. +1 Stefan - 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]
Re: jaxme
On 9/1/05, robert burrell donkin [EMAIL PROTECTED] wrote: On Thu, 2005-09-01 at 06:09 +0200, Stefan Bodewig wrote: On Tue, 30 Aug 2005, robert burrell donkin [EMAIL PROTECTED] wrote: the original plan was to try to run two gump builds until the mavenised one was debugged. however, since the original run is no longer running very well, i suppose that there may be an argument for biting the bullet and moving now. I wouldn't expect the Maven run to work any better or worse than the Ant one, so go ahead if you feel like it. The main problems we have with mavenized projects in Gump are (1) artifact-Id mismatches (2) projects depending on Maven plugins that are not (yet) installed on the Gump machines. The second point somewhat bothers me since we have a few builds that don't run just because a plugin that we wouldn't use for our builds is not installed. But that's just me disagreeing with Maven's worldview 8-) i agree that this is a little bit bothersome. i wonder whether it's not so much a problem with the worldview as a lacking feature. i don't know how to specify plugin dependencies for a maven build (so they could be automatically downloaded). without this feature, the build is not truly automatic or replicable. Same way you specify any dependencies I thought. Problem is that Gump builds in --offline mode, so it doesn't download anything. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Adding external projects
Is there any form of rule on which external projects can be added? I'd love to be using gump for osjava.org's projects (20 or so, all BSD licenced), and given that the ASF gump builds other projects, wondered if I could add an osjava.xml file. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Gump built Jars?
The Jakarta site currently links to the dead address: http://gump.covalent.net/jars/latest/ Is there a similar url of some kind for brutus.apache.org? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Commons failure reports
Just wanted to point out that we got an email for every commons project tonight. Unsure if all other projects got it. Anyway, looking forward to hearing why :) Is everything broken? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PROPOSAL] End Gump builds for sandbox projects
Okay, so you just mean no gump for sandbox [deletes long rant about importance of nightly builds]. Summary of it is, that I think gump and the apache repository need to be hooked together so each project is updating the SNAPSHOT whenever it changes. Last Lang SNAPSHOT was the end of January. +1 to kill gump builds for sandbox projects. In fact, +1 to kill it for all unreleased projects [sorry dIon/Phil/Mark]. Hen On Mon, 1 Mar 2004, Nick Chalko wrote: As long as project don't decide to use gump anyways and cheat relying on a version sandbox projects jar checked into CVS then I think this is a reasonable thing. Stephen Colebourne wrote: This is a proposal to begin to end the abuse of the sandbox. (The sandbox was intended as a temporary 'play area' for new ideas, not a long term project home) Gump is the key mechanism used in apache to ensure that everything keeps building. By removing the sandbox projects, we should encourage other projects not to depend on the sandbox unless they are willing to help push the project to a release. Normally decisions such as this have been left to each project, but IMHO its time for commons-dev to take control. Any views? Do we vote or just do it? Stephen - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
