[jira] Commented: (GERONIMO-4557) geronimo/stop-server -p 3099 can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.

2009-02-27 Thread Jason Dillon (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677271#action_12677271
 ] 

Jason Dillon commented on GERONIMO-4557:


This is not a GShell issue... its a Geronimo issue with its GShell command 
implementations.  Moved from GSHELL to GERONIMO.

In the future please do not file issues which are related to a Geronimo GShell 
command impl in the GSHELL JIRA project.

 geronimo/stop-server -p 3099 can't shutdown a server with NamingPort 
 changed to 3099 in config_substitutions.properties.
 --

 Key: GERONIMO-4557
 URL: https://issues.apache.org/jira/browse/GERONIMO-4557
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: commands
 Environment: XP + SUN JDK 1.5 + 
 geronimo-tomcat-2.1.4-snapshot_20090225
Reporter: Shawn Jiang
Assignee: Jason Dillon

 Reproduce steps:
 1, Change NamingPort=3099  in var/config-substitutions.properties.
 2, Use GShell command geronimo/start-server to start the server. 
 3, Use Use GShell command geronimo/stop-server -p 3099 to stop the server.
 Expected result: the server could be shutdown and return to the GShell 
 command line mode.
 Actually result: The server can't be shutdown, can't return to the GShell 
 command line.
 Root Cause:
 You have to use geronimo/start-server -p 3099 to start server if you want 
 use geronimo/stop-server -p 3099  to stop the server.
 I believe there should not be a -p args for geronimo/start-server command.  
 Instead, geronimo/start-server should read NamingPort=3099 in 
 config.substitutions.properties to avoid the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Assigned: (GERONIMO-4557) geronimo/stop-server -p 3099 can't shutdown a server with NamingPort changed to 3099 in config_substitutions.properties.

2009-02-27 Thread Jason Dillon (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-4557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jason Dillon reassigned GERONIMO-4557:
--

Assignee: (was: Jason Dillon)

 geronimo/stop-server -p 3099 can't shutdown a server with NamingPort 
 changed to 3099 in config_substitutions.properties.
 --

 Key: GERONIMO-4557
 URL: https://issues.apache.org/jira/browse/GERONIMO-4557
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: commands
 Environment: XP + SUN JDK 1.5 + 
 geronimo-tomcat-2.1.4-snapshot_20090225
Reporter: Shawn Jiang

 Reproduce steps:
 1, Change NamingPort=3099  in var/config-substitutions.properties.
 2, Use GShell command geronimo/start-server to start the server. 
 3, Use Use GShell command geronimo/stop-server -p 3099 to stop the server.
 Expected result: the server could be shutdown and return to the GShell 
 command line mode.
 Actually result: The server can't be shutdown, can't return to the GShell 
 command line.
 Root Cause:
 You have to use geronimo/start-server -p 3099 to start server if you want 
 use geronimo/stop-server -p 3099  to stop the server.
 I believe there should not be a -p args for geronimo/start-server command.  
 Instead, geronimo/start-server should read NamingPort=3099 in 
 config.substitutions.properties to avoid the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (GERONIMO-4554) Cant deploy an ejb web service as a plugin using car-maven-plugin

2009-02-27 Thread David Jencks (JIRA)

[ 
https://issues.apache.org/jira/browse/GERONIMO-4554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12677273#action_12677273
 ] 

David Jencks commented on GERONIMO-4554:


branches/2.1 rev 748420 implements the simplest possible (?) solution for this 
by naming both the jetty and tomcat web containers WebContainer.  Further 
simplification is possible but maybe not for 2.1.4.

For trunk we can think about actually setting up the config.xml overrides and 
substitutions although I'm not sure it's essential.

 Cant deploy an ejb web service as a plugin using car-maven-plugin
 -

 Key: GERONIMO-4554
 URL: https://issues.apache.org/jira/browse/GERONIMO-4554
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: car-maven-plugin
Affects Versions: 2.1.3
Reporter: David Jencks
Assignee: David Jencks
 Fix For: 2.1.4, 2.2


 I tried to deploy an ejb web service using the car-maven-plugin.  The cxf and 
 axis2 ejb deployers set up the wslink gbean with a reference to the web 
 container.  This is set in the plan for the deployers as WebContainer but 
 the geronimo-plugin.xml overrides this to ${webContainer}.  The jetty and 
 tomcat plugins use a config-substitutions entry to e.g. set 
 webContainer=JettyWebContainer
 So, this all works on a server where all the plugins are installed.  However 
 it doesn't work when using the car-maven-plugin since the config.xml 
 overrides and config-substitutions are not applied.
 We need to either make the config modifications work for the car-maven-plugin 
 or make sure none of the deployers the car-maven-plugin might use depend on 
 these customizations to work.  For instance, we could change all the names to 
 WebContainer. 

-- 
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: 748413

2009-02-27 Thread gawor
Geronimo Revision: 748413 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227/build-0300.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 38 minutes 41 seconds
[INFO] Finished at: Fri Feb 27 03:45:19 EST 2009
[INFO] Final Memory: 421M/963M
[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/20090227/logs-0300-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-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:44.320
[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 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:14.231) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:29.887) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:34.920) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:17.048) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:13.158) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:23.476) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.240) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:46.576) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:13.943) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:40.751) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:31.548) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.630) Java 
returned: 1
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:31.097) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:00.898) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:56.819) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:07.197) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.725) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:49.184) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:41.423) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.678) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5

[jira] Updated: (GERONIMODEVTOOLS-560) Can't Add or Remove AppClient Project via GEP

2009-02-27 Thread viola.lu (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

viola.lu updated GERONIMODEVTOOLS-560:
--

Summary: Can't Add or Remove AppClient Project via GEP  (was: Can't Add to 
Remove AppClient Project via GEP)

 Can't Add or Remove AppClient Project via GEP
 -

 Key: GERONIMODEVTOOLS-560
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-560
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.3, 2.2.0
 Environment: OS:windows 2003
 JDK:1.5
Reporter: viola.lu
Assignee: Delos Dai
 Attachments: 560_214branch.patch, 560_trunk.patch


 1.Run a fresh new eclipse in new workspace, install GEP , create geronimo 
 server runtime
 2.Create a JEE application client attached, and then right-click G server 
 runtime-add and remove project, but it indicates no project to add
 3.If i imported other war or ear, ejb jar, then add and remove project, 
 then all are listed to add and remove, if i choose app client, it will 
 reminde me that:
 The server does not support version 1.4 or 5 of the J2EE Application Client 
 module specification.
 So fail to deploy app client to server via GEP

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMODEVTOOLS-561) Can't change version in project facets

2009-02-27 Thread viola.lu (JIRA)
Can't change version in project facets
--

 Key: GERONIMODEVTOOLS-561
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-561
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.4
 Environment: OS:windows JDK 1.5
Reporter: viola.lu
Assignee: Tim McConnell
Priority: Minor


1.Create an application client in eclipse and run it on geronimo runtime
2.Right-click project properties and choose App client  version from 5 to 
1.4, but error exists:
App Client 5 can't be uninstalled.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Assigned: (GERONIMO-4517) Apply unified message display style(G-4484) to javascript alert messages. Together with the localization of these messages.

2009-02-27 Thread Gang Yin (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMO-4517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gang Yin reassigned GERONIMO-4517:
--

Assignee: Donald Woods

Hi Donald,
All needed patches are submitted, please help to review and commit them, so 
this jira could be closed, thanks.

 Apply unified message display style(G-4484) to javascript alert messages. 
 Together with the localization of these messages.
 ---

 Key: GERONIMO-4517
 URL: https://issues.apache.org/jira/browse/GERONIMO-4517
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: console
Affects Versions: 2.2
Reporter: Gang Yin
Assignee: Donald Woods
Priority: Minor
 Fix For: 2.2

 Attachments: js-localization-activemq.patch, 
 js-localization-console.patch, js-localization-core.patch, 
 js-localization-openejb.patch, js-localization-plugin.patch, 
 js-localization-sysdb.patch, screenshot-1.jpg, screenshot-2.jpg, 
 screenshot-3.jpg


 Currently all the messages generated from backend is displayed in a unified 
 manner(G-4484), but frontend javascript use alert boxes to display all kinds 
 of messages without distinguishing their types(e.g. error, warn, info), and 
 the UX of alert boxes is not so good, so I'm going to extend the unified 
 message display style of backend messages to frontend messages. Also, the 
 localization work will be done meantime.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (GERONIMO-4558) Update to latest TranQL DB2 driver

2009-02-27 Thread Kevan Miller (JIRA)
Update to latest TranQL DB2 driver
--

 Key: GERONIMO-4558
 URL: https://issues.apache.org/jira/browse/GERONIMO-4558
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
Affects Versions: 2.1.4, 2.2
Reporter: Kevan Miller
 Fix For: 2.1.4, 2.2


Matt has pushed out a new TranQL driver for DB2 XA. We should pick it up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: [NOTICE] Creating server/branches/2.1.4

2009-02-27 Thread Kevan Miller


On Feb 26, 2009, at 10:52 PM, Joe Bohn wrote:

Thanks for the heads up David.  No, I didn't start the branch yet. I  
got tied up in some other things.  Perhaps tomorrow.  Even still, we  
can still put fixes in for a few days while we wait for out  
dependencies to get released.


:D

Matt has pushed out a new TranQL driver for DB2 that I'd like to get  
in. It's currently a SNAPSHOT. Once I've confirmed it's working, can  
have Matt release it.


--kevan


[jira] Assigned: (GERONIMODEVTOOLS-561) Can't change version in project facets

2009-02-27 Thread Delos Dai (JIRA)

 [ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Delos Dai reassigned GERONIMODEVTOOLS-561:
--

Assignee: Delos Dai  (was: Tim McConnell)

 Can't change version in project facets
 --

 Key: GERONIMODEVTOOLS-561
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-561
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 2.1.4
 Environment: OS:windows JDK 1.5
Reporter: viola.lu
Assignee: Delos Dai
Priority: Minor

 1.Create an application client in eclipse and run it on geronimo runtime
 2.Right-click project properties and choose App client  version from 5 to 
 1.4, but error exists:
 App Client 5 can't be uninstalled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[BUILD] branches/2.1: Failed for Revision: 748489

2009-02-27 Thread gawor
Geronimo Revision: 748489 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227/build-0800.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 34 minutes 4 seconds
[INFO] Finished at: Fri Feb 27 08:40:27 EST 2009
[INFO] Final Memory: 318M/939M
[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/2.1/20090227/logs-0800-tomcat/test.log
 
[INFO] Running web-testsuite.tomcat
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.079 
sec  FAILURE!
 
Assembly: jetty
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227/logs-0800-jetty/test.log
 
[INFO] Running web-testsuite.jetty
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.089 
sec  FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227/samples-0800.log
 
Build status: OK
 


[BUILD] trunk: Failed for Revision: 748501

2009-02-27 Thread gawor
Geronimo Revision: 748501 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227/build-0900.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 37 minutes 6 seconds
[INFO] Finished at: Fri Feb 27 09:40:53 EST 2009
[INFO] Final Memory: 387M/1001M
[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/20090227/logs-0900-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-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:43.684
[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 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:12.192) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:30.338) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:35.510) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.486) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:14.657) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:24.432) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:47.620) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:46.301) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:00:54.228) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:39.841) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:31.212) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.579) Java 
returned: 1
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:31.419) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:59.100) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:51.055) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:10.009) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.441) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.004) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:41.234) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:29.345) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5

Re: [NOTICE] Creating server/branches/2.1.4

2009-02-27 Thread Joe Bohn

I decided to wait a little longer before creating a 2.1.4 branch.

It will probably be mid next week before all of our dependencies are 
released and we can begin the work for creating a release candidate. 
Therefore, I'm going to wait until early-mid next week to create the 
2.1.4 branch.  That will save us propagating any fixes in the interim.


Please continue to use caution when checking into branches/2.1 for now.

Thanks,
Joe


Joe Bohn wrote:
We're getting very close to a Geronimo 2.1.4 release.  I think it's 
nearly time to create a branch to prepare for the release.


So, I'm planning to create a branch on Thursday afternoon (2/26).

Please carefully consider any changes in the branches/2.1 that might 
destabilize things and consider holding off until after the branch.  I 
do anticipate that there will continue to be bug fixes and other minor 
changes.  Hopefully, we will be in a position to create a release 
candidate sometime next week.


Thanks,
Joe





[BUILD] branches/2.1: Failed for Revision: 748622

2009-02-27 Thread gawor
Geronimo Revision: 748622 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227/build-1400.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 50 seconds
[INFO] Finished at: Fri Feb 27 14:41:26 EST 2009
[INFO] Final Memory: 312M/912M
[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/2.1/20090227/logs-1400-tomcat/test.log
 
[INFO] Running web-testsuite.tomcat
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.093 
sec  FAILURE!
 
Assembly: jetty
=
See the full test.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227/logs-1400-jetty/test.log
 
[INFO] Running web-testsuite.jetty
[INFO] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.085 
sec  FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090227/samples-1400.log
 
Build status: OK
 


[BUILD] trunk: Failed for Revision: 748646

2009-02-27 Thread gawor
Geronimo Revision: 748646 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227/build-1500.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 19 seconds
[INFO] Finished at: Fri Feb 27 15:45:17 EST 2009
[INFO] Final Memory: 390M/1004M
[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/20090227/logs-1500-tomcat/test.log
 
 
[INFO] snapshot 
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking 
for updates from codehaus-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:44.860
[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 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:14.734) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:30.456) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:35.693) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:17.135) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:16.582) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:23.784) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:46.149) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:46.122) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:39.968) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:39.264) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:29.940) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.803) Java 
returned: 1
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:31.459) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:57.107) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:50.418) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:04.456) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.628) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.238) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   SUCCESS (0:00:41.649) 
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:28.505) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test

[BUILD] trunk: Failed for Revision: 748764

2009-02-27 Thread gawor
Geronimo Revision: 748764 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227/build-2100.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090227
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 7 seconds
[INFO] Finished at: Fri Feb 27 21:40:30 EST 2009
[INFO] Final Memory: 658M/965M
[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/20090227/logs-2100-tomcat/test.log
 
 
[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:39.935
[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 36 test builds
[INFO] 
[INFO] 
---
[INFO] 
[INFO] commands-testsuite/deploy  RUNNING
[INFO] commands-testsuite/deploy  SUCCESS (0:01:00.418) 
[INFO] commands-testsuite/gshell  RUNNING
[INFO] commands-testsuite/gshell  SUCCESS (0:00:28.060) 
[INFO] commands-testsuite/jaxws   RUNNING
[INFO] commands-testsuite/jaxws   SUCCESS (0:00:33.188) 
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:15.827) 
[INFO] concurrent-testsuite/concurrent-basic  RUNNING
[INFO] concurrent-testsuite/concurrent-basic  SUCCESS (0:06:24.091) 
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:19.262) 
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:43.136) 
[INFO] corba-testsuite/corba-helloworld   RUNNING
[INFO] corba-testsuite/corba-helloworld   SUCCESS (0:00:48.138) 
[INFO] corba-testsuite/corba-marshal  RUNNING
[INFO] corba-testsuite/corba-marshal  SUCCESS (0:01:03.572) 
[INFO] corba-testsuite/corba-mytime   RUNNING
[INFO] corba-testsuite/corba-mytime   SUCCESS (0:00:39.862) 
[INFO] deployment-testsuite/deployment-tests  RUNNING
[INFO] deployment-testsuite/deployment-tests  SUCCESS (0:00:30.425) 
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests FAILURE (0:00:02.422) Java 
returned: 1
[INFO] deployment-testsuite/manifestcp-tests  RUNNING
[INFO] deployment-testsuite/manifestcp-tests  SUCCESS (0:00:30.930) 
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:56.951) 
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:52.114) 
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:05.010) 
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:27.417) 
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:48.439) 
[INFO] security-testsuite/test-security   RUNNING
[INFO] security-testsuite/test-security   FAILURE (0:00:35.863) Java 
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.040) 
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:27.844) 
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web