[BUILD] trunk: Failed for Revision: 703767
Geronimo Revision: 703767 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012/unit-test-reports local:org.apache.cxf:cxf-common-utilities:jar:2.1.3-SNAPSHOT:compile local:org.apache.ws.commons.schema:XmlSchema:jar:1.4.2:compile local:org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1.1:compile already in car, returning:org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1.1:compile local:org.codehaus.woodstox:wstx-asl:jar:3.2.1:compile already in car, returning:org.codehaus.woodstox:wstx-asl:jar:3.2.1:compile local:org.apache.neethi:neethi:jar:2.0:compile local:org.apache.cxf:cxf-common-utilities:jar:2.1.3-SNAPSHOT:compile local:org.springframework:spring-core:jar:2.0.5:compile already in car, returning:org.springframework:spring-core:jar:2.0.5:compile local:org.springframework:spring-beans:jar:2.0.5:compile already in car, returning:org.springframework:spring-beans:jar:2.0.5:compile local:org.springframework:spring-context:jar:2.0.5:compile already in car, returning:org.springframework:spring-context:jar:2.0.5:compile local:org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1.1:compile already in car, returning:org.apache.geronimo.specs:geronimo-annotation_1.0_spec:jar:1.1.1:compile local:javax.xml.bind:jaxb-api:jar:2.1:compile already in car, returning:javax.xml.bind:jaxb-api:jar:2.1:compile local:org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1:compile already in car, returning:org.apache.geronimo.specs:geronimo-stax-api_1.0_spec:jar:1.0.1:compile local:wsdl4j:wsdl4j:jar:1.6.2:compile already in car, returning:wsdl4j:wsdl4j:jar:1.6.2:compile local:xml-resolver:xml-resolver:jar:1.2:compile local:org.apache.ws.commons.schema:XmlSchema:jar:1.4.2:compile local:org.apache.cxf:cxf-rt-bindings-soap:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-api:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-tools-common:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.1.3-SNAPSHOT:compile local:javax.xml.bind:jaxb-api:jar:2.1:compile already in car, returning:javax.xml.bind:jaxb-api:jar:2.1:compile local:org.apache.cxf:cxf-rt-bindings-xml:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-api:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-core:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-api:jar:2.1.3-SNAPSHOT:compile local:org.apache.ws.commons.schema:XmlSchema:jar:1.4.2:compile local:org.springframework:spring-core:jar:2.0.5:compile already in car, returning:org.springframework:spring-core:jar:2.0.5:compile local:org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-api:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-core:jar:2.1.3-SNAPSHOT:compile local:org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.2:compile already in car, returning:org.apache.geronimo.specs:geronimo-activation_1.1_spec:jar:1.0.2:compile local:org.codehaus.woodstox:wstx-asl:jar:3.2.1:compile already in car, returning:org.codehaus.woodstox:wstx-asl:jar:3.2.1:compile local:org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.1.3-SNAPSHOT:compile local:org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0:compile already in car, returning:org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0:compile local:asm:asm:jar:2.2.3:compile already in car, returning:asm:asm:jar:2.2.3:compile local:org.apache.cxf:cxf-api:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-core:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-bindings-soap:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-bindings-xml:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-frontend-simple:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-ws-addr:jar:2.1.3-SNAPSHOT:compile local:com.sun.xml.messaging.saaj:saaj-impl:jar:1.3:compile already in car, returning:com.sun.xml.messaging.saaj:saaj-impl:jar:1.3:compile local:com.sun.xml.parsers:jaxp-ri:jar:1.4.2:compile local:javax.xml.parsers:jaxp-api:jar:1.4.2:compile local:org.apache.cxf:cxf-rt-frontend-simple:jar:2.1.3-SNAPSHOT:compile local:org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0:compile already in car, returning:org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0:compile local:org.apache.cxf:cxf-api:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-core:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-bindings-soap:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-transports-http:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-api:jar:2.1.3-SNAPSHOT:compile local:org.apache.cxf:cxf-rt-core:jar:2.1.3-SNAPSHOT:compile
[jira] Commented: (GERONIMO-4343) Tuscany Geronimo plugin bring up
[ https://issues.apache.org/jira/browse/GERONIMO-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638836#action_12638836 ] Vamsavardhana Reddy commented on GERONIMO-4343: --- add-jms-sca-binding.diff applied in rev 703773. Tuscany Geronimo plugin bring up Key: GERONIMO-4343 URL: https://issues.apache.org/jira/browse/GERONIMO-4343 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: ant elder Attachments: add-jms-sca-binding.diff, asm.diff, GeronimoServletHost1.diff, GeronimoServletHost2.diff, tuscany-core-1.3.jar, tuscany-xsd-dependency.diff, up-to-tuscany-1.4-snapshot.diff, wsdlgen-depenency.diff JIRA to cover getting the Tuscany Geronimo Plugin working again with the latest releases of Tuscany and Geronimo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 703814
Geronimo Revision: 703814 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 37 minutes 47 seconds
[INFO] Finished at: Sun Oct 12 09:42:11 EDT 2008
[INFO] Final Memory: 380M/1013M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012/logs-0900-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-jsr88:2.2-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.framework:geronimo-deploy-jsr88:2.2-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:40.561
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 33 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:01:10.593)
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:28.627)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:19.959)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:15.871)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:13.478)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:37.782)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:43.736)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:42.874)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:53.546)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:45.098)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.559)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:38.062)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:28.779)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:44.055)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:46.570)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:53.518)
[INFO] enterprise-testsuite/sec-client RUNNING
[INFO] enterprise
[BUILD] trunk: Failed for Revision: 703902
Geronimo Revision: 703902 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 76 minutes 29 seconds
[INFO] Finished at: Sun Oct 12 22:20:14 EDT 2008
[INFO] Final Memory: 371M/1013M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012/logs-2100-tomcat/test.log
Assembly: jetty
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20081012/logs-2100-jetty/test.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: jetty
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-jetty6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty6-javaee5/2.2-SNAPSHOT/geronimo-jetty6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:42.332
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 33 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:01:08.844)
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:30.315)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:19.719)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:15.822)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:08.189)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.445)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:49.636)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:42.887)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:56.962)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:44.224)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.143)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.790)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:28.412)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:35.315)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:47.309)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:38.010)
[INFO] enterprise-testsuite/sec
Improve geronimo samples use experience
Generating standalone and deployment-ready war or ear ball will make geronimo samples more easier for first try, and will improve user's use experience. For currently generated war or ear of samples 2.1.2 release, user should supply an external deployment plan.xml to make it deployable. I think it will lead user bad use experience when first trying a simple sample war or ear ball. Of course, I believe geronimo plugin is a good stuff to try those samples, but it takes time for user to build up geronimo plugin knowledge. For an experienced JEE developer, he/she is used to consider a .ear or .war ball is a ready-to-deploy artifact. Suppose that, If they finally find they need to learn more about geronimo in order to make a simple sample's .ear or .war deployed succussfully, what feeling will they have? I think well considering user's use habit and ensuring first-try success experience is very important to attract new user to stay with our JEE server and consequently work with it. So I would suggest we add back geronimo specific deployment plan into packaged war or ear balls. What do you think of this? Forrest -- View this message in context: http://www.nabble.com/Improve-geronimo-samples-use-experience-tp19948784s134p19948784.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
Re: ASF Board Report - Initial Reminder for Oct 2008
All, I've made additional updates to our board report. Will submit to the board on Monday morning. --kevan On Oct 3, 2008, at 10:25 AM, Kevan Miller wrote: All, Our quarterly board report is due on October 13. Donald has already made some updates -- thanks Donald! Please take a look at http://cwiki.apache.org/GMOxPMGT/apache-geronimo-board-report-2008-10-october.html and update as you see fit... --kevan Begin forwarded message: From: ASF Board [EMAIL PROTECTED] Date: September 30, 2008 8:50:04 PM EDT To: Kevan Miller [EMAIL PROTECTED] Subject: ASF Board Report - Initial Reminder for Oct 2008 This email was sent by an automated system on behalf of the ASF Board. It is an initial reminder to give you plenty of time to prepare the report. The meeting is scheduled for Wed, 15 October 2008, 10 am PST and the deadline for submitting your report is two full days prior to that! According to board records, you are listed as the chair of at least one committee that is due to submit a report this month. [1] [2] Details on which project reports are due and how to submit a report are enclosed below. Please submit your report with sufficient time to allow the board members to review and digest. Again, the very latest you should submit your report is two full days (48h) prior to the board meeting. The exact date of the board meeting can be found in the calendar.txt file in the board directory of the committers repository [2]. If you feel that an error has been made, please consult [1] and if there is still an issue then contact the board directly. Thanks, The ASF Board [1] - https://svn.apache.org/repos/private/committers/board/committee-info.txt [2] - https://svn.apache.org/repos/private/committers/board/calendar.txt Submitting your Report -- Full details about the process and schedule are in [1]. Your report should be sent in plain-text format to [EMAIL PROTECTED] with a Subject line that follows the below format: Subject: [REPORT] Project Name Cutting and pasting directly from a Wiki is not acceptable due to formatting issues. Line lengths should be limited to 77 characters. The content should also be committed to the meeting agenda in the board directory in the foundation repository. ASF Board Reports - Reports are due from you for the following committees: - Geronimo
Re: Improve geronimo samples use experience
On Oct 12, 2008, at 9:47 PM, Forrest_Xia wrote: Generating standalone and deployment-ready war or ear ball will make geronimo samples more easier for first try, and will improve user's use experience. For currently generated war or ear of samples 2.1.2 release, user should supply an external deployment plan.xml to make it deployable. I think it will lead user bad use experience when first trying a simple sample war or ear ball. Of course, I believe geronimo plugin is a good stuff to try those samples, but it takes time for user to build up geronimo plugin knowledge. For an experienced JEE developer, he/she is used to consider a .ear or .war ball is a ready-to-deploy artifact. Suppose that, If they finally find they need to learn more about geronimo in order to make a simple sample's .ear or .war deployed succussfully, what feeling will they have? I think well considering user's use habit and ensuring first-try success experience is very important to attract new user to stay with our JEE server and consequently work with it. So I would suggest we add back geronimo specific deployment plan into packaged war or ear balls. What do you think of this? Well, the _only_ javaee compliant location for a plan that I know of is _outside_ the javaee artifact... see jsr88. Any time you include a plan inside a javaee artifact you are using a proprietary extension. I'm not familiar with what other container recommend, are you? Most of the samples do need a plan to indicate at least the dependency on the samples datasource. I'm not really convinced that hiding this plan inside the javaee artifact will make it clear to users that the dependency is required. I'm not completely opposed to including a plan if we can provide some automated way to make sure it is at least as functional as the related plans in the plugin subprojects. Do you have any ideas on how to assure this? Is it worth the extra effort? Another possibility might be to publish the completed plans from the plugin subprojects as additional attached artifacts with say classifier plan. That way the plans would be available through maven just as the javaee artifacts are. To me the main problem with deploying the javaee artifacts is that you have to build the plugins anyway to get the completed plan, and making the plans as available as the javaee artifacts might solve this problem. thanks david jencks Forrest -- View this message in context: http://www.nabble.com/Improve-geronimo-samples-use-experience-tp19948784s134p19948784.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
