[jira] Commented: (GERONIMO-4317) SQL jdbc driver class name is wrong in db pool creation wizard
[ https://issues.apache.org/jira/browse/GERONIMO-4317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633630#action_12633630 ] Forrest Xia commented on GERONIMO-4317: --- default connection url is not correct as well. the correct one should be "jdbc:sqlserver://..." not "jdbc:-microsoft-.sqlserver://..." > SQL jdbc driver class name is wrong in db pool creation wizard > -- > > Key: GERONIMO-4317 > URL: https://issues.apache.org/jira/browse/GERONIMO-4317 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: databases >Affects Versions: 2.0.2 >Reporter: Forrest Xia >Priority: Minor > > In the driver type, select SQL Server, then click next, you will see the > driver class by default > is com.microsoft.jdbc.sqlserver.SQLServerDriver. > It's not correct for sql server 2005. The correct one should be > "com.microsoft.sqlserver.jdbc.SQLServerDriver" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4317) SQL jdbc driver class name is wrong in db pool creation wizard
SQL jdbc driver class name is wrong in db pool creation wizard -- Key: GERONIMO-4317 URL: https://issues.apache.org/jira/browse/GERONIMO-4317 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: databases Affects Versions: 2.0.2 Reporter: Forrest Xia Priority: Minor In the driver type, select SQL Server, then click next, you will see the driver class by default is com.microsoft.jdbc.sqlserver.SQLServerDriver. It's not correct for sql server 2005. The correct one should be "com.microsoft.sqlserver.jdbc.SQLServerDriver" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4313) Deploy exploded web application from Console
[ https://issues.apache.org/jira/browse/GERONIMO-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633593#action_12633593 ] Ivan commented on GERONIMO-4313: It is really a very important feature, I remember most Application Server has it. To implement it, I guess there is two ways, one is writing a applet, another way is using those ajax tools like DWR . And maybe the later is better. > Deploy exploded web application from Console > > > Key: GERONIMO-4313 > URL: https://issues.apache.org/jira/browse/GERONIMO-4313 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Jürgen Weber > Attachments: fileChooser.png > > > Deploying exploded web applications from the Geronimo Console is not > possible, this has to be done with the deploy tool: ./deploy.sh deploy > --inPlace /mywebapp > Deployment of server-accessible web applications should also be possible via > the Geronimo Console. Generally, it should be possible to do everything via > the Console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4284) Server farm management based on plugins
[ https://issues.apache.org/jira/browse/GERONIMO-4284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633572#action_12633572 ] David Jencks commented on GERONIMO-4284: rev 698040 adds remove-plugin (from plugin list) and remove-plugin-list (from cluster) commands. > Server farm management based on plugins > --- > > Key: GERONIMO-4284 > URL: https://issues.apache.org/jira/browse/GERONIMO-4284 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: Clustering >Affects Versions: 2.2 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > > Our current farm support is based on (IIUC) fairly hard coded farm members > and deployment of applications with automatic distribution to farm members. > We could also use farm management based on installing plugins with more > dynamic farm membership and explicit distribution commands. For something > like this database persistence seems more appropriate than using gbeans and > repositories. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-519) Document the Deployment Plan editors
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633469#action_12633469 ] Ted Kirby commented on GERONIMODEVTOOLS-519: We're in a bit of flux regarding GEP doc. I think the doc you propose should go in pages under http://cwiki.apache.org/confluence/display/GMOxDOC22/Apache+Geronimo+Development+Tools+Project. In a separate thread, Donald has proposed giving GEP its own wiki space. We need to get our GEP doc properly tied in with GMOxDOC22. I'd like one page for each set of info, and certainly one install page, with pre-reqs. I don't think this new doc belongs in GMOxSITE. > Document the Deployment Plan editors > > > Key: GERONIMODEVTOOLS-519 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-519 > Project: Geronimo-Devtools > Issue Type: Sub-task > Components: eclipse-plugin >Affects Versions: 2.2.0 >Reporter: B.J. Reed >Assignee: B.J. Reed >Priority: Minor > Fix For: 2.2.0 > > > As the Deployment Plan Editors are completed, we need to add detailed > documentation for the use of each editor and page. It should be hooked into > the existing documentation on the > http://geronimo.apache.org/development-tools.html page. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-519) Document the Deployment Plan editors
Document the Deployment Plan editors Key: GERONIMODEVTOOLS-519 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-519 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: B.J. Reed Assignee: B.J. Reed Priority: Minor Fix For: 2.2.0 As the Deployment Plan Editors are completed, we need to add detailed documentation for the use of each editor and page. It should be hooked into the existing documentation on the http://geronimo.apache.org/development-tools.html page. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Java doc is Geronimo 2.0.1 API
Jason Dillon wrote: On Sep 22, 2008, at 11:57 PM, Joe Bohn wrote: Yep, that's pretty ancient. So it looks like we haven't released javadoc for Geronimo since the referenced link to 2.0.1. Does anybody know if the plan was to start using a maven generated site to produce provide this and we just haven't implemented it yet? AFAIK yes. There is a maven site out there for server but the content seems related to trunk and I haven't figured out how to navigate is successfully to actually get to javadoc (if any actually exists). See http://geronimo.apache.org/maven/server/ Sure there are docs there: http://geronimo.apache.org/maven/server/modules/geronimo-activation/apidocs/index.html Maven default site muck does a good job at hiding them, have to click on a module (jar module), then Project Reports and then JavaDocs. We could change the skin or add index.apt files to the modules to link to the important stuff on the main module page though. Ah, so there *is* javadoc buried in there. Thanks for pointing it out. I agree that it would be nice if we could make this more visible and perhaps aggregated at a higher level than the module level. Assuming the direction is to move toward using maven site generation - there may be some problems. The doc that I've found indicates that site generation is not support for multi module builds - which covers both Geronimo and our samples (another area that we need to address). Does anybody have any pointers/advice on generating sites for multi module builds. Is this even possible? Sure its possible, that is how the http://geronimo.apache.org/maven/server tree got up there in the first place. What docs have you found that state otherwise? I was looking at the maven site plugin docs like this one: http://maven.apache.org/plugins/maven-site-plugin/ and http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html While the second link only references generating the site for a single project I guess it really doesn't preclude multi module builds directly ... and stating that the links between modules will not work in a multi module build. I was thinking that this may explain some of the problems with generating the site for samples ... it may just be that I have some more configuration to do. Joe
[jira] Updated: (GERONIMO-4313) Deploy exploded web application from Console
[ https://issues.apache.org/jira/browse/GERONIMO-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen Weber updated GERONIMO-4313: --- Attachment: fileChooser.png Glassfish's install from local file system dialog > Deploy exploded web application from Console > > > Key: GERONIMO-4313 > URL: https://issues.apache.org/jira/browse/GERONIMO-4313 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Jürgen Weber > Attachments: fileChooser.png > > > Deploying exploded web applications from the Geronimo Console is not > possible, this has to be done with the deploy tool: ./deploy.sh deploy > --inPlace /mywebapp > Deployment of server-accessible web applications should also be possible via > the Geronimo Console. Generally, it should be possible to do everything via > the Console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4313) Deploy exploded web application from Console
[ https://issues.apache.org/jira/browse/GERONIMO-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633427#action_12633427 ] Jürgen Weber commented on GERONIMO-4313: Well, I think if one only provides a one line text input for the path, it could well go with the existing portlet. If you work with server-local folders, you usually will work in a shell where you can copy/paste the path name from. But really nice were to have a server-side file browser, this is not a small change .. I append a screenshot of the Glass-fish deploy-window. > Deploy exploded web application from Console > > > Key: GERONIMO-4313 > URL: https://issues.apache.org/jira/browse/GERONIMO-4313 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Jürgen Weber > > Deploying exploded web applications from the Geronimo Console is not > possible, this has to be done with the deploy tool: ./deploy.sh deploy > --inPlace /mywebapp > Deployment of server-accessible web applications should also be possible via > the Geronimo Console. Generally, it should be possible to do everything via > the Console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Java doc is Geronimo 2.0.1 API
On Sep 22, 2008, at 11:57 PM, Joe Bohn wrote: Yep, that's pretty ancient. So it looks like we haven't released javadoc for Geronimo since the referenced link to 2.0.1. Does anybody know if the plan was to start using a maven generated site to produce provide this and we just haven't implemented it yet? AFAIK yes. There is a maven site out there for server but the content seems related to trunk and I haven't figured out how to navigate is successfully to actually get to javadoc (if any actually exists). See http://geronimo.apache.org/maven/server/ Sure there are docs there: http://geronimo.apache.org/maven/server/modules/geronimo-activation/apidocs/index.html Maven default site muck does a good job at hiding them, have to click on a module (jar module), then Project Reports and then JavaDocs. We could change the skin or add index.apt files to the modules to link to the important stuff on the main module page though. Assuming the direction is to move toward using maven site generation - there may be some problems. The doc that I've found indicates that site generation is not support for multi module builds - which covers both Geronimo and our samples (another area that we need to address). Does anybody have any pointers/advice on generating sites for multi module builds. Is this even possible? Sure its possible, that is how the http://geronimo.apache.org/maven/server tree got up there in the first place. What docs have you found that state otherwise? --jason
[jira] Updated: (GERONIMODEVTOOLS-437) Determing success/failure of Abbot testcase from Maven
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-437: --- Assignee: Ashish Jain (was: B.J. Reed) > Determing success/failure of Abbot testcase from Maven > -- > > Key: GERONIMODEVTOOLS-437 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-437 > Project: Geronimo-Devtools > Issue Type: Sub-task >Reporter: Tim McConnell >Assignee: Ashish Jain > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4314) Console Server Information should show used port numbers
[ https://issues.apache.org/jira/browse/GERONIMO-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633409#action_12633409 ] Jürgen Weber commented on GERONIMO-4314: Yes, that's what I'm suggesting. Plus the listen address. The ports will have a different offset for each server instance in a cluster. > Console Server Information should show used port numbers > > > Key: GERONIMO-4314 > URL: https://issues.apache.org/jira/browse/GERONIMO-4314 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Jürgen Weber >Priority: Minor > > Console should list on the Server Info page the port numbers and the listen > address of this server instance, as these are important JVM resources: > "This page provides information about [..] the resources being used by the > JVM." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [BUILD] trunk: Failed for Revision: 697804
We'll see how many other problems I've created but the jetty testsuite
is now working OK for me. lets see if the automated build also
works.
sorry for the protracted breakage.
david jencks
On Sep 22, 2008, at 8:22 AM, [EMAIL PROTECTED] wrote:
Geronimo Revision: 697804 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080922/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080922
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 58 minutes 17 seconds
[INFO] Finished at: Mon Sep 22 10:00:42 EDT 2008
[INFO] Final Memory: 375M/1005M
[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/20080922/logs-0900-tomcat/test.log
[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.353
[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 32 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:05:12.662)
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:29.520)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:19.398)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:16.436)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:14.090)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE
(0:00:49.551) Java returned: 1
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:47.103)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld FAILURE
(0:00:28.994) Java returned: 1
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalFAILURE
(0:00:25.359) Java returned: 1
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime FAILURE
(0:00:33.386) Java returned: 1
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:29.742)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.296)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:29.307)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:42.002)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:47.375)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.874)
[INFO] enterprise-testsuite/sec-client RUNNING
[INFO] enterprise-testsuite/sec-client FAILURE
(0:00:14.920) Java returned: 1
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE
(0:00:25.527) Java returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:39.724)
[INFO] web-testsuite/test-2.1-jsps RUNNING
[INFO] web-testsuite/test-2.1-jsps SUCCESS (0:00:37.513)
[INFO] web-testsuite/test-2.5-servlets RUN
[jira] Commented: (GERONIMO-4302) Install the server.jar, client.jar, etc files in bin from individual no-classloader plugins, not boilerplate
[ https://issues.apache.org/jira/browse/GERONIMO-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633399#action_12633399 ] David Jencks commented on GERONIMO-4302: The above attempt really didn't work as the manifest was completely wrong. Reverted in rev 697918. > Install the server.jar, client.jar, etc files in bin from individual > no-classloader plugins, not boilerplate > > > Key: GERONIMO-4302 > URL: https://issues.apache.org/jira/browse/GERONIMO-4302 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 2.2 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > > Now that the c-m-p can easily generate no-classloader plugins we can more > easily set up a way to install the startup jars in bin. Currently they are > all stuffed into boilerplate and are present in any server whether or not > appropriate: e.g. client.jar is in all servers, even those that don't have > the rest of the client system. > The idea is to have a plugin with no classloader that unpacks the .e.g > client.jar into bin, possibly along with supporting scripts. This might > require a little enhancement of the c-m-p ArchiveMojo. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4239) car-maven-plugin dependencies configuration should enhance maven dependencies
[ https://issues.apache.org/jira/browse/GERONIMO-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633400#action_12633400 ] David Jencks commented on GERONIMO-4239: Fixed more class path problems mostly from the console in rev 697918. The testsuite now passes for me. > car-maven-plugin dependencies configuration should enhance maven dependencies > - > > Key: GERONIMO-4239 > URL: https://issues.apache.org/jira/browse/GERONIMO-4239 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: car-maven-plugin >Affects Versions: 2.2 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > > When useMavenDependencies is true, we should take any info in the c-m-p > plugin configuration dependencies section and use it to enhance the maven > dependencies with and information. This should let us > _always_ have useMavenDependencies on and result in much shorter plugin > configurations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Java doc is Geronimo 2.0.1 API
Yep, that's pretty ancient. So it looks like we haven't released javadoc for Geronimo since the referenced link to 2.0.1. Does anybody know if the plan was to start using a maven generated site to produce provide this and we just haven't implemented it yet? There is a maven site out there for server but the content seems related to trunk and I haven't figured out how to navigate is successfully to actually get to javadoc (if any actually exists). See http://geronimo.apache.org/maven/server/ Assuming the direction is to move toward using maven site generation - there may be some problems. The doc that I've found indicates that site generation is not support for multi module builds - which covers both Geronimo and our samples (another area that we need to address). Does anybody have any pointers/advice on generating sites for multi module builds. Is this even possible? Joe Ted Kirby wrote: From the home page, if I choose Javadoc as the first choice under the Development section of the left nav bar, I get 2.0.1 Javadoc. This should be updated to 2.1.3. Ted Kirby
[jira] Closed: (GERONIMO-4306) Plugin list won't be updated after installing a new server plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lin Sun closed GERONIMO-4306. - Resolution: Fixed Upon further testing, the new behavior when not caching both lists seems reasonable (maybe 1-2 seconds slow down on my macbook pro). With that I am okay with not caching them. So close this JIRA. > Plugin list won't be updated after installing a new server plugin > - > > Key: GERONIMO-4306 > URL: https://issues.apache.org/jira/browse/GERONIMO-4306 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Rex Wang > Fix For: 2.1.4, 2.2 > > Attachments: GERONIMO-4306.patch > > > Steps: > 1. Login web console > 2. Go to "Plugin -> Assemble Server" portlet, and click the button - > "Assemble a server", then get the current plugin list. > 3. Go to "Plugin -> Install Plugins" portlet to install a new plugin > 4. Go back to the "Assemble Server", and click the button, then the list is > not updated. > Proposed fix: > 1. > In "AssemblyListHandler.java", we cached the plugin list in portlet session, > and that won't be updated after installing a new plugin by web console. > If we add codes to refresh the session after installing a plugin in "Install > Plugins" portlet, it seems to solve this problem. But it does not work for > using the gsh to install new plugins. > So, we have to let the AssemblyListHandler load the plugin list each time we > open the portlet. And good news is that I did not see any significant > performance falling. > 2. > And another method to solve this problem is that "ask user to logout and > login back when they install some plugins if they want to see their plugins > list in the 'assemble Server' portlet", but is it acceptable? > If the #1 is more reasonable, I can provide a patch. > Thanks > Rex -- 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: 697804
Geronimo Revision: 697804 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080922/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080922
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 58 minutes 17 seconds
[INFO] Finished at: Mon Sep 22 10:00:42 EDT 2008
[INFO] Final Memory: 375M/1005M
[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/20080922/logs-0900-tomcat/test.log
[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.353
[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 32 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deploySUCCESS (0:05:12.662)
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:29.520)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:19.398)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:16.436)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:14.090)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:49.551) Java
returned: 1
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:47.103)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld FAILURE (0:00:28.994) Java
returned: 1
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalFAILURE (0:00:25.359) Java
returned: 1
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime FAILURE (0:00:33.386) Java
returned: 1
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:29.742)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.296)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:29.307)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:42.002)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:47.375)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.874)
[INFO] enterprise-testsuite/sec-client RUNNING
[INFO] enterprise-testsuite/sec-client FAILURE (0:00:14.920) Java
returned: 1
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests FAILURE (0:00:25.527) Java
returned: 1
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:39.724)
[INFO] web-testsuite/test-2.1-jsps RUNNING
[INFO] web-testsuite/test-2.1-jsps SUCCESS (0:00:37.513)
[INFO] web-testsuite/test-2.5-servlets RUNNING
[INFO] web-testsuite/test-2.5-servlets SUCCESS (0:00:26.312)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.527)
[INFO] web-testsuite/test-tomcatRUNNING
[INFO] web-testsuite
Re: [VOTE] Release Geronimo Eclipse Plugin 2.1.3 (RC1)
On Sep 21, 2008, at 12:22 AM, Ted Kirby wrote: I am happy to report that the vote has been approved, with 4 +1 votes, and no +0 or -1 votes. I will now undertake the appropriate actions, starting in a few hours. Thanks everyone for your support! Hi Ted, Cool. Sorry I hadn't gotten the time to review. A few minor notes: 1) A minimum of 3 PMC +1 votes are required for all release votes. This vote met that minimum requirement. Just want to remind the community... 2) When the number of votes is low, nothing wrong in extending a vote for several days to encourage additional review . In fact, I'd say it should be encouraged. We're always eager to get a new release out. However, it's important to give the community time to review these releases. Gentle (and not so gentle) reminders/nudges can usually help get people's attention... --kevan
[jira] Created: (GERONIMO-4316) Use plugin groups to construct javaee5 assemblies
Use plugin groups to construct javaee5 assemblies - Key: GERONIMO-4316 URL: https://issues.apache.org/jira/browse/GERONIMO-4316 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: buildsystem Reporter: Lin Sun Assignee: Lin Sun Per discussion on dev list, let's switch to use plugin groups to construct javaee5 assemblies, instead of individual plugins. Currently, the assemblies have both for testing purpose. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4313) Deploy exploded web application from Console
[ https://issues.apache.org/jira/browse/GERONIMO-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633256#action_12633256 ] Lin Sun commented on GERONIMO-4313: --- Ok so server-accesible web applications is the in place deployment in geronimo... I had thought you meant some other deployment method. How about provide this function when clicking on the deploy new link, either in the install new applications portlet or perhaps a new portlet? > Deploy exploded web application from Console > > > Key: GERONIMO-4313 > URL: https://issues.apache.org/jira/browse/GERONIMO-4313 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Jürgen Weber > > Deploying exploded web applications from the Geronimo Console is not > possible, this has to be done with the deploy tool: ./deploy.sh deploy > --inPlace /mywebapp > Deployment of server-accessible web applications should also be possible via > the Geronimo Console. Generally, it should be possible to do everything via > the Console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4314) Console Server Information should show used port numbers
[ https://issues.apache.org/jira/browse/GERONIMO-4314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633250#action_12633250 ] Lin Sun commented on GERONIMO-4314: --- Are you suggesting the following information in the startup console to be provided the server info portlet? 1050 127.0.0.1 CORBA Naming Service 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 2001 127.0.0.1 OpenEJB ORB Adapter 4201 0.0.0.0 OpenEJB Daemon 6882 127.0.0.1 OpenEJB ORB Adapter 8009 0.0.0.0 Tomcat Connector AJP AJP 8080 0.0.0.0 Tomcat Connector HTTP BIO HTTP 8443 0.0.0.0 Tomcat Connector HTTPS BIO HTTPS 0.0.0.0 JMX Remoting Connector 61613 0.0.0.0 ActiveMQ Transport Connector 61616 0.0.0.0 ActiveMQ Transport Connector Thanks Lin > Console Server Information should show used port numbers > > > Key: GERONIMO-4314 > URL: https://issues.apache.org/jira/browse/GERONIMO-4314 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Jürgen Weber >Priority: Minor > > Console should list on the Server Info page the port numbers and the listen > address of this server instance, as these are important JVM resources: > "This page provides information about [..] the resources being used by the > JVM." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4315) various links on the Installed Web Applications portlet lead to 404
various links on the Installed Web Applications portlet lead to 404 --- Key: GERONIMO-4315 URL: https://issues.apache.org/jira/browse/GERONIMO-4315 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.1.3 Reporter: Lin Sun Assignee: Lin Sun Priority: Minor Fix For: 2.2 Various links on the Installed Web Applications portlet lead to 404, such as /system-database, /remote-deploy, /dojo, etc. If we don't intend to allow users to access them from console, we should not provide these hyperlinks in the portlet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4314) Console Server Information should show used port numbers
Console Server Information should show used port numbers Key: GERONIMO-4314 URL: https://issues.apache.org/jira/browse/GERONIMO-4314 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: console Affects Versions: 2.1.3 Reporter: Jürgen Weber Priority: Minor Console should list on the Server Info page the port numbers and the listen address of this server instance, as these are important JVM resources: "This page provides information about [..] the resources being used by the JVM." -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4313) Deploy exploded web application from Console
[ https://issues.apache.org/jira/browse/GERONIMO-4313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633208#action_12633208 ] Jürgen Weber commented on GERONIMO-4313: server-accessible = in the file system the server is running in. Glassfish offers two options: () Packaged file to be uploaded to the server () Local packaged file or directory that is accessible from the Application Server Geronimo Console offers only the first one, the second option is subject of this bug. > Deploy exploded web application from Console > > > Key: GERONIMO-4313 > URL: https://issues.apache.org/jira/browse/GERONIMO-4313 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Jürgen Weber > > Deploying exploded web applications from the Geronimo Console is not > possible, this has to be done with the deploy tool: ./deploy.sh deploy > --inPlace /mywebapp > Deployment of server-accessible web applications should also be possible via > the Geronimo Console. Generally, it should be possible to do everything via > the Console. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Nebeans 6.1 plugin for Geronimo 2.x
Jacek Laskowski wrote: > > On Wed, Aug 27, 2008 at 9:41 PM, hat27533 <[EMAIL PROTECTED]> wrote: > >> I have managed to check out and build your nbm in netbeans 6.5 beta >> without >> a hitch. >> >> It ran my "geronimo-tomcat6-javaee5-2.1.1" based geronimo and deployed a >> noddy web app too >> >> It didnt bring the browser up though I had to nav there myself, it did >> run >> Ok. >> >> Keep up the good work Jacek, look forward to the finished module. > > Hi Neil, > > I'm glad to hear so. You're probably the sole user of the module so > far beside myself. I haven't been able to work on it for the past two > weeks, but hopefully find some spare time next week. > > Jacek > > -- > Jacek Laskowski > Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl > > Hi, Just back from a holiday, have you had any time to work on the Geronimo plugin Jacek? -- View this message in context: http://www.nabble.com/Nebeans-6.1-plugin-for-Geronimo-2.x-tp19024687s134p19604899.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[BUILD] trunk: Failed for Revision: 697688
Geronimo Revision: 697688 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080922/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080922/unit-test-reports org.apache.maven.plugins:maven-stage-plugin:maven-plugin:1.0-alpha-1 from the specified remote repositories: apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-stage-plugin:maven-plugin:1.0-alpha-1 from the specified remote repositories: apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo1.maven.org/maven2) [INFO] [INFO] Trace org.apache.maven.BuildFailureException: A required plugin was not found: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-stage-plugin -Dversion=1.0-alpha-1 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-stage-plugin -Dversion=1.0-alpha-1 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-stage-plugin:maven-plugin:1.0-alpha-1 from the specified remote repositories: apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-stage-plugin:maven-plugin:1.0-alpha-1 from the specified remote repositories: apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo1.maven.org/maven2) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:487) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-stage-plugin -Dversion=1.0-alpha-1 -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins -DartifactId=maven-stage-plugin -Dversion=1.0-alpha-1 -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.plugins:maven-stage-plugin:maven-plugin:1.0-alpha-1 from the specified remote repositories: apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo1.maven.org/maven2) org.apache.maven.plugins:maven-stage-plugin:maven-plugin:1.0-alpha-1 from the specified remote repositories: apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), ibiblio.org (http://repo1.maven.org/maven2) at
