[jira] Commented: (GERONIMO-4011) Need new release of JLine to fix GShell problems on Windows
[ https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597019#action_12597019 ] Jason Dillon commented on GERONIMO-4011: Are there other issues to be fixed other than the ones listed? Seems there is some kinda multi-line problem on windows, but I have no idea how to fix that. I can apply the duplicate prompt fix, that seems reasonable, and as mentioned the HeadlessException patch seems to be applied already, pending some digging to find out when/by who. Need new release of JLine to fix GShell problems on Windows --- Key: GERONIMO-4011 URL: https://issues.apache.org/jira/browse/GERONIMO-4011 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.1, 2.1.1, 2.1.2, 2.2 Reporter: Donald Woods Assignee: Jason Dillon Fix For: 2.1.2, 2.2 There are several GShell problems on Windows, due to JLine bugs. I'm going to try and create a patched build of JLine 0.9.94 to resolve these issues, as Geronimo packages the JLine jar into our assembly for GShell to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Google Analytics
Setup google analytics on all our spaces and added everyone who's a committer who I could easily find a gmail address for. [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You don't need a gmail address, just a google account. So if you're not in the above list, just get someone in the above list to add your google account. Just visit http://www.google.com/analytics/ to log in and view the data. It'll be a day or two before we see much of anything. -David
[BUILD] trunk: Failed for Revision: 656523
Geronimo Revision: 656523 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515/unit-test-reports org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850) org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(PackageMojo.java:500) org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(PackageMojo.java:325) org.apache.geronimo.mavenplugins.car.PackageMojo.doExecute(PackageMojo.java:227) org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:122) org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) org.apache.maven.cli.MavenCli.main(MavenCli.java:287) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) org.codehaus.classworlds.Launcher.launch(Launcher.java:255) org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] org.apache.geronimo.gbean.InvalidConfigurationException: Could not load class org.apache.geronimo.pool.ThreadPool org.apache.geronimo.management.J2EEManagedObject [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: org.apache.geronimo.gbean.InvalidConfigurationException: Could not load class org.apache.geronimo.pool.ThreadPool at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) 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.MojoExecutionException: org.apache.geronimo.gbean.InvalidConfigurationException: Could not load class org.apache.geronimo.pool.ThreadPool at org.codehaus.mojo.pluginsupport.MojoSupport.execute(MojoSupport.java:137) at org.apache.maven.plugin.DefaultPluginManager.executeMojo
[jira] Commented: (GERONIMO-4013) Make our dependency usage the same as maven dependency usage via car-maven-plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597053#action_12597053 ] David Jencks commented on GERONIMO-4013: Time will tell but I think rev 656537 fixes this issue. We now construct our own tree modeling the dependencies and remove the ones as direct dependencies that are also available from ancestor cars. The DependencyTree maven builds won't work since it eliminates lots of duplicates, typically removing the ones farther from the starting project, those often being the ones in a car file that we want to rely on. Make our dependency usage the same as maven dependency usage via car-maven-plugin - Key: GERONIMO-4013 URL: https://issues.apache.org/jira/browse/GERONIMO-4013 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Affects Versions: 2.2 Reporter: David Jencks Assignee: David Jencks Fix For: 2.2 Attachments: GERONIMO-4013.diff Right now the car-maven-plugin ignores maven transitive dependencies. One reason for this is that our build is not using our plugins as the classloader source of the maven dependencies that are in the plugin poms. If we restructured our build so that the pom dependency graph matched the geronimo classloader graph then perhaps we could let the car-maven-plugin follow transitive dependencies, thus making our view of dependencies pretty much the same as maven's. This may show up many other problems, such as too many badly scoped dependencies in all sorts of projects we use. One first step is to try out the car-maven-plugin with a flag for following transitive dependencies. As long as it is false we ought to get pretty much the previous behavior. A first use could be for the new gshell plugins so they don't have to restate all the transitive dependencies. This may show up scope problems as well. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4020) ResourceBinding doesn't actually override preprocessValue
ResourceBinding doesn't actually override preprocessValue - Key: GERONIMO-4020 URL: https://issues.apache.org/jira/browse/GERONIMO-4020 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: naming Affects Versions: 2.1.1 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.x, 2.2 Somehow the signature of ResourceBinding preprocessValue doesn't match that of the method it's trying to override, so we are binding the gbeans rather than the datasources/destinations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4014) simplify monitorying plugin structure
[ https://issues.apache.org/jira/browse/GERONIMO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597067#action_12597067 ] David Jencks commented on GERONIMO-4014: I fixed the jndi problem in GERONIMO-4020 and committed a slightly improved version of the patch in rev 656565. Could you please check whether I broke stuff? simplify monitorying plugin structure - Key: GERONIMO-4014 URL: https://issues.apache.org/jira/browse/GERONIMO-4014 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: David Jencks Fix For: 2.2 Attachments: GERONIMO-4014-2.diff, GERONIMO-4014.diff Suggestion on how to eliminate one of the apparently superfluous ears, move plan to more appropriate location. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4020) ResourceBinding doesn't actually override preprocessValue
[ https://issues.apache.org/jira/browse/GERONIMO-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597066#action_12597066 ] David Jencks commented on GERONIMO-4020: fixed trunk rev 656562. ResourceBinding doesn't actually override preprocessValue - Key: GERONIMO-4020 URL: https://issues.apache.org/jira/browse/GERONIMO-4020 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: naming Affects Versions: 2.1.1 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.x, 2.2 Somehow the signature of ResourceBinding preprocessValue doesn't match that of the method it's trying to override, so we are binding the gbeans rather than the datasources/destinations. -- 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: 656588
Geronimo Revision: 656588 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20080515/build-0800.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.1/20080515
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 31 minutes 47 seconds
[INFO] Finished at: Thu May 15 08:35:48 EDT 2008
[INFO] Final Memory: 310M/1002M
[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/20080515/logs-0800-tomcat/test.log
[INFO] [INFO]
[INFO] [INFO] Building Geronimo TestSuite :: CORBA TestSuite :: Hello World EAR
[INFO] [INFO]task-segment: [install]
[INFO] [INFO]
[INFO] [INFO] [enforcer:enforce {execution: default}]
[INFO] [INFO] [ear:generate-application-xml]
[INFO] [INFO] Generating application.xml
[INFO] [INFO] [tools:copy-legal-files {execution: install-legal-files}]
[INFO] [INFO] Created dir:
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/target/classes/META-INF
[INFO] [INFO] Copying 2 files to
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/target/classes/META-INF
[INFO] [INFO] [resources:resources]
[INFO] [INFO] Using default encoding to copy filtered resources.
[INFO] [INFO] [compiler:testCompile {execution: default}]
[INFO] [INFO] Compiling 1 source file to
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/target/test-classes
[INFO] [INFO] [surefire:test {execution: test}]
[INFO] [INFO] Tests are skipped.
[INFO] [INFO] [ear:ear]
[INFO] [INFO] Copying
artifact[war:org.apache.geronimo.testsuite:corba-helloworld-war:2.1.2-SNAPSHOT]
to[corba-helloworld-war-2.1.2-SNAPSHOT.war]
[INFO] [INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-helloworld-ejb:2.1.2-SNAPSHOT]
to[corba-helloworld-ejb-2.1.2-SNAPSHOT.jar]
[INFO] [INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-helloworld-client:2.1.2-SNAPSHOT]
to[corba-helloworld-client-2.1.2-SNAPSHOT.jar]
[INFO] [INFO] Copy ear resources to
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/target/corba-helloworld-ear-2.1.2-SNAPSHOT
[INFO] [INFO] Could not find manifest file:
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] [INFO] Building jar:
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/target/corba-helloworld-ear-2.1.2-SNAPSHOT.ear
[INFO] Downloading:
http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
[INFO] Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] Downloading:
http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
[INFO] Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[INFO] [INFO] [geronimo:start-module {execution: start-j2ee-corba-yoko}]
[INFO] [INFO] Using non-artifact based module id:
org.apache.geronimo.configs/j2ee-corba-yoko/2.1.2-SNAPSHOT/car
[WARNING] log4j:WARN No appenders could be found for logger
(org.apache.geronimo.deployment.plugin.factories.BaseDeploymentFactory).
[WARNING] log4j:WARN Please initialize the log4j system properly.
[INFO] [WARNING] Module is already started:
org.apache.geronimo.configs/j2ee-corba-yoko/2.1.2-SNAPSHOT/car
[INFO] [INFO] [geronimo:start-module {execution: openejb-corba-deployer}]
[INFO] [INFO] Using non-artifact based module id:
org.apache.geronimo.configs/openejb-corba-deployer/2.1.2-SNAPSHOT/car
[INFO] [WARNING] Module is already started:
org.apache.geronimo.configs/openejb-corba-deployer/2.1.2-SNAPSHOT/car
[INFO] [INFO] [geronimo:deploy-module {execution: deploy-ear}]
[INFO] [INFO] Using non-artifact based module archive:
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/target/corba-helloworld-ear-2.1.2-SNAPSHOT.ear
[INFO] [INFO] Distributing module artifact:
/home/geronimo/geronimo/2.1/testsuite/corba-testsuite/corba-helloworld/corba-helloworld-ear/target/corba-helloworld-ear-2.1.2
Re: ASF hosted machines for TCK testing
On May 14, 2008, at 10:32 AM, Jason Dillon wrote: On May 14, 2008, at 2:35 AM, Kevan Miller wrote: On May 13, 2008, at 1:25 PM, Jason Dillon wrote: What happened to the AMD systems which were heating up my apartment last year? 2 4x (dual core) 16g machines with nice RAID cards, etc... ? Those machines are owned by IBM. IBM would be happy to donate them to the ASF. However, they then become a potential support annoyance/ headache/migraine for Infra. IIUC, it's simpler, more manageable, etc to buy new, standard hardware and roll it into mainstream ASF infrastructure. Um... that is not what I had understood, I was under the impression that AMD donated them to the Geronimo project for TCK mucky muckski. Well, you can't donate to 'Geronimo' per se only to the ASF. I wasn't involved directly in this, but I believe the heritage for the machines is AMD - IBM. IBM people used the machines for their geronimo work (including GBuild). --kevan
[jira] Updated: (GERONIMODEVTOOLS-344) Cannot utilize the xpp3-1.1.3.4.O jar in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] B.J. Reed updated GERONIMODEVTOOLS-344: --- Attachment: GERONIMODEVTOOLS-344.patch I was unable to figure out exactly where the clash was occurring, so I went the second routeremoving the need for xstream and xpp3 from ModuleArtifactMapper. I have added an inner class that does simple parsing and writing for the moduleserver.info file. I'm sure we could use JAXB or some other solution to be more elegant, but I figure for the small amount of data that we are dealing with in that file, we can just roll our own. Also needed to change a few pom's and a manifest.mf since we no longer need the xstream and xpp3 jars so it will make the whole GEP smaller. Ted, please give this a try and see if it helps. Cannot utilize the xpp3-1.1.3.4.O jar in GEP - Key: GERONIMODEVTOOLS-344 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-344 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 2.1.0 Reporter: Tim McConnell Assignee: B.J. Reed Fix For: 2.1.1 Attachments: GERONIMODEVTOOLS-344.patch During the release of the GEP 2.1.0 we encountered problems with the xpp3-1.1.3.4.O.jar file when trying to create a new dynamic web problem (i.e., unhandled event condition). Need to investigate and understand why so that we can use the same version of this artifact that the server is using. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3864) Security warning about installation a certificate from a CA claiming to represent: Me
[ https://issues.apache.org/jira/browse/GERONIMO-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor updated GERONIMO-3864: -- Attachment: GERONIMO-3864.patch A patch for this issue that ignores Windows-MY and Windows-ROOT keystores from checking if they support storing a certificate or not (that check is causing that prompt to be displayed on Windows). Security warning about installation a certificate from a CA claiming to represent: Me - Key: GERONIMO-3864 URL: https://issues.apache.org/jira/browse/GERONIMO-3864 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1 Environment: C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:25.17 ver Microsoft Windows XP [Version 5.1.2600] C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:27.43 java -version java version 1.6.0_03 Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing) C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:30.79 echo %JAVA_HOME% c:\apps\java6 Reporter: Jacek Laskowski Attachments: GERONIMO-3864.patch, screenshot-1.jpg When you start geronimo-tomcat6-javaee5-2.1 on Windows XP with Java SE 6 you'll get a security warning about installation a certificate from a CA claiming to represent: Me. It doesn't show up with geronimo-jetty6-javaee5-2.1. See the attachment. -- 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: 656645
Geronimo Revision: 656645 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 33 minutes 27 seconds
[INFO] Finished at: Thu May 15 09:35:29 EDT 2008
[INFO] Final Memory: 352M/1007M
[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/20080515/logs-0900-tomcat/test.log
[INFO] [selenium:start-server {execution: start}]
Launching Selenium Server
Waiting for Selenium Server...
[INFO] Including display properties from:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/display.properties
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[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:36.603
[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 27 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:35.710)
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:39.563)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld FAILURE (0:00:30.091) Java
returned: 1
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:01:02.778)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime FAILURE (0:00:29.945) Java
returned: 1
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.220)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.511)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:28.181)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:36.667)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:43.731)
[INFO] enterprise-testsuite/jpa-tests
Re: ASF hosted machines for TCK testing
Jason Warner wrote: On Wed, May 14, 2008 at 10:10 AM, Joe Bohn [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Jay D. McHugh wrote: I'll volunteer to help out on supporting the machines. Thanks Jay! I'd be willing to help support the machines as well, if more people are needed, assuming you don't need to be a sysadmin superstar to do so. Excellent Jason Thanks for volunteering. I'm going to indicate that these machines would be developer maintained (unless I hear any strong objections) and as such we will need 2 developers assigned to them. Thanks, Joe I haven't been able to to much useful TCK work since my most powerful available system is a laptop that gets restarted twice a day. I saw some messages between Kevan and Matt so hopefully you have ids now (or soon will) for Matt's machines. Joe -- ~Jason Warner
Re: Testsuite updates
Maybe I don't quite understand but why can't I just cd into any testsuite directory and run mvn install from there to run all tests (including tests of sub modules if any)? Also, when I run tests with -Dtests= option, maven is installing and starting a server. That's fine when I run the tests automatically but when debugging I want maven to run tests against a running server. That's what -P child used to do for me. Is there a way to do it now? Jarek On Fri, May 9, 2008 at 8:44 AM, Jason Dillon [EMAIL PROTECTED] wrote: Folks, I've finished cleaning up some of the testsuite, a few issues that I see remain, like splitting those ear|war modules up to remove the need for extra maven configuration in modules to run the tests. Looks like there are some legitimate failures in the console-testsuite, which I've no idea how to fix ATM. The shitty-maven-plugin now runs all of the tests from the top-level testsuite module directory, using the intermediate modules only to hold common configuration. And all of the child modules use the same assembly installation as well as selenium configuration. You can still run parts of the tests, just by configuring -Dtests for the shitty plugin, as in: cd testsuite mvn -Dtests=console-testsuite/advance ^^^ which will run all of the tests for the console-testsuite/advanced testsuite module. Or cd testsuite mvn -Dtests=console-testsuite/\* ^^^ which will run all of the console-testsuite modules. Separate additional tests with a comma. A lot of duplicate configuration was dropped, the need for profiles in child modules has been removed, and IMO the whole thing has become a lot simpler and easier to grok. I may fix up the remain problems I've found soon, but I have to get some other bits finished first. Cheers, --jason
Re: Testsuite updates
Sure, you can cd into the directory you want and run mvn, just make sure you have geronimo and selenium running already. --jason On May 15, 2008, at 10:03 PM, Jarek Gawor wrote: Maybe I don't quite understand but why can't I just cd into any testsuite directory and run mvn install from there to run all tests (including tests of sub modules if any)? Also, when I run tests with -Dtests= option, maven is installing and starting a server. That's fine when I run the tests automatically but when debugging I want maven to run tests against a running server. That's what -P child used to do for me. Is there a way to do it now? Jarek On Fri, May 9, 2008 at 8:44 AM, Jason Dillon [EMAIL PROTECTED] wrote: Folks, I've finished cleaning up some of the testsuite, a few issues that I see remain, like splitting those ear|war modules up to remove the need for extra maven configuration in modules to run the tests. Looks like there are some legitimate failures in the console- testsuite, which I've no idea how to fix ATM. The shitty-maven-plugin now runs all of the tests from the top-level testsuite module directory, using the intermediate modules only to hold common configuration. And all of the child modules use the same assembly installation as well as selenium configuration. You can still run parts of the tests, just by configuring -Dtests for the shitty plugin, as in: cd testsuite mvn -Dtests=console-testsuite/advance ^^^ which will run all of the tests for the console-testsuite/ advanced testsuite module. Or cd testsuite mvn -Dtests=console-testsuite/\* ^^^ which will run all of the console-testsuite modules. Separate additional tests with a comma. A lot of duplicate configuration was dropped, the need for profiles in child modules has been removed, and IMO the whole thing has become a lot simpler and easier to grok. I may fix up the remain problems I've found soon, but I have to get some other bits finished first. Cheers, --jason
Re: ASF hosted machines for TCK testing
On May 14, 2008, at 10:32 AM, Jason Dillon wrote: On May 14, 2008, at 2:35 AM, Kevan Miller wrote: On May 13, 2008, at 1:25 PM, Jason Dillon wrote: What happened to the AMD systems which were heating up my apartment last year? 2 4x (dual core) 16g machines with nice RAID cards, etc... ? Those machines are owned by IBM. IBM would be happy to donate them to the ASF. However, they then become a potential support annoyance/ headache/migraine for Infra. IIUC, it's simpler, more manageable, etc to buy new, standard hardware and roll it into mainstream ASF infrastructure. Um... that is not what I had understood, I was under the impression that AMD donated them to the Geronimo project for TCK mucky muckski. AMD donated them to Geronimo. They are owned by the project.
Re: ASF hosted machines for TCK testing
Well, you can't donate to 'Geronimo' per se only to the ASF. I wasn't involved directly in this, but I believe the heritage for the machines is AMD - IBM. IBM people used the machines for their geronimo work (including GBuild). I worked with AMD to acquire these systems. When we got the systems from AMD they agreed to provide them for the use of the GBuild project and were never in a corporate owner's asset list. I provided AMD with the ship to address (which I think was David Blevins) so continuing to use them for the Geronimo is totally in line with what the original intention was. I think the machines would be fine except that they are now about 4- years old and had some issues that Jason struggled with so they may not be highly dependable. As far as Lights Out Management I suspect that the this means that we would likely plug them into a remote power management unit so they can be power cycled remotely and not require any manual intervention. I don't know if these machines would qualify for that kind of support. We'll need to investigate that. Is someone tracking them down and do we have a current inventory on what they are? As far as machine requirements here is my input. Given that TCK is largely single threaded a quad-core system would be fine. Running a hypervisor like XEN would make the most sense. I suggest 4GB per server instance and with a Quad core that would be 16GB. We can go lower on memory but we'll since TCK runs servers, adjunct Java processes, etc we'll grow into the extra head room. So, that said, we should acquire a Quad-Core 16GB system. I have some SuperMicro X7DB8+ motherboards (2) I can donate. I have processors as well (2.66Ghz dual core or quad core). To make these whole we'll need cases, heat sinks and memory. If we figure out that this will save us some dough I'd be happy to build the systems and prepare them to send to Infra. I've been busy with other stuff but I do have time and resources to help out here. Should I work up a list of required pieces and approximate prices to acquire and ship to the remote locations?
[jira] Commented: (GERONIMO-3947) Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1)
[ https://issues.apache.org/jira/browse/GERONIMO-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597172#action_12597172 ] Jacques Le Roux commented on GERONIMO-3947: --- Hi Donald (or anybody else aware), I need to download the Geronimo sources corresponding to WASCE 2.0.0.1. Is someone aware of where I could find them ? Thanks by advance Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1) -- Key: GERONIMO-3947 URL: https://issues.apache.org/jira/browse/GERONIMO-3947 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Environment: XP SP2, Java Sun sdk 1.5_011 Reporter: Jacques Le Roux With deployer tool, I get this error Module was not a war: framework/webtools/webapp/webtools/ With this WAR (deployed, not in a jar file) through its plan from console, I get this error Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (planFile=C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml) There is a web.xml used in OFBiz without problems (OFBiz runs with Tomcat embedded) The C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml deployment plan is web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:naming=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:security=http://geronimo.apache.org/xml/ns/security-1.2; dep:environment dep:moduleId dep:groupIdorg.ofbiz.webtools/dep:groupId dep:artifactIdwebtools/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies/ dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment context-root/webtools/context-root /web-app Am I missing something ? I thought that, since I got any problems with WASCE 2, it should work also in Geronimo. If you need more information, there is a guidelines at http://docs.ofbiz.org/x/Ah Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ASF hosted machines for TCK testing
I did a quick search on the web for what it would take to build two systems. Here is the initial SWAG. SuperMicro CSE-825S2-R700LPV U2 Rackmountable eATX Case (700W PSU, Silver) $750 x 2 = $1500 Sony DRU190A 20X DVD Rewritable Drive - 20x DVD±R $40 x 2 =80 Dynatron H53G 2U CPU Heatsink For Intel Xeon $50 x 4 = 200 Memory - 2GB DDR2 667 ECC Fully Buffered $80 x 16 = 1280 Disk - Western Digital Caviar RE2 WD7500AYYS 750GB 7200 RPM 16MB Cache SATA $200 x 4 = 800 Here is a SWAG at what we'd need to put two 8-core 16GB systems with logical mirroring 750GB storage. The cost is $3860 from the above. I'd round up to $4000 for tax, shipping, etc. We might be able to buy other systems for a lower price point. I've rounded to be conservative on cost. I would Run Linux with Xen and 4 VM's per server which would give us 8 server instances to work from. Thoughts welcome. Motherboard Information http://shopper.cnet.com/cases/supermicro-cse-825s2-r700lpv/4014-3030_9-31954268.html Heatsink Information http://www.netfreez.com/?p=catalogmode=searchsearch_in=tagssearchstr=xeon DVD Information http://www.tigerdirect.com/applications/SearchTools/item-details.asp?EdpNo=3569869CatId=482 Memory http://www.newegg.com/Product/Product.aspx?Item=N82E16820208200 Disk http://www.newegg.com/Product/Product.aspx?Item=N82E16822136144
[jira] Issue Comment Edited: (GERONIMO-3947) Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1)
[ https://issues.apache.org/jira/browse/GERONIMO-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597172#action_12597172 ] jacques.le.roux edited comment on GERONIMO-3947 at 5/15/08 9:05 AM: Hi Donald (or anybody else aware), I need to download the Geronimo sources corresponding to WASCE 2.0.0.1. Is someone aware of where I could find them ? I found https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2, could it be sufficient ? (I know the snapshot was 2.0.3) Thanks by advance was (Author: jacques.le.roux): Hi Donald (or anybody else aware), I need to download the Geronimo sources corresponding to WASCE 2.0.0.1. Is someone aware of where I could find them ? Thanks by advance Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1) -- Key: GERONIMO-3947 URL: https://issues.apache.org/jira/browse/GERONIMO-3947 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Environment: XP SP2, Java Sun sdk 1.5_011 Reporter: Jacques Le Roux With deployer tool, I get this error Module was not a war: framework/webtools/webapp/webtools/ With this WAR (deployed, not in a jar file) through its plan from console, I get this error Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (planFile=C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml) There is a web.xml used in OFBiz without problems (OFBiz runs with Tomcat embedded) The C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml deployment plan is web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:naming=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:security=http://geronimo.apache.org/xml/ns/security-1.2; dep:environment dep:moduleId dep:groupIdorg.ofbiz.webtools/dep:groupId dep:artifactIdwebtools/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies/ dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment context-root/webtools/context-root /web-app Am I missing something ? I thought that, since I got any problems with WASCE 2, it should work also in Geronimo. If you need more information, there is a guidelines at http://docs.ofbiz.org/x/Ah Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: How to stop loading of default certificate
On Tue, May 6, 2008 at 2:36 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: Hi Jarek, One reason for introducing the certKeystoreTypes is that the PKCS12 keystoreType in Sun JRE 5.0 does not allow storing of trusted certificates where as the one in IBM JRE 5.0 does allow storing of trusted certificates. Instead of letting the user figure it out, I thought it is better done before presenting a choice to the user. Irrespective of this certKeystoreTypes member, we will have to prevent these special keystore type entries from making into the supported keystore types since Windows-MY and Windows-ROOT type keystores don't behave in the same way as other keystores. I still think that we should let the user figure out which keystore to use or not but for now I decided to just ignore the Windows-MY and Windows-ROOT keystores. I attached a patch with these changes to https://issues.apache.org/jira/browse/GERONIMO-3864. If there are no objections to the patch I'll commit it tomorrow. Jarek
[jira] Assigned: (GERONIMO-3864) Security warning about installation a certificate from a CA claiming to represent: Me
[ https://issues.apache.org/jira/browse/GERONIMO-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3864: - Assignee: Jarek Gawor Security warning about installation a certificate from a CA claiming to represent: Me - Key: GERONIMO-3864 URL: https://issues.apache.org/jira/browse/GERONIMO-3864 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1 Environment: C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:25.17 ver Microsoft Windows XP [Version 5.1.2600] C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:27.43 java -version java version 1.6.0_03 Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing) C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:30.79 echo %JAVA_HOME% c:\apps\java6 Reporter: Jacek Laskowski Assignee: Jarek Gawor Attachments: GERONIMO-3864.patch, screenshot-1.jpg When you start geronimo-tomcat6-javaee5-2.1 on Windows XP with Java SE 6 you'll get a security warning about installation a certificate from a CA claiming to represent: Me. It doesn't show up with geronimo-jetty6-javaee5-2.1. See the attachment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4020) ResourceBinding doesn't actually override preprocessValue
[ https://issues.apache.org/jira/browse/GERONIMO-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597188#action_12597188 ] David Jencks commented on GERONIMO-4020: fix ported to branches/2.1 rev 656730. ResourceBinding doesn't actually override preprocessValue - Key: GERONIMO-4020 URL: https://issues.apache.org/jira/browse/GERONIMO-4020 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: naming Affects Versions: 2.1.1 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.x, 2.2 Somehow the signature of ResourceBinding preprocessValue doesn't match that of the method it's trying to override, so we are binding the gbeans rather than the datasources/destinations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-4020) ResourceBinding doesn't actually override preprocessValue
[ https://issues.apache.org/jira/browse/GERONIMO-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4020. -- Resolution: Fixed ResourceBinding.java not present in branches/2.0, so I guess its fixed. ResourceBinding doesn't actually override preprocessValue - Key: GERONIMO-4020 URL: https://issues.apache.org/jira/browse/GERONIMO-4020 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: naming Affects Versions: 2.1.1 Reporter: David Jencks Assignee: David Jencks Fix For: 2.1.x, 2.2 Somehow the signature of ResourceBinding preprocessValue doesn't match that of the method it's trying to override, so we are binding the gbeans rather than the datasources/destinations. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3947) Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1)
[ https://issues.apache.org/jira/browse/GERONIMO-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597195#action_12597195 ] Donald Woods commented on GERONIMO-3947: WASCE does not provide copies of the source code used to build it. For CE 2.0.0.1, you would need to download the Geronimo 2.0.2 tag and manually apply the patches listed in the WASCE CHANGES.txt file. So, the latest Geronimo 2.0.3-SNAPSHOT release worked for you, right? The minimal tomcat assembly can be found at the same link under its corresponding directory - http://people.apache.org/repo/m2-snapshot-repository/org/apache/geronimo/assemblies/geronimo-tomcat6-minimal/2.0.3-SNAPSHOT/ Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1) -- Key: GERONIMO-3947 URL: https://issues.apache.org/jira/browse/GERONIMO-3947 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Environment: XP SP2, Java Sun sdk 1.5_011 Reporter: Jacques Le Roux With deployer tool, I get this error Module was not a war: framework/webtools/webapp/webtools/ With this WAR (deployed, not in a jar file) through its plan from console, I get this error Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (planFile=C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml) There is a web.xml used in OFBiz without problems (OFBiz runs with Tomcat embedded) The C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml deployment plan is web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:naming=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:security=http://geronimo.apache.org/xml/ns/security-1.2; dep:environment dep:moduleId dep:groupIdorg.ofbiz.webtools/dep:groupId dep:artifactIdwebtools/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies/ dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment context-root/webtools/context-root /web-app Am I missing something ? I thought that, since I got any problems with WASCE 2, it should work also in Geronimo. If you need more information, there is a guidelines at http://docs.ofbiz.org/x/Ah Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4014) simplify monitorying plugin structure
[ https://issues.apache.org/jira/browse/GERONIMO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597196#action_12597196 ] David Jencks commented on GERONIMO-4014: Changes ported to branches/2.1 in rev 656740. simplify monitorying plugin structure - Key: GERONIMO-4014 URL: https://issues.apache.org/jira/browse/GERONIMO-4014 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: David Jencks Fix For: 2.2 Attachments: GERONIMO-4014-2.diff, GERONIMO-4014.diff Suggestion on how to eliminate one of the apparently superfluous ears, move plan to more appropriate location. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4014) simplify monitorying plugin structure
[ https://issues.apache.org/jira/browse/GERONIMO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-4014: -- Assignee: Viet Hung Nguyen Could you close this issue if you don't see any problems with the committed simplification? simplify monitorying plugin structure - Key: GERONIMO-4014 URL: https://issues.apache.org/jira/browse/GERONIMO-4014 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: David Jencks Assignee: Viet Hung Nguyen Fix For: 2.2 Attachments: GERONIMO-4014-2.diff, GERONIMO-4014.diff Suggestion on how to eliminate one of the apparently superfluous ears, move plan to more appropriate location. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release Yoko ORB subproject 1.0, RC2
+1 Joe Rick McGuire wrote: All, I've prepared a release candidate of Geronimo Yoko ORB 1.0 for your review and vote. This version has the corrected copyright dates in the NOTICES files and also corrected the missing headers in the poms. The extraneous license files and the ws sample in distribution have been deleted. These were relics of the web services binding support that was adopted by the CXF project. The source for the Yoko ORB release currently resides here: https://svn.apache.org/repos/asf/geronimo/yoko/tags/yoko-1.0 This will also be the final tag version if the release vote is approved. The maven artifacts for the release can be found here: http://people.apache.org/~rickmcguire/staging-repo/yoko There are 4 different components involved here, the core, rmi-impl, rmi-spec, and yoko-corba-spec. Each components has a jar file and also generated javadoc and source jars. For convenience, the artifacts can be located using these URLs: http://people.apache.org/~rickmcguire/staging-repo/yoko/org/apache/yoko/yoko-core/1.0/ http://people.apache.org/~rickmcguire/staging-repo/yoko/org/apache/yoko/rmi-impl/1.0/ http://people.apache.org/~rickmcguire/staging-repo/yoko/org/apache/yoko/rmi-spec/1.0/ http://people.apache.org/~rickmcguire/staging-repo/yoko/org/apache/yoko/yoko-corba-spec/1.0/ When the release vote is approved, these maven artifacts will be moved to the m2-ibiblio-rsync-repository at Apache. [ ] +1 Release Yoko 1.0 [ ] 0 No opinion [ ] -1 Do not release Yoko 1.0 (please provide rationale) I'll plan on calling this vote on Thursday afternoon (4 PM EST). Rick
Re: ASF hosted machines for TCK testing
On May 15, 2008, at 11:22 AM, Matt Hogstrom wrote: On May 14, 2008, at 10:32 AM, Jason Dillon wrote: On May 14, 2008, at 2:35 AM, Kevan Miller wrote: On May 13, 2008, at 1:25 PM, Jason Dillon wrote: What happened to the AMD systems which were heating up my apartment last year? 2 4x (dual core) 16g machines with nice RAID cards, etc... ? Those machines are owned by IBM. IBM would be happy to donate them to the ASF. However, they then become a potential support annoyance/headache/migraine for Infra. IIUC, it's simpler, more manageable, etc to buy new, standard hardware and roll it into mainstream ASF infrastructure. Um... that is not what I had understood, I was under the impression that AMD donated them to the Geronimo project for TCK mucky muckski. AMD donated them to Geronimo. They are owned by the project. They could have been donated for use by Geronimo or GBuild. However, they can't be owned by Geronimo. The Geronimo project can't own anything... The ASF can own things, but not individual projects. I have no problems with someone/something donating the machines to the ASF. However, I doubt they want them. They would become an admin liability for ASF Infra. --kevan
Re: ASF hosted machines for TCK testing
On May 15, 2008, at 11:31 AM, Matt Hogstrom wrote: Well, you can't donate to 'Geronimo' per se only to the ASF. I wasn't involved directly in this, but I believe the heritage for the machines is AMD - IBM. IBM people used the machines for their geronimo work (including GBuild). I worked with AMD to acquire these systems. When we got the systems from AMD they agreed to provide them for the use of the GBuild project and were never in a corporate owner's asset list. I provided AMD with the ship to address (which I think was David Blevins) so continuing to use them for the Geronimo is totally in line with what the original intention was. I think the machines would be fine except that they are now about 4- years old and had some issues that Jason struggled with so they may not be highly dependable. As far as Lights Out Management I suspect that the this means that we would likely plug them into a remote power management unit so they can be power cycled remotely and not require any manual intervention. I don't know if these machines would qualify for that kind of support. We'll need to investigate that. Is someone tracking them down and do we have a current inventory on what they are? As far as machine requirements here is my input. Given that TCK is largely single threaded a quad-core system would be fine. Running a hypervisor like XEN would make the most sense. I suggest 4GB per server instance and with a Quad core that would be 16GB. We can go lower on memory but we'll since TCK runs servers, adjunct Java processes, etc we'll grow into the extra head room. So, that said, we should acquire a Quad-Core 16GB system. I have some SuperMicro X7DB8+ motherboards (2) I can donate. I have processors as well (2.66Ghz dual core or quad core). To make these whole we'll need cases, heat sinks and memory. If we figure out that this will save us some dough I'd be happy to build the systems and prepare them to send to Infra. I've been busy with other stuff but I do have time and resources to help out here. Should I work up a list of required pieces and approximate prices to acquire and ship to the remote locations? Yes, I'm certainly assuming (hoping) that we'll be able to run multiple images on a single box. We should check to see what sort of heap sizes we're allocating to the JVM processes during our TCK runs. To help with calculating guidelines for memory per core. We also need to discuss with ASF Infra specifics about running XEN (or similar) hypervisor. We need to be aware of any concerns they might have... --kevan
[jira] Updated: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen updated GERONIMO-3996: --- Component/s: monitoring Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3947) Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1)
[ https://issues.apache.org/jira/browse/GERONIMO-3947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597205#action_12597205 ] Jacques Le Roux commented on GERONIMO-3947: --- Thanks for your fast reply Donald, Yes Geronimo 2.0.3-SNAPSHOT release worked fine. I will give it a go tomorrow, and will let you know of course. Apache OFBiz deploys and runs under WASCE 2 but not under Geronimo 2.0.1 (nor 2.1) -- Key: GERONIMO-3947 URL: https://issues.apache.org/jira/browse/GERONIMO-3947 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.0.1 Environment: XP SP2, Java Sun sdk 1.5_011 Reporter: Jacques Le Roux With deployer tool, I get this error Module was not a war: framework/webtools/webapp/webtools/ With this WAR (deployed, not in a jar file) through its plan from console, I get this error Cannot deploy the requested application module because no deployer is able to handle it. This can happen if you have omitted the J2EE deployment descriptor, disabled a deployer module, or if, for example, you are trying to deploy an EJB module on a minimal Geronimo server that does not have EJB support installed. (planFile=C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml) There is a web.xml used in OFBiz without problems (OFBiz runs with Tomcat embedded) The C:\Program Files\Apache Software Foundation\geronimo-tomcat6-jee5-2.0.1\var\temp\geronimo-web.xml deployment plan is web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:naming=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:security=http://geronimo.apache.org/xml/ns/security-1.2; dep:environment dep:moduleId dep:groupIdorg.ofbiz.webtools/dep:groupId dep:artifactIdwebtools/dep:artifactId dep:version1.0/dep:version dep:typewar/dep:type /dep:moduleId dep:dependencies/ dep:hidden-classes/ dep:non-overridable-classes/ /dep:environment context-root/webtools/context-root /web-app Am I missing something ? I thought that, since I got any problems with WASCE 2, it should work also in Geronimo. If you need more information, there is a guidelines at http://docs.ofbiz.org/x/Ah Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ASF hosted machines for TCK testing
On May 15, 2008, at 12:04 PM, Matt Hogstrom wrote: I did a quick search on the web for what it would take to build two systems. Here is the initial SWAG. SuperMicro CSE-825S2-R700LPV U2 Rackmountable eATX Case (700W PSU, Silver) $750 x 2 = $1500 Sony DRU190A 20X DVD Rewritable Drive - 20x DVD±R $40 x 2 =80 Dynatron H53G 2U CPU Heatsink For Intel Xeon $50 x 4 = 200 Memory - 2GB DDR2 667 ECC Fully Buffered $80 x 16 = 1280 Disk - Western Digital Caviar RE2 WD7500AYYS 750GB 7200 RPM 16MB Cache SATA $200 x 4 = 800 Here is a SWAG at what we'd need to put two 8-core 16GB systems with logical mirroring 750GB storage. The cost is $3860 from the above. I'd round up to $4000 for tax, shipping, etc. We might be able to buy other systems for a lower price point. I've rounded to be conservative on cost. I would Run Linux with Xen and 4 VM's per server which would give us 8 server instances to work from. Cool. As long as Infra can pick them up and manage them, that's great. In the past, we've always run into hardware/management issues in the colo's that we've run the machines in. IMO, the more standard we are the more likely that Infra will be able to administer/repair these machines. Fewer headaches all the way around. --kevan
[jira] Closed: (GERONIMO-4014) simplify monitorying plugin structure
[ https://issues.apache.org/jira/browse/GERONIMO-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen closed GERONIMO-4014. -- Resolution: Fixed Thanks David. Everything looks fine. simplify monitorying plugin structure - Key: GERONIMO-4014 URL: https://issues.apache.org/jira/browse/GERONIMO-4014 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: David Jencks Assignee: Viet Hung Nguyen Fix For: 2.2 Attachments: GERONIMO-4014-2.diff, GERONIMO-4014.diff Suggestion on how to eliminate one of the apparently superfluous ears, move plan to more appropriate location. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-346) Adding security roles in the Geronimo Deployment Plan Editor does not work
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-346: --- Fix Version/s: 2.1.1 Assignee: B.J. Reed (was: Tim McConnell) Adding security roles in the Geronimo Deployment Plan Editor does not work -- Key: GERONIMODEVTOOLS-346 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-346 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Environment: Eclipse Europa Winter (WTP 2.0.2), Windows XP SP2, Geronimo 2.1.1, GEP 2.1.0, Reporter: Cedric Hurst Assignee: B.J. Reed Fix For: 2.1.1 Original Estimate: 0h Remaining Estimate: 0h Steps to reproduce === 1. Create a new Enterprise Application Project 2. Open the geronimo-application.xml file in the graphical editor 3. Select the security tab 4. Click the add button in the Security Roles section 5. Provide any value for name and/or description and click Finish Expected behavior === New role will show up in the Security Role list and in the source view of geronimo-application.xml Actual behavior === Role does not show up, nor is it added the the actual xml file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-339) Provide tooling application client interface (instead of current command line interface)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-339: --- Fix Version/s: (was: 2.1.x) 2.1.1 Assignee: B.J. Reed (was: Tim McConnell) Provide tooling application client interface (instead of current command line interface) Key: GERONIMODEVTOOLS-339 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-339 Project: Geronimo-Devtools Issue Type: New Feature Components: eclipse-plugin Reporter: Tim McConnell Assignee: B.J. Reed Priority: Minor Fix For: 2.1.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Webapp-based Tuscany/Geronimo integration in Tuscany SCA Java 1.2 release
Hi, In the recently released Tuscany SCA Java 1.2 [1], we produce a whitepaper [2] to describe webapp-based Tuscany/Geronimo integration. We would like to share the information here and hope it can trigger more interests from both Geronimo and Tuscany community to bring more values into these areas collaboratively. Developing SOA based solutions can be very complex and expensive. Apache Tuscany provides a lightweight infrastructure which enables users to easily implement SOA based solutions or to use their existing assets and align them with SOA principles which would support a business model that can extend and expand as business needs change. Apache Tuscany implements SCA specifications that is being standardized at OASIS. Tuscany provides the capabilities to construct, assemble and deploy composite applications using SCA. This white paper explains how Tuscany integrates with Apache Geronimo, a fully certified Java EE 5 application server runtime, to provide added value to users wanting to develop SOA solutions using Geronimo as a platform. The added values include: * Extensibility of component implementation technologies * Extensibility of transport and protocol abstractions * A notion of cross-application/cross-network assembly and configuration * Integration of SCA with existing or new EJB based applications The following are a set of usage scenarios that both JEE and SCA developers could be interested in. * Access SCA composites from Java EE components using JEE programming model * Access session beans from SCA service components * Expose SCA services as session beans or web services * Include Session Beans in a single SCA composition by providing an SCA implementation for session beans. * Inject SCA service references to web components to enable Web 2.0 * Expose enterprise applications into an SCA domain * Use recursive SCA assembly in enterprise applications [1] http://incubator.apache.org/tuscany/sca-java-releases.html [2] http://cwiki.apache.org/TUSCANYWIKI/tuscany-web-application-based-integration-with-geronimo.html Thanks, Raymond
[jira] Updated: (GERONIMO-3864) Security warning about installation a certificate from a CA claiming to represent: Me
[ https://issues.apache.org/jira/browse/GERONIMO-3864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy updated GERONIMO-3864: -- Attachment: GERONIMO-3864-new.patch GERONIMO-3864.patch seems to have some formatting changes too. Please use GERONIMO-3864-new.patch instead. Security warning about installation a certificate from a CA claiming to represent: Me - Key: GERONIMO-3864 URL: https://issues.apache.org/jira/browse/GERONIMO-3864 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1 Environment: C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:25.17 ver Microsoft Windows XP [Version 5.1.2600] C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:27.43 java -version java version 1.6.0_03 Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing) C:\geronimo-tomcat6-javaee5-2.1 Mon 02/18/2008 23:53:30.79 echo %JAVA_HOME% c:\apps\java6 Reporter: Jacek Laskowski Assignee: Jarek Gawor Attachments: GERONIMO-3864-new.patch, GERONIMO-3864.patch, screenshot-1.jpg When you start geronimo-tomcat6-javaee5-2.1 on Windows XP with Java SE 6 you'll get a security warning about installation a certificate from a CA claiming to represent: Me. It doesn't show up with geronimo-jetty6-javaee5-2.1. See the attachment. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4011) Need new release of JLine to fix GShell problems on Windows
[
https://issues.apache.org/jira/browse/GERONIMO-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Dillon updated GERONIMO-4011:
---
Attachment: jline-0.9.95-SNAPSHOT.jar
See if the attached {{jline-0.9.95-SNAPSHOT.jar}} resolves the 2 problems noted
in the issue on Windows.
Need new release of JLine to fix GShell problems on Windows
---
Key: GERONIMO-4011
URL: https://issues.apache.org/jira/browse/GERONIMO-4011
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: dependencies
Affects Versions: 2.1, 2.1.1, 2.1.2, 2.2
Reporter: Donald Woods
Assignee: Jason Dillon
Fix For: 2.1.2, 2.2
Attachments: jline-0.9.95-SNAPSHOT.jar
There are several GShell problems on Windows, due to JLine bugs.
I'm going to try and create a patched build of JLine 0.9.94 to resolve these
issues, as Geronimo packages the JLine jar into our assembly for GShell to
use.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: svn commit: r656788 - /geronimo/server/trunk/pom.xml
Jason,
Can you explain why?
Jarek
On Thu, May 15, 2008 at 2:46 PM, [EMAIL PROTECTED] wrote:
Author: jdillon
Date: Thu May 15 11:46:43 2008
New Revision: 656788
URL: http://svn.apache.org/viewvc?rev=656788view=rev
Log:
STOP using properties to define versions for dependencies
Modified:
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=656788r1=656787r2=656788view=diff
==
--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Thu May 15 11:46:43 2008
@@ -67,8 +67,10 @@
geronimoSchemaVersion1.2/geronimoSchemaVersion
!--
-Having a single well named version properties makes automatic
updating for the weekly build much easier.
+FIXME: STOP using properties for dependency versions unless you
absolutly need them,
+ ie. you have a hundred dependencies that all use the same
version.
--
+
openejbVersion3.1-SNAPSHOT/openejbVersion
yokoVersion1.0-SNAPSHOT/yokoVersion
derbyVersion10.2.2.0/derbyVersion
@@ -83,10 +85,6 @@
plutoVersion1.1.6-G643117/plutoVersion
openjpaVersion1.0.2/openjpaVersion
xbeanVersion3.3/xbeanVersion
-gmavenVersion1.0-rc-1/gmavenVersion
-minaVersion1.1.6/minaVersion
-slf4jVersion1.5.0/slf4jVersion
-groovyVersion1.5.6/groovyVersion
wadiVersion2.0-SNAPSHOT/wadiVersion
!-- Deployers --
@@ -484,25 +482,25 @@
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-api/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-simple/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-log4j12/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdjcl104-over-slf4j/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
@@ -1378,25 +1376,25 @@
dependency
groupIdorg.codehaus.groovy.maven/groupId
artifactIdgmaven-mojo/artifactId
-version${gmavenVersion}/version
+version1.0-rc-1/version
/dependency
dependency
groupIdorg.codehaus.groovy.maven.runtime/groupId
artifactIdgmaven-runtime-default/artifactId
-version${gmavenVersion}/version
+version1.0-rc-1/version
/dependency
dependency
groupIdorg.codehaus.groovy.maven.support/groupId
artifactIdslf4j-gossip/artifactId
-version${gmavenVersion}/version
+version1.0-rc-1/version
/dependency
dependency
groupIdorg.codehaus.groovy/groupId
artifactIdgroovy-all-minimal/artifactId
-version${groovyVersion}/version
+version1.5.6/version
/dependency
dependency
@@ -1481,13 +1479,13 @@
dependency
groupIdorg.apache.mina/groupId
artifactIdmina-core/artifactId
-version${minaVersion}/version
+version1.1.6/version
/dependency
dependency
groupIdorg.apache.mina/groupId
artifactIdmina-filter-ssl/artifactId
-version${minaVersion}/version
+version1.1.6/version
/dependency
!-- Admin Console support --
[jira] Assigned: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig reassigned GERONIMO-3996: --- Assignee: Erik B. Craig Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Erik B. Craig Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r656788 - /geronimo/server/trunk/pom.xml
Disagree, as using properties makes it easier to read and maintain the
versions, especially when the TCK relies on the server pom for versions
and if you create samples or plugins that want to rely on the same
versions as the server
But whatever, as this seems to be a personal preference based on your
love or hate of Maven. :-)
-Donald
[EMAIL PROTECTED] wrote:
Author: jdillon
Date: Thu May 15 11:46:43 2008
New Revision: 656788
URL: http://svn.apache.org/viewvc?rev=656788view=rev
Log:
STOP using properties to define versions for dependencies
Modified:
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=656788r1=656787r2=656788view=diff
==
--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Thu May 15 11:46:43 2008
@@ -67,8 +67,10 @@
geronimoSchemaVersion1.2/geronimoSchemaVersion
!--
-Having a single well named version properties makes automatic updating
for the weekly build much easier.
+FIXME: STOP using properties for dependency versions unless you
absolutly need them,
+ ie. you have a hundred dependencies that all use the same
version.
--
+
openejbVersion3.1-SNAPSHOT/openejbVersion
yokoVersion1.0-SNAPSHOT/yokoVersion
derbyVersion10.2.2.0/derbyVersion
@@ -83,10 +85,6 @@
plutoVersion1.1.6-G643117/plutoVersion
openjpaVersion1.0.2/openjpaVersion
xbeanVersion3.3/xbeanVersion
-gmavenVersion1.0-rc-1/gmavenVersion
-minaVersion1.1.6/minaVersion
-slf4jVersion1.5.0/slf4jVersion
-groovyVersion1.5.6/groovyVersion
wadiVersion2.0-SNAPSHOT/wadiVersion
!-- Deployers --
@@ -484,25 +482,25 @@
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-api/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-simple/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-log4j12/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdjcl104-over-slf4j/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
@@ -1378,25 +1376,25 @@
dependency
groupIdorg.codehaus.groovy.maven/groupId
artifactIdgmaven-mojo/artifactId
-version${gmavenVersion}/version
+version1.0-rc-1/version
/dependency
dependency
groupIdorg.codehaus.groovy.maven.runtime/groupId
artifactIdgmaven-runtime-default/artifactId
-version${gmavenVersion}/version
+version1.0-rc-1/version
/dependency
dependency
groupIdorg.codehaus.groovy.maven.support/groupId
artifactIdslf4j-gossip/artifactId
-version${gmavenVersion}/version
+version1.0-rc-1/version
/dependency
dependency
groupIdorg.codehaus.groovy/groupId
artifactIdgroovy-all-minimal/artifactId
-version${groovyVersion}/version
+version1.5.6/version
/dependency
dependency
@@ -1481,13 +1479,13 @@
dependency
groupIdorg.apache.mina/groupId
artifactIdmina-core/artifactId
-version${minaVersion}/version
+version1.1.6/version
/dependency
dependency
groupIdorg.apache.mina/groupId
artifactIdmina-filter-ssl/artifactId
-version${minaVersion}/version
+version1.1.6/version
/dependency
!-- Admin Console support --
smime.p7s
Description: S/MIME Cryptographic Signature
[BUILD] trunk: Failed for Revision: 656794
Geronimo Revision: 656794 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515/unit-test-reports
[INFO] [car:package]
[INFO] Packaging module configuration:
/home/geronimo/geronimo/trunk/plugins/cxf/cxf-ejb-deployer/target/resources/META-INF/plan.xml
[INFO] Started deployer:
org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car
[INFO] snapshot org.apache.geronimo.configs:cxf-deployer:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.configs:cxf-deployer:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.configs:cxf-deployer:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] snapshot org.apache.geronimo.configs:cxf-ejb:2.2-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot org.apache.geronimo.configs:cxf-ejb:2.2-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot org.apache.geronimo.configs:cxf-ejb:2.2-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-cxf-ejb-builder:2.2-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-cxf-ejb-builder:2.2-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.modules:geronimo-cxf-ejb-builder:2.2-SNAPSHOT: checking for
updates from apache.snapshots
[INFO] [car:prepare-metadata]
[INFO] [car:archive-car]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/plugins/cxf/cxf-ejb-deployer/target/cxf-ejb-deployer-2.2-SNAPSHOT.car
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: cxf-ejb-deployer-2.2-SNAPSHOT.car
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/cxf/cxf-ejb-deployer/target/cxf-ejb-deployer-2.2-SNAPSHOT.car
to
/home/geronimo/.m2/repository/org/apache/geronimo/configs/cxf-ejb-deployer/2.2-SNAPSHOT/cxf-ejb-deployer-2.2-SNAPSHOT.car
[INFO] [car:update-pluginlist]
[INFO]
[INFO] Building Geronimo Plugins, Dojo
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [site:attach-descriptor]
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] [install:install]
[INFO] Installing /home/geronimo/geronimo/trunk/plugins/dojo/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/plugins/dojo/2.2-SNAPSHOT/dojo-2.2-SNAPSHOT.pom
[INFO]
[INFO] Building Geronimo Plugins, Dojo :: WAR
[INFO]task-segment: [install]
[INFO]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact: org.dojotoolkit:dojo:1.1.0:tgz
[INFO] Unpacking
/home/geronimo/.m2/repository/org/dojotoolkit/dojo/1.1.0/dojo-1.1.0.tgzto
/home/geronimo/geronimo/trunk/plugins/dojo/geronimo-dojo/target
with Includes null and excludes:null
[INFO] Expanding
/home/geronimo/.m2/repository/org/dojotoolkit/dojo/1.1.0/dojo-1.1.0.tgz to
/tmp/tmp36123.tar
[INFO] Expanding: /tmp/tmp36123.tar into
/home/geronimo/geronimo/trunk/plugins/dojo/geronimo-dojo/target
[WARNING] ---
[WARNING] Standard error:
[WARNING] ---
[WARNING]
[WARNING] ---
[WARNING] Standard output:
[WARNING] ---
[WARNING] /bin/sh: line 0: cd:
/home/geronimo/geronimo/trunk/plugins/dojo/geronimo-dojo/target/dojo-release-1.1.0/dojox/data/demos/geography/Commonwealth:
No such file or directory
[WARNING] ---
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error unpacking file:
/home/geronimo/.m2/repository/org/dojotoolkit/dojo/1.1.0/dojo-1.1.0.tgz to:
/home/geronimo/geronimo/trunk/plugins/dojo/geronimo-dojo/target
org.codehaus.plexus.archiver.ArchiverException: chmod exit code was: 1
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error unpacking file:
/home/geronimo/.m2/repository/org/dojotoolkit/dojo/1.1.0/dojo-1.1.0.tgz to:
/home/geronimo/geronimo/trunk/plugins/dojo/geronimo-dojo/target
org.codehaus.plexus.archiver.ArchiverException: chmod exit code was: 1
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals
Re: Update Derby to 10.3.2.1
The issue ended up being completely unrelated to derby, so I'm going to leave the version in the server alone. I'll look at upgrading derby to 10.4.1.3 later as it incorporates a fix for the issue that prevented the upgrade to 10.3.2.1 a while ago. I'll make a new thread before I actually make the update, though, whenever it is that I get around to that. On Wed, May 14, 2008 at 1:25 PM, Jason Warner [EMAIL PROTECTED] wrote: Thanks, Jarek. I had actually stumbled onto that already and just haven't updated my post. I tried upgrading to 10.4.1.3, but that didn't solve the problem that 10.3.2.1 seemed to solve. I'm working on trying to understand the problem better so I can fix it somehow. On Wed, May 14, 2008 at 1:13 PM, Jarek Gawor [EMAIL PROTECTED] wrote: Please run the little sql shown in my comment on https://issues.apache.org/jira/browse/GERONIMO-3545 to verify the problem is fixed in 10.3.2.1. From https://issues.apache.org/jira/browse/DERBY-3094 it looks like the problem was fixed in 10.3.2.2 and 10.4.1.3 so 10.3.2.1 might not work. Jarek On Tue, May 13, 2008 at 3:53 PM, Jason Warner [EMAIL PROTECTED] wrote: I'd like to update our derby version to 10.3.2.1 in branches/2.1 and trunk. This is directly related to the update of tomcat and resolves some TCK issues introduced by the tomcat update. This is all assuming TCK remains happy. -- ~Jason Warner -- ~Jason Warner -- ~Jason Warner
[jira] Updated: (GERONIMODEVTOOLS-348) JSF Tags Not Displayed in Eclipse Web Page Editor
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cedric Hurst updated GERONIMODEVTOOLS-348: -- Attachment: jsf palettes visible.jpg JSF Tags Not Displayed in Eclipse Web Page Editor - Key: GERONIMODEVTOOLS-348 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Environment: Windows XP SP2, Eclipse Europa Winter Maintenance Release, Geronimo 2.1.1, GEP 2.1.0 Reporter: Cedric Hurst Assignee: Tim McConnell Attachments: jsf palettes visible.jpg Eclipse WTP tooling provides a drag-and-drop palette for various taglibs in its Web Page Editor. When the JSF Project Facet is attached to a Dynamic Web Project, JSF Core and JSF HTML taglibs should be added to the palette (see screenshot). However, this is not the case when using Geronimo/GEP. Steps to Reproduce === 1. Create a new Dynamic Web Project using Geronimo 2.1 as the Targeted Runtime, click Next 2. Add the JavaServer Faces 1.2 Facet to the Project, click Next 3. Accept the default web module settings, click Next 4. In the JSF Capabilities page, select the Server Supplied JSF Implementation option and click Finish 5. Create a new JSP page in the WebContent directory 6. Right click on the new JSP page and open it with the Web Page Editor 7. Expand the Palette in the WYSIWYG pane Expected Behavior === JSF Core and JSF HTML taglibs should be visible in the palette (as per attached screenshot) Actual Behavior === JSF Core and JSF HTML taglibs are not displayed Possible Explanation === It seems that the taglibs are not loading properly somewhere within WTP. Curiously enough, the following scenario works: 1. Copy the myfaces-api and myfaces-impl jar files from the repository into some other directory on the file system. 2. Explicitly define a JSF library in the Window - Preferences - Web and XML - JavaServerFaces Tools - Libraries page 3. Add the copied JAR files to this new library definition and check the Is JSF Implementation box. 4. Repeat steps 1-7 described above, but specify this new JSF library instead of the Server Supplied JSF Implementation in step 4. Directly linking to the files myfaces-api and myfaces-impl files in the repository when explicitly defining the JSF implementation doesn't work either. The JSF tags only display when the files sit outside the repository. So there must be something in the Geronimo runtime definition that is preventing these files from being referenced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-348) JSF Tags Not Displayed in Eclipse Web Page Editor
JSF Tags Not Displayed in Eclipse Web Page Editor - Key: GERONIMODEVTOOLS-348 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Environment: Windows XP SP2, Eclipse Europa Winter Maintenance Release, Geronimo 2.1.1, GEP 2.1.0 Reporter: Cedric Hurst Assignee: Tim McConnell Attachments: jsf palettes visible.jpg Eclipse WTP tooling provides a drag-and-drop palette for various taglibs in its Web Page Editor. When the JSF Project Facet is attached to a Dynamic Web Project, JSF Core and JSF HTML taglibs should be added to the palette (see screenshot). However, this is not the case when using Geronimo/GEP. Steps to Reproduce === 1. Create a new Dynamic Web Project using Geronimo 2.1 as the Targeted Runtime, click Next 2. Add the JavaServer Faces 1.2 Facet to the Project, click Next 3. Accept the default web module settings, click Next 4. In the JSF Capabilities page, select the Server Supplied JSF Implementation option and click Finish 5. Create a new JSP page in the WebContent directory 6. Right click on the new JSP page and open it with the Web Page Editor 7. Expand the Palette in the WYSIWYG pane Expected Behavior === JSF Core and JSF HTML taglibs should be visible in the palette (as per attached screenshot) Actual Behavior === JSF Core and JSF HTML taglibs are not displayed Possible Explanation === It seems that the taglibs are not loading properly somewhere within WTP. Curiously enough, the following scenario works: 1. Copy the myfaces-api and myfaces-impl jar files from the repository into some other directory on the file system. 2. Explicitly define a JSF library in the Window - Preferences - Web and XML - JavaServerFaces Tools - Libraries page 3. Add the copied JAR files to this new library definition and check the Is JSF Implementation box. 4. Repeat steps 1-7 described above, but specify this new JSF library instead of the Server Supplied JSF Implementation in step 4. Directly linking to the files myfaces-api and myfaces-impl files in the repository when explicitly defining the JSF implementation doesn't work either. The JSF tags only display when the files sit outside the repository. So there must be something in the Geronimo runtime definition that is preventing these files from being referenced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-348) JSF Tags Not Displayed in Eclipse Web Page Editor
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cedric Hurst updated GERONIMODEVTOOLS-348: -- Attachment: jsfPalette.JPG JSF Tags Not Displayed in Eclipse Web Page Editor - Key: GERONIMODEVTOOLS-348 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Environment: Windows XP SP2, Eclipse Europa Winter Maintenance Release, Geronimo 2.1.1, GEP 2.1.0 Reporter: Cedric Hurst Assignee: Tim McConnell Attachments: jsfPalette.JPG Eclipse WTP tooling provides a drag-and-drop palette for various taglibs in its Web Page Editor. When the JSF Project Facet is attached to a Dynamic Web Project, JSF Core and JSF HTML taglibs should be added to the palette (see screenshot). However, this is not the case when using Geronimo/GEP. Steps to Reproduce === 1. Create a new Dynamic Web Project using Geronimo 2.1 as the Targeted Runtime, click Next 2. Add the JavaServer Faces 1.2 Facet to the Project, click Next 3. Accept the default web module settings, click Next 4. In the JSF Capabilities page, select the Server Supplied JSF Implementation option and click Finish 5. Create a new JSP page in the WebContent directory 6. Right click on the new JSP page and open it with the Web Page Editor 7. Expand the Palette in the WYSIWYG pane Expected Behavior === JSF Core and JSF HTML taglibs should be visible in the palette (as per attached screenshot) Actual Behavior === JSF Core and JSF HTML taglibs are not displayed Possible Explanation === It seems that the taglibs are not loading properly somewhere within WTP. Curiously enough, the following scenario works: 1. Copy the myfaces-api and myfaces-impl jar files from the repository into some other directory on the file system. 2. Explicitly define a JSF library in the Window - Preferences - Web and XML - JavaServerFaces Tools - Libraries page 3. Add the copied JAR files to this new library definition and check the Is JSF Implementation box. 4. Repeat steps 1-7 described above, but specify this new JSF library instead of the Server Supplied JSF Implementation in step 4. Directly linking to the files myfaces-api and myfaces-impl files in the repository when explicitly defining the JSF implementation doesn't work either. The JSF tags only display when the files sit outside the repository. So there must be something in the Geronimo runtime definition that is preventing these files from being referenced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-348) JSF Tags Not Displayed in Eclipse Web Page Editor
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cedric Hurst updated GERONIMODEVTOOLS-348: -- Attachment: (was: jsf palettes visible.jpg) JSF Tags Not Displayed in Eclipse Web Page Editor - Key: GERONIMODEVTOOLS-348 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Environment: Windows XP SP2, Eclipse Europa Winter Maintenance Release, Geronimo 2.1.1, GEP 2.1.0 Reporter: Cedric Hurst Assignee: Tim McConnell Attachments: jsfPalette.JPG Eclipse WTP tooling provides a drag-and-drop palette for various taglibs in its Web Page Editor. When the JSF Project Facet is attached to a Dynamic Web Project, JSF Core and JSF HTML taglibs should be added to the palette (see screenshot). However, this is not the case when using Geronimo/GEP. Steps to Reproduce === 1. Create a new Dynamic Web Project using Geronimo 2.1 as the Targeted Runtime, click Next 2. Add the JavaServer Faces 1.2 Facet to the Project, click Next 3. Accept the default web module settings, click Next 4. In the JSF Capabilities page, select the Server Supplied JSF Implementation option and click Finish 5. Create a new JSP page in the WebContent directory 6. Right click on the new JSP page and open it with the Web Page Editor 7. Expand the Palette in the WYSIWYG pane Expected Behavior === JSF Core and JSF HTML taglibs should be visible in the palette (as per attached screenshot) Actual Behavior === JSF Core and JSF HTML taglibs are not displayed Possible Explanation === It seems that the taglibs are not loading properly somewhere within WTP. Curiously enough, the following scenario works: 1. Copy the myfaces-api and myfaces-impl jar files from the repository into some other directory on the file system. 2. Explicitly define a JSF library in the Window - Preferences - Web and XML - JavaServerFaces Tools - Libraries page 3. Add the copied JAR files to this new library definition and check the Is JSF Implementation box. 4. Repeat steps 1-7 described above, but specify this new JSF library instead of the Server Supplied JSF Implementation in step 4. Directly linking to the files myfaces-api and myfaces-impl files in the repository when explicitly defining the JSF implementation doesn't work either. The JSF tags only display when the files sit outside the repository. So there must be something in the Geronimo runtime definition that is preventing these files from being referenced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r656788 - /geronimo/server/trunk/pom.xml
On May 16, 2008, at 2:17 AM, Jarek Gawor wrote:
Jason,
Can you explain why?
Seems like I have to give this speech several times each year. I have
already sent numerous emails on the subject and spent a lot of time
trying to get rid of these properties, which I'm sad to see slowly
creeping back into the build.
The main problem is that using pom properties to manage versions of
dependencies adds additional complexity to the build and makes it
harder to actually see what versions of dependencies are being used
when inspecting poms (because the version property can not live close
to the dependency definition, when trying to understand the versions
used, a lot of bouncing around in the pom is required).
A secondary problem is that once folks see there is a property for the
version, they often keep re-specifying the version of dependencies
instead of letting maven use its dependencyManagement configuration to
resolve versions. For example, take a look at how the ${dojoVersion}
(and ${dojoLegacyVersion} properties are being used by server/trunk
#656813. You will find that each time one of the dojo artifacts is
referenced its version is also specified, when the version should only
be configured once in a dependenyManagement section.
This was one of the few properties which I had left in there before
due to the build needing to know the version to unpack and include
bits of the release archives into our dojo war files.
BUT, its not really needed, as we can figure out what the directory
name is dynamically, making this property unnecessary.
Some of the other properties I had also left there, like the
derbyVersion, since there is a bug in Maven making certain usage of
dependencyManagement information unusable. But overall I firmly
believe that we should use Maven's dependencyManagement mechanism to
manage all versions, and not dance around that by using properties, as
was the norm with Maven 1.
Our top-level pom is already overly complicated with all of the
dependencies used by various plugins. It has become almost
unmanageable. Every once in a while I inspect it to look for
problems, and often I find that folks have duplicated dependencies, or
forgot to remove old dependencies, leaving the pom to grow out of
control with junk. Adding properties for the versions of each
dependency will only compound that problem and make this file even
more unmanageable.
--jason
Jarek
On Thu, May 15, 2008 at 2:46 PM, [EMAIL PROTECTED] wrote:
Author: jdillon
Date: Thu May 15 11:46:43 2008
New Revision: 656788
URL: http://svn.apache.org/viewvc?rev=656788view=rev
Log:
STOP using properties to define versions for dependencies
Modified:
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=656788r1=656787r2=656788view=diff
=
=
=
=
=
=
=
=
=
=
--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Thu May 15 11:46:43 2008
@@ -67,8 +67,10 @@
geronimoSchemaVersion1.2/geronimoSchemaVersion
!--
-Having a single well named version properties makes
automatic updating for the weekly build much easier.
+FIXME: STOP using properties for dependency versions
unless you absolutly need them,
+ ie. you have a hundred dependencies that all use
the same version.
--
+
openejbVersion3.1-SNAPSHOT/openejbVersion
yokoVersion1.0-SNAPSHOT/yokoVersion
derbyVersion10.2.2.0/derbyVersion
@@ -83,10 +85,6 @@
plutoVersion1.1.6-G643117/plutoVersion
openjpaVersion1.0.2/openjpaVersion
xbeanVersion3.3/xbeanVersion
-gmavenVersion1.0-rc-1/gmavenVersion
-minaVersion1.1.6/minaVersion
-slf4jVersion1.5.0/slf4jVersion
-groovyVersion1.5.6/groovyVersion
wadiVersion2.0-SNAPSHOT/wadiVersion
!-- Deployers --
@@ -484,25 +482,25 @@
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-api/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-simple/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-log4j12/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
groupIdorg.slf4j/groupId
artifactIdjcl104-over-slf4j/artifactId
-version${slf4jVersion}/version
+version1.5.0/version
/dependency
dependency
@@ -1378,25 +1376,25 @@
[jira] Assigned: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen reassigned GERONIMO-3996: -- Assignee: Viet Hung Nguyen (was: Erik B. Craig) Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Viet Hung Nguyen Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-349) GEP synchronization with a server running outside of Eclipse no longer works
GEP synchronization with a server running outside of Eclipse no longer works Key: GERONIMODEVTOOLS-349 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Tim McConnell Assignee: B.J. Reed Fix For: 2.1.1 The GEP should synchronize with a Geronimo server running either inside of Eclipse or outside of Eclipse. It no longer works though when the server is started outside of Eclipse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r656788 - /geronimo/server/trunk/pom.xml
On May 16, 2008, at 2:40 AM, Donald Woods wrote:
Disagree, as using properties makes it easier to read and maintain
the versions, especially when the TCK relies on the server pom for
versions and if you create samples or plugins that want to rely on
the same versions as the server
I disagree that use of properties for versions makes the pom easier to
read or maintain, in fact I believe the complete opposite of this.
For example, you added a ${groovyVersion} property, which was in use
by 1 dependency. So as one looks through the dependencyManagement
list, runs across groovy-all-minimal... and what version is it? Well,
now they have to go back up to the top of the file to see what that
property is set to. So I guess if your idea of easier to read means
doing more work, digging around more in an already out of control xml
file, to find the information you are looking for...
And I've no idea what you mean regarding the TCK, samples or
plugins... :-\
--jason
[jira] Updated: (GERONIMODEVTOOLS-348) JSF Tags Not Displayed in Eclipse Web Page Editor
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell updated GERONIMODEVTOOLS-348: --- Fix Version/s: 2.1.1 JSF Tags Not Displayed in Eclipse Web Page Editor - Key: GERONIMODEVTOOLS-348 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-348 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Environment: Windows XP SP2, Eclipse Europa Winter Maintenance Release, Geronimo 2.1.1, GEP 2.1.0 Reporter: Cedric Hurst Assignee: Tim McConnell Fix For: 2.1.1 Attachments: jsfPalette.JPG Eclipse WTP tooling provides a drag-and-drop palette for various taglibs in its Web Page Editor. When the JSF Project Facet is attached to a Dynamic Web Project, JSF Core and JSF HTML taglibs should be added to the palette (see screenshot). However, this is not the case when using Geronimo/GEP. Steps to Reproduce === 1. Create a new Dynamic Web Project using Geronimo 2.1 as the Targeted Runtime, click Next 2. Add the JavaServer Faces 1.2 Facet to the Project, click Next 3. Accept the default web module settings, click Next 4. In the JSF Capabilities page, select the Server Supplied JSF Implementation option and click Finish 5. Create a new JSP page in the WebContent directory 6. Right click on the new JSP page and open it with the Web Page Editor 7. Expand the Palette in the WYSIWYG pane Expected Behavior === JSF Core and JSF HTML taglibs should be visible in the palette (as per attached screenshot) Actual Behavior === JSF Core and JSF HTML taglibs are not displayed Possible Explanation === It seems that the taglibs are not loading properly somewhere within WTP. Curiously enough, the following scenario works: 1. Copy the myfaces-api and myfaces-impl jar files from the repository into some other directory on the file system. 2. Explicitly define a JSF library in the Window - Preferences - Web and XML - JavaServerFaces Tools - Libraries page 3. Add the copied JAR files to this new library definition and check the Is JSF Implementation box. 4. Repeat steps 1-7 described above, but specify this new JSF library instead of the Server Supplied JSF Implementation in step 4. Directly linking to the files myfaces-api and myfaces-impl files in the repository when explicitly defining the JSF implementation doesn't work either. The JSF tags only display when the files sit outside the repository. So there must be something in the Geronimo runtime definition that is preventing these files from being referenced. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-349) GEP synchronization with a server running outside of Eclipse no longer works
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597256#action_12597256 ] Tim McConnell commented on GERONIMODEVTOOLS-349: HI BJ, I know one of your Abbot testcases starts and stops a Geronimo server within Eclipse. Would it be possible to do something similar with Abbot to start and stop a Geronimo server outside of Eclipse to ensure it synchronzies with Eclipse ?? GEP synchronization with a server running outside of Eclipse no longer works Key: GERONIMODEVTOOLS-349 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-349 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Tim McConnell Assignee: B.J. Reed Fix For: 2.1.1 The GEP should synchronize with a Geronimo server running either inside of Eclipse or outside of Eclipse. It no longer works though when the server is started outside of Eclipse -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12597321#action_12597321 ] Viet Hung Nguyen commented on GERONIMO-3996: Committed to trunk 656823. Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Viet Hung Nguyen Priority: Minor When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: confluence notifications
Seems all the commits lists were updated recently and everyone's notifications were getting filtered again. It should be fixed in a day or two. -David On May 12, 2008, at 11:56 AM, Hernan Cunico wrote: something probably went wrong on the Confluence side. IIRC Dave Blevins set this up, Dave what UID you used for shooting emails to SCM? the other question that comes to my mind is, is SCM list monitored? any chance these mails getting bounced back? Cheers! Hernan Kevan Miller wrote: On May 12, 2008, at 2:07 PM, Hernan Cunico wrote: yup, Confluence notifications from SCM are no longer flowing. If you are monitoring the spaces individually then you should still receive the notifications. Is there a reason that this has changed? I think all change notices should be going to [EMAIL PROTECTED] Confluence updates should be treated the same as code updates... --kevan
Re: Need some advice on how to include repository/* bits in the boilerplate
Hey, so now the plugins are doing the trick... yay... thanks David! But, now I'm wondering, when the server loads, it shows those plugins loading, which is fine I guess... but I'm wondering if they are eating up memory or building classpath muck that is never going to be used by the server (or well, not until we get support for running an rshd instance in the server). --jason On May 14, 2008, at 2:38 PM, David Jencks wrote: On May 13, 2008, at 6:02 PM, Donald Woods wrote: Attached patch includes other changes, like moving to jaxb 2.1, some security changes, I thought I left out the security changes, sorry. Comes from trying to do too many things at once :-( Other comments attached to GERONIMO-4013. I may have been unclear. I wasn't suggesting my initial GERONIMO-4013 patch was suitable to be committed, but that it might let us figure out some of the problems with the idea of the car- maven-plugin including maven transitive dependencies before we broke everything at once. In particular it looks to me as if the dependencies for the gshell-* plugins are too all-inclusive and was wondering what to do about this. For instance, I have no problem with removing gshell-embeddable, but would prefer to get the car-maven-plugin working better before attacking that problem. thanks david jencks -Donald David Jencks wrote: I've attached a patch to GERONIMO-4013 that reverses the changes from 4012 and change the car-maven-plugin to optionally follow transitive dependencies. I think if you apply my patch you won't be using the gshell-* plugins. I had to make a couple other minor build changes to get the build to complete. The server builds and shows signs of starting -- on my copy it runs into some problems with unrelated changes to the security system I'm working on. Jason, can you check the generated dependencies in the gshell-* plugins to see if they look remotely plausible or can be nudged closer to plausible? thanks david jencks On May 13, 2008, at 11:55 AM, David Jencks wrote: I talked with jason a bit on irc and we're doing an experiment with optionally including transitive dependencies using the car- maven-plugin. Hopefully this will work and avoid the duplication jason is leery of. Please don't commit duplication until we find out if this works or not. AFAICT this isn't a bug fix but rather new development so I'm unclear about why you are thinking of including this in 2.1.2? thanks david jencks On May 13, 2008, at 11:32 AM, Donald Woods wrote: I started with your new framework/configs/gshell-* code, updated gshell-framework to include all the individual depends so we don't need gshell-embeddable, updated server/pom.xml with the new depends and updated boilerplate with the new gshell-geronimo car depend and it looks promising. I'm still exercising some of the gsh commands, but so far help, geronimo/start-server, deploy/ connect and geronimo/stop-server are working If all looks well after a few more tests, I'll commit the changes into trunk for everyone to review before we spend the time pulling it into 2.1.2. -Donald Jason Dillon wrote: On May 13, 2008, at 1:14 AM, David Jencks wrote: So including the dependencies you need for gshell in the boilerplate's pom would get them into the geronimo repo. As I said transitive dependencies don't result in inclusion at the moment for rather good reasons. I don't know what the include tag would do but it's probably worth investigating. What include tag are you talking about? I guess I'm gonna try to make plugins for the gshell dependencies, these 3: gshell-framework - just the core bits required to make gshell work gshell-geronimo - our additional commands to work with the server + their deps gshell-remote - the remote/whisper commands I must say I'm really quite frustrated at the lack of transitive dependency support here. As this means that alot of the dependencyManagement configuration which is already in the GShell poms need to be duplicated into the Geronimo poms, making version management even more of a nightmare. :-( Well, I started to add these cars to framework/configs, but I must admit I really am clueless for how this stuff works now. :-( --jason
[jira] Closed: (GERONIMO-3996) Clicking Test these settings leads to 500 error in admin console
[ https://issues.apache.org/jira/browse/GERONIMO-3996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Viet Hung Nguyen closed GERONIMO-3996. -- Resolution: Fixed Fix Version/s: 2.1 2.2 Committed revision 656911 in branches/2.1 Clicking Test these settings leads to 500 error in admin console -- Key: GERONIMO-3996 URL: https://issues.apache.org/jira/browse/GERONIMO-3996 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console, monitoring Affects Versions: 2.1 Environment: SW: red hat enterprise linux 5.2 prerelease snapshot 3 HW: intel x86 32bit Reporter: Xia Ming Assignee: Viet Hung Nguyen Priority: Minor Fix For: 2.2, 2.1 When monitoring a remote Geronimo server, if the remote server is shutdown, then click Test these settings of that remote server monitoring in the Edit page, the 500 error will be shown. The specific exception as below: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception java.lang.IllegalArgumentException: Render parameter key or value must not be null. org.apache.pluto.internal.impl.ActionResponseImpl.setRenderParameter(ActionResponseImpl.java:179) org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:234) org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:219) org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:112) org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:158) javax.servlet.http.HttpServlet.service(HttpServlet.java:713) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) note The full stack trace of the root cause is available in the Apache Tomcat/6.0-snapshot logs. Apache Tomcat/6.0-snapshot -- 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: 656912
Geronimo Revision: 656912 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080515
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 32 minutes 37 seconds
[INFO] Finished at: Thu May 15 21:34:46 EDT 2008
[INFO] Final Memory: 353M/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/20080515/logs-2100-tomcat/test.log
[INFO] [site:attach-descriptor]
[INFO] [selenium:start-server {execution: start}]
Launching Selenium Server
Waiting for Selenium Server...
[INFO] Including display properties from:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/display.properties
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading: http://download.java.net/maven/1//woodstox/poms/wstx-asl-3.2.1.pom
Downloading:
http://people.apache.org/repo/m2-incubating-repository//woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
Downloading:
http://repo1.maven.org/maven2/woodstox/wstx-asl/3.2.1/wstx-asl-3.2.1.pom
[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:39.071
[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 27 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:37.417) Java
returned: 1
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:39.639)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:44.963)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:54.238)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:41.663)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.262)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:26.945)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:27.807)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:34.753)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:42.919)
[INFO] enterprise-testsuite/jpa-tests
[jira] Created: (GERONIMO-4021) monitoring console takes too long to recognize that a server is offline
monitoring console takes too long to recognize that a server is offline --- Key: GERONIMO-4021 URL: https://issues.apache.org/jira/browse/GERONIMO-4021 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Reporter: Viet Hung Nguyen Assignee: Viet Hung Nguyen Fix For: 2.2 Whenever the monitoring plugin attempts to monitor a server that is offline/doesn't exist, it takes way too long to load the page. We need to reduce this timeout period. I suggest that we add a parameter for the admin to set as the timeout period somewhere in the portlet. By default, we can choose to have this timeout parameter be set to 5000 milliseconds. We can use the InetAddress class to call isReachable(int timeout) to see if the server is online. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Google Analytics
Can someone add me to the list? donaldrwoods at gmail -Donald David Blevins wrote: Setup google analytics on all our spaces and added everyone who's a committer who I could easily find a gmail address for. [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You don't need a gmail address, just a google account. So if you're not in the above list, just get someone in the above list to add your google account. Just visit http://www.google.com/analytics/ to log in and view the data. It'll be a day or two before we see much of anything. -David smime.p7s Description: S/MIME Cryptographic Signature
Re: Google Analytics
Thanks Dave. Can you add [EMAIL PROTECTED] Regards, Alan On May 14, 2008, at 11:32 PM, David Blevins wrote: Setup google analytics on all our spaces and added everyone who's a committer who I could easily find a gmail address for. [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] You don't need a gmail address, just a google account. So if you're not in the above list, just get someone in the above list to add your google account. Just visit http://www.google.com/analytics/ to log in and view the data. It'll be a day or two before we see much of anything. -David
