[jira] Created: (GERONIMO-5447) Fix the testsuite
Fix the testsuite - Key: GERONIMO-5447 URL: https://issues.apache.org/jira/browse/GERONIMO-5447 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: testsuite Affects Versions: 3.0-M1 Reporter: Guang Zhe Wang Fix For: 3.0-M1 Add it-manual profile to the testsuite pom for starting the server once in the whole testsuite running phase instead of starting the server every time a new sub-testsuite begins which profile it does. In addition, some test cases related to the console should be modified due to the changes of the console in the 3.0-M1. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5446) ERROR [EjbModuleImpl] Module does not exist. when start MEJB module
[ https://issues.apache.org/jira/browse/GERONIMO-5446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888214#action_12888214 ] viola.lu commented on GERONIMO-5446: File: /openejb/branches/openejb-3.1.x/container/openejb-core/src/main/java/org/apache/openejb/util/References.java ERROR [EjbModuleImpl] Module does not exist. when start MEJB module - Key: GERONIMO-5446 URL: https://issues.apache.org/jira/browse/GERONIMO-5446 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.2.2 Environment: OS: winxp, suse 10sp2 Reporter: viola.lu Assignee: Shawn Jiang Fix For: 2.2.2 Build geronimo with lastest openejb 3.1.3 ,start server, got an error below: 2010-07-13 22:10:15,859 ERROR [EjbModuleImpl] Module does not exist. org.apache.openejb.NoSuchApplicationException: D:\g22src\plugins\mejb\geronimo-mejb\target\geronimo-mejb-2.2.2-SNAPSHOT.jar at org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:791) at org.apache.geronimo.openejb.OpenEjbSystemGBean.removeEjbJar(OpenEjbSystemGBean.java:428) at org.apache.geronimo.openejb.EjbModuleImpl.doStop(EjbModuleImpl.java:178) at org.apache.geronimo.openejb.EjbModuleImpl.doFail(EjbModuleImpl.java:191) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:983) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:539) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:816)
[BUILD] branches/2.1: Failed for Revision: 963950
Geronimo Revision: 963950 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100714/build-0200.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.1/20100714 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 29 minutes [INFO] Finished at: Wed Jul 14 02:33:58 EDT 2010 [INFO] Final Memory: 303M/1005M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100714/logs-0200-tomcat/ [INFO] Running commands-testsuite.gshell [INFO] Tests run: 4, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.763 sec FAILURE! -- [INFO] Running security-testsuite.security [INFO] Tests run: 36, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 59.852 sec FAILURE! Assembly: jetty = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.1/20100714/logs-0200-jetty/ [INFO] Running commands-testsuite.gshell [INFO] Tests run: 4, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.737 sec FAILURE! Samples: branches/2.1 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.1/20100714/samples-0200.log Build status: FAILED
[BUILD] trunk: Failed for Revision: 963958
Geronimo Revision: 963958 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/build-0300.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 37 minutes 26 seconds
[INFO] Finished at: Wed Jul 14 03:40:49 EDT 2010
[INFO] Final Memory: 439M/1015M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/logs-0300-tomcat/
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [ianal:verify-legal-files {execution: default}]
[WARNING] Skipping verification of legal files in artifacts:
[WARNING]
org.apache.geronimo.testsuite:corba-marshal-client:jar:3.0-SNAPSHOT
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/corba-marshal-client-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/corba-marshal-client/3.0-SNAPSHOT/corba-marshal-client-3.0-SNAPSHOT.jar
[INFO] [failsafe:verify {execution: verify}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/failsafe-reports
[INFO]
[INFO] Building Geronimo TestSuite :: CORBA TestSuite :: Marshal EAR
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO] Generating application.xml
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/resources
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [ear:ear {execution: default-ear}]
[INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:3.0-SNAPSHOT]
to[corba-marshal-ejb-3.0-SNAPSHOT.jar]
[INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:3.0-SNAPSHOT]
to[corba-marshal-client-3.0-SNAPSHOT.jar]
[INFO] Copy ear resources to
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT
[INFO] Could not find manifest file:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT.ear
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
into
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@1a6119a}
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost
Re: OpenEJB 3.1.* branch merge is already done?
This is a regression due to openejb-3@962740. The following patch
should be applied to openejb 3.1 branch to resovle this error:
Index:
src/main/java/org/apache/openejb/core/stateless/StatelessInstanceManager.java
===
---
src/main/java/org/apache/openejb/core/stateless/StatelessInstanceManager.java
(revision
963951)
+++
src/main/java/org/apache/openejb/core/stateless/StatelessInstanceManager.java
(working
copy)
@@ -329,8 +329,8 @@
try {
final Context context = deploymentInfo.getJndiEnc();
-context.bind(comp/EJBContext, data.sessionContext);
-context.bind(comp/WebServiceContext, new
EjbWsContext(data.sessionContext));
+context.bind(java:comp/EJBContext, data.sessionContext);
+context.bind(java:comp/WebServiceContext, new
EjbWsContext(data.sessionContext));
} catch (NamingException e) {
throw new OpenEJBException(Failed to bind EJBContext, e);
}
Kevan, Could you please help apply the patch above ? Thanks in advance.
On Tue, Jul 13, 2010 at 10:16 PM, viola lu viola...@gmail.com wrote:
Hi, Kevan:
Here is the error log, now i am trying to revert local open 3.1.* to
previous revisions one by one after July 7, and then build openejb ,
geronimo 2.2.2 to check which revision results in this error. If you can
give some information, thanks in advance!
2010-07-13 22:10:15,843 INFO [startup] Undeploying app:
D:\g22src\plugins\mejb\geronimo-mejb\target\geronimo-mejb-2.2.2-SNAPSHOT.jar
2010-07-13 22:10:15,859 ERROR [EjbModuleImpl] Module does not exist.
org.apache.openejb.NoSuchApplicationException:
D:\g22src\plugins\mejb\geronimo-mejb\target\geronimo-mejb-2.2.2-SNAPSHOT.jar
at
org.apache.openejb.assembler.classic.Assembler.destroyApplication(Assembler.java:791)
at
org.apache.geronimo.openejb.OpenEjbSystemGBean.removeEjbJar(OpenEjbSystemGBean.java:428)
at
org.apache.geronimo.openejb.EjbModuleImpl.doStop(EjbModuleImpl.java:178)
at
org.apache.geronimo.openejb.EjbModuleImpl.doFail(EjbModuleImpl.java:191)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:983)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:525)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:110)
at
org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:145)
at
org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:119)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:175)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44)
at
org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:253)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:295)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:539)
at
org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377)
at
org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456)
at
org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190)
at
org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546)
at
[BUILD] branches/2.2: Failed for Revision: 964008
Geronimo Revision: 964008 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100714/build-0800.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100714/unit-test-reports 2) org.apache.axis2:axis2-jaxws:jar:1.5.2-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) 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:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.ws.commons.axiom:axiom-api:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-api -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-api -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-api:jar:1.2.9-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-impl:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-impl -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-impl -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-impl:jar:1.2.9-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-dom -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-dom -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.axis2:axis2-jaxws:jar:1.5.2-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http
Re: [VOTE] Release Geronimo Samples 3.0-M1 -- Third Attempt
+1 On 7/1/2010 1:29 PM, Forrest Xia wrote: Hi All, A release candidate for Geronimo Samples 3.0-M1 has been created and staged. This release includes these samples which works with Geronimo 3.0-M1: 1. Java EE 5 samples * dbtester * inventory * ldap-sample-app * timereport * jsp-examples * servlet-examples 2. Java EE 6 samples * cviewer-javaee6 * converter-javaee6 * jarresource-javaee6 * fileupload-javaee6 3. OSGi samples * aries-datasource 4. Daytrader * daytrader-web-jdbc * daytrader-web-jpa The tag has been created here: https://svn.apache.org/repos/asf/geronimo/samples/tags/samples-parent-3.0-M1/ The staging repo is here: https://repository.apache.org/content/repositories/orgapachegeronimo-029/ The main artifacts up for vote are the source release archives: https://repository.apache.org/content/repositories/orgapachegeronimo-029/org/apache/geronimo/samples/samples-parent/3.0-M1/samples-parent-3.0-M1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-029/org/apache/geronimo/samples/samples-parent/3.0-M1/samples-parent-3.0-M1-source-release.zip A sample plugin catalog file is prepared for your convenience: http://geronimo.apache.org/plugins/samples-3.0-M1/ The vote will be last for 72 hours. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) Forrest
[BUILD] trunk: Failed for Revision: 964039
Geronimo Revision: 964039 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 17 seconds
[INFO] Finished at: Wed Jul 14 09:44:39 EDT 2010
[INFO] Final Memory: 471M/1014M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/logs-0900-tomcat/
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [ianal:verify-legal-files {execution: default}]
[WARNING] Skipping verification of legal files in artifacts:
[WARNING]
org.apache.geronimo.testsuite:corba-marshal-client:jar:3.0-SNAPSHOT
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/corba-marshal-client-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/corba-marshal-client/3.0-SNAPSHOT/corba-marshal-client-3.0-SNAPSHOT.jar
[INFO] [failsafe:verify {execution: verify}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/failsafe-reports
[INFO]
[INFO] Building Geronimo TestSuite :: CORBA TestSuite :: Marshal EAR
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO] Generating application.xml
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/resources
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [ear:ear {execution: default-ear}]
[INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:3.0-SNAPSHOT]
to[corba-marshal-ejb-3.0-SNAPSHOT.jar]
[INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:3.0-SNAPSHOT]
to[corba-marshal-client-3.0-SNAPSHOT.jar]
[INFO] Copy ear resources to
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT
[INFO] Could not find manifest file:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT.ear
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
into
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@51b30d}
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost
[jira] Commented: (GERONIMO-5441) Update openejb pool JMX attributes
[ https://issues.apache.org/jira/browse/GERONIMO-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888369#action_12888369 ] viola.lu commented on GERONIMO-5441: pls help review it.thanks Update openejb pool JMX attributes --- Key: GERONIMO-5441 URL: https://issues.apache.org/jira/browse/GERONIMO-5441 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.2.2 Reporter: viola.lu Assignee: viola.lu Fix For: 2.2.2 Attachments: G5441.patch Based on the update from openejb pool jmx attributes in openejb : https://issues.apache.org/jira/browse/OPENEJB-1235, reflect those changes in file $g22src\plugins\openejb\geronimo-openejb\src\main\java\org\apache\geronimo\openejb\StatelessContainerGBean.java Added the following pool config options: GarbageCollection ReplaceFlushed Renamed the following pool config options: PoolMin - MinSize PoolMax - MaxSize PollInterval - SweepInterval Pool will also now call @PreDestroy callbacks on garbage collected instances Added the following pool JMX attributes: GarbageCollection ReplaceFlushed InstancesIdle InstancesActive Renamed the following pool JMX attributes: PollInterval - SweepInterval Available - AvailablePermits Instances - InstancesPooled -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5441) Update openejb pool JMX attributes
[ https://issues.apache.org/jira/browse/GERONIMO-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu updated GERONIMO-5441: --- Attachment: G5441.patch Update openejb pool JMX attributes --- Key: GERONIMO-5441 URL: https://issues.apache.org/jira/browse/GERONIMO-5441 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: OpenEJB Affects Versions: 2.2.2 Reporter: viola.lu Assignee: viola.lu Fix For: 2.2.2 Attachments: G5441.patch Based on the update from openejb pool jmx attributes in openejb : https://issues.apache.org/jira/browse/OPENEJB-1235, reflect those changes in file $g22src\plugins\openejb\geronimo-openejb\src\main\java\org\apache\geronimo\openejb\StatelessContainerGBean.java Added the following pool config options: GarbageCollection ReplaceFlushed Renamed the following pool config options: PoolMin - MinSize PoolMax - MaxSize PollInterval - SweepInterval Pool will also now call @PreDestroy callbacks on garbage collected instances Added the following pool JMX attributes: GarbageCollection ReplaceFlushed InstancesIdle InstancesActive Renamed the following pool JMX attributes: PollInterval - SweepInterval Available - AvailablePermits Instances - InstancesPooled -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ${project.version} is a problem..
That's the expected behavior, in that ${project.version} is the current
module's version and not that of it's parent. If you need the parent's
version, then yes, we need a property like geronimoVersion.
-Donald
On 7/13/10 10:56 PM, Rex Wang wrote:
Hi,
I suggest we stop using ${project.version} in 3.0's pom.
This maven variable will magicly change when I create a new sub-project
which has it own version.
For example,
When I create a new server assembly abc under the assemblies project,
and the abc's pom has it own version 3.0.0.0 http://3.0.0.0:
parent
groupIdorg.apache.geronimo.assemblies/groupId
artifactIdassemblies/artifactId
version3.0-M1/version
/parent
groupIdc.i.w.assemblies/groupId
artifactIdabc/artifactId
version3.0.0.0/version
packagingserver-assembly/packaging
Then, in its effective pom, maven will replace all the
${project.version} defined in parent pom with 3.0.0.0
I think we use ${geronimoVersion} instead and specify geronimoVersion
explicitly in root pom.
Thoughts?
--
Lei Wang (Rex)
rwonly AT apache.org http://apache.org
Re: Question about geronimoHome configuration in geronimo-maven-plugin
You could also set it as a property in the pom, like -
properties
geronimoHome${project.build.outputDirectory}/geronimoHome
/properties
which allows users to override it either in settings.xml or on the
command line. In your case, you could define a profile in settings.xml
that sets geronimoHome for your specific machine and then enable it when
building, like -
mvn clean install -Pg30home
Including hard-coded paths in poms is not a best practice, unless you
allow users to override it. Otherwise, we are adding profiles that are
specific to each user's machine and making the pom harder to maintain...
-Donald
On 7/14/10 12:54 AM, Shawn Jiang wrote:
You could use optionSets to add your customized properties.
1, add optionSets to your geronimo-maven-plugin configuration
plugin
groupIdorg.apache.geronimo.buildsupport/groupId
artifactIdgeronimo-maven-plugin/artifactId
configuration
optionSets
optionSet
idmoreMemory/id
options
option-XX:MaxPermSize=256m/option
option-XX:+HeapDumpOnOutOfMemoryError/option
option-enableassertions/option
/options
/optionSet
optionSet
idghome/id
options
option-DgeronimoHome=/home/genspring/geronimo222-SNAPSHOT
/option
option-DXXX=XXX
/option
/options
/optionSet
/optionSets
/configuration
/plugin
2, add -Doptions=xxx when do the mvn build to active the option set.
mvn clean install -Doptions=ghome
On Wed, Jul 14, 2010 at 11:20 AM, viola lu viola.lu
http://viola.lu@gmail.com http://gmail.com wrote:
From geronimo-maven-plugin site doc, it described that if i want to
run a customized geornimo server, i can run command:
mvn geronimo:start-server -DgeronimoHome=[$dir_geronimo-server]
but i want to define geronimoHome in pom.xml not in command, how to
configure geronimo-maven-plugin?
The way below is possible?thanks in advance!
plugin
groupIdorg.apache.geronimo.plugins/groupId
artifactIdgeronimo-maven-plugin/artifactId
configuration
geronimoHomec:\server1\/geroninomHome
/configuration
/plugin
--
viola
--
Shawn
Re: [VOTE] Release new versions of the Geronimo bundle components
+1 Was able to build all 6 from their tags and each passed rat:check. Note: The version on woodstox has an extra _1 and should be listed as woodstox-4.0.6_1. -Donald On 7/13/10 10:43 AM, Rick McGuire wrote: To allow the Geronimo trunk release to upgrade the some of the components used by the server, I'd like release new versions of some of the Geronimo bundle components. This components are versions of external Geronimo dependencies that have been converted into OSGi jars. This is a single vote for multiple upgraded bundles used by the Geronimo 3.0 trunk branch. The RAT and IANAL plugins have been run against of the projects. All tag svn versions have been successfully built. Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-056/ All source repos are relative to location https://svn.apache.org/repos/asf/geronimo/bundles/tags and have the same final element as the artifact name. The following components are being voted on (the bundles-parent has already been promoted): aspectjrt-1.6.8_1 aspectjweaver-1.6.8_1 derby-all-10.6.1.0_1 sxc-jaxb-0.7.3_1 sxc-runtime-0.7.3_1 woodstox-4.0.6_1_1
Re: ${project.version} is a problem..
On Jul 13, 2010, at 7:56 PM, Rex Wang wrote:
Hi,
I suggest we stop using ${project.version} in 3.0's pom.
This maven variable will magicly change when I create a new sub-project which
has it own version.
For example,
When I create a new server assembly abc under the assemblies project, and
the abc's pom has it own version 3.0.0.0:
parent
groupIdorg.apache.geronimo.assemblies/groupId
artifactIdassemblies/artifactId
version3.0-M1/version
/parent
groupIdc.i.w.assemblies/groupId
artifactIdabc/artifactId
version3.0.0.0/version
packagingserver-assembly/packaging
Then, in its effective pom, maven will replace all the ${project.version}
defined in parent pom with 3.0.0.0
I think we use ${geronimoVersion} instead and specify geronimoVersion
explicitly in root pom.
Thoughts?
I think this is a really bad idea. In your example above, you should not have
the explicit version version3.0.0.0/version
Generally, if you want a different version for a particular project, put the
project in a different tree without a file system parent pom. There are a few
special cases like the bundles even those probably shouldn't have a file
system parent pom (not actually sure if they do right now).
thanks
david jencks
--
Lei Wang (Rex)
rwonly AT apache.org
[BUILD] branches/2.2: Failed for Revision: 964101
Geronimo Revision: 964101 built with tests included See the full build-1400.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100714/build-1400.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100714/unit-test-reports 2) org.apache.axis2:axis2-jaxws:jar:1.5.2-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) 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:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.ws.commons.axiom:axiom-api:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-api -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-api -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-api:jar:1.2.9-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-impl:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-impl -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-impl -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-impl:jar:1.2.9-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-dom -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-dom -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.axis2:axis2-jaxws:jar:1.5.2-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), codehaus.snapshots (http
[jira] Reopened: (GERONIMO-5259) Annoying access denied security exceptions for oenwebbeans while java2 security is enabled.
[ https://issues.apache.org/jira/browse/GERONIMO-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YING WANG reopened GERONIMO-5259: - 299 TCK does not like the protected nested static helper class. We need to switch to anonymous inner classes. I will upload patch shortly. === Added Classes - javax.enterprise.util.AnnotationLiteral$PrivilegedActionForAccessibleObject Added Nested Classes javax.enterprise.util.AnnotationLiteral:nested protected static javax.enterprise.util.AnnotationLiteral$PrivilegedActionForAccessibleObject STATUS:Failed.2 errors === Annoying access denied security exceptions for oenwebbeans while java2 security is enabled. - Key: GERONIMO-5259 URL: https://issues.apache.org/jira/browse/GERONIMO-5259 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: specs Affects Versions: 3.0 Reporter: YING WANG Assignee: Donald Woods Priority: Minor Fix For: 3.0-M1 Attachments: 5259.patch, AnnotationLiteral.java Hello neighbors, I am from the openwebbean project. while I am fixing owb-312 (https://issues.apache.org/jira/browse/OWB-312), I found some of AccessControlExceptions are fired fom javax.enterprise.util.AnnotationLiteral in jcdi api. Fixing the issue in OWB will be nasty since it is referenced all over the owb code. Could we add doPrivileged block around Class.setAccess() and getDeclaredMethods calls in this class? Thanks in advnace. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ${project.version} is a problem..
I see this as a common use case, where users want to build their own
assemblies, but want ONE place to change the Geronimo version they are
using (as using scopeimport/scope doesn't resolve this for every
case anymore.) Heck, we even use this method for our TCK builds.
-Donald
On 7/14/10 12:31 PM, David Jencks wrote:
On Jul 13, 2010, at 7:56 PM, Rex Wang wrote:
Hi,
I suggest we stop using ${project.version} in 3.0's pom.
This maven variable will magicly change when I create a new
sub-project which has it own version.
For example,
When I create a new server assembly abc under the assemblies
project, and the abc's pom has it own version 3.0.0.0 http://3.0.0.0/:
parent
groupIdorg.apache.geronimo.assemblies/groupId
artifactIdassemblies/artifactId
version3.0-M1/version
/parent
groupIdc.i.w.assemblies/groupId
artifactIdabc/artifactId
version3.0.0.0/version
packagingserver-assembly/packaging
Then, in its effective pom, maven will replace all the
${project.version} defined in parent pom with 3.0.0.0
I think we use ${geronimoVersion} instead and specify geronimoVersion
explicitly in root pom.
Thoughts?
I think this is a really bad idea. In your example above, you should
not have the explicit version version3.0.0.0/version
Generally, if you want a different version for a particular project, put
the project in a different tree without a file system parent pom. There
are a few special cases like the bundles even those probably
shouldn't have a file system parent pom (not actually sure if they do
right now).
thanks
david jencks
--
Lei Wang (Rex)
rwonly AT apache.org http://apache.org/
[BUILD] trunk: Failed for Revision: 964138
Geronimo Revision: 964138 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 30 seconds
[INFO] Finished at: Wed Jul 14 15:41:52 EDT 2010
[INFO] Final Memory: 470M/987M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/logs-1500-tomcat/
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO] [ianal:verify-legal-files {execution: default}]
[WARNING] Skipping verification of legal files in artifacts:
[WARNING]
org.apache.geronimo.testsuite:corba-marshal-client:jar:3.0-SNAPSHOT
[INFO] [install:install {execution: default-install}]
[INFO] Installing
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/corba-marshal-client-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/corba-marshal-client/3.0-SNAPSHOT/corba-marshal-client-3.0-SNAPSHOT.jar
[INFO] [failsafe:verify {execution: verify}]
[INFO] Failsafe report directory:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-client/target/failsafe-reports
[INFO]
[INFO] Building Geronimo TestSuite :: CORBA TestSuite :: Marshal EAR
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [ear:generate-application-xml {execution:
default-generate-application-xml}]
[INFO] Generating application.xml
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/resources
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] [ear:ear {execution: default-ear}]
[INFO] Copying
artifact[ejb:org.apache.geronimo.testsuite:corba-marshal-ejb:3.0-SNAPSHOT]
to[corba-marshal-ejb-3.0-SNAPSHOT.jar]
[INFO] Copying
artifact[jar:org.apache.geronimo.testsuite:corba-marshal-client:3.0-SNAPSHOT]
to[corba-marshal-client-3.0-SNAPSHOT.jar]
[INFO] Copy ear resources to
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT
[INFO] Could not find manifest file:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/src/main/application/META-INF/MANIFEST.MF
- Generating one
[INFO] Building jar:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/corba-marshal-ear-3.0-SNAPSHOT.ear
[INFO] [geronimo:start-server {execution: start-geronimo}]
[INFO] Using assembly configuration: tomcat
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-tomcat7-javaee6-3.0-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat7-javaee6/3.0-SNAPSHOT/geronimo-tomcat7-javaee6-3.0-SNAPSHOT-bin.zip
into
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/corba-testsuite/corba-marshal/corba-marshal-ear/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Initialized with URL:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector,
environment: {jmx.remote.credentials=[Ljava.lang.String;@140b31}
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connecting to:
service:jmx:rmi://localhost/jndi/rmi://localhost:1099/JMXConnector
[org.apache.geronimo.mavenplugins.geronimo.ServerProxy] : Connection failure;
ignoring: java.io.IOException: Failed to retrieve RMIServer stub:
javax.naming.ServiceUnavailableException [Root exception is
java.rmi.ConnectException: Connection refused to host: localhost; nested
[BUILD] branches/2.2: Failed for Revision: 964258
Geronimo Revision: 964258 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100714/build-2000.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.2/20100714/unit-test-reports 2) org.apache.axis2:axis2-jaxws:jar:1.5.2-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) 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:301) 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.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.ws.commons.axiom:axiom-api:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-api -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-api -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-api:jar:1.2.9-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-impl:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-impl -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-impl -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.ws.commons.axiom:axiom-impl:jar:1.2.9-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-dom -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ws.commons.axiom -DartifactId=axiom-dom -Dversion=1.2.9-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT 2) org.apache.axis2:axis2-jaxws:jar:1.5.2-SNAPSHOT 3) org.apache.ws.commons.axiom:axiom-dom:jar:1.2.9-SNAPSHOT -- 3 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-axis2:jar:2.2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), apache.snapshots (http
Re: [VOTE] Geronimo Eclipse Plugin 2.1.6 RC1
We only have one PMC voting. Could anyone help to review it? 2010/7/14 Delos dait...@gmail.com Thanks, Donald! Hope other PMC members can take a look at this! 2010/7/13 Donald Woods dwo...@apache.org +1 Was able to build the tag on Win7 (but not Mac as with GEP 3.0.0) and rat:check returned some hits that can be ignored (can we backport the excludes list from trunk to ignore all of the .* Eclipse files?) -Donald On 7/8/10 10:12 AM, Delos wrote: Hi all, Please review and vote on the release of the Geronimo Eclipse Plugin 2.1.6 *RC1*. GEP 2.1.6 supports Geronimo server 2.1.6 and Eclipse 3.6. *Note*: Now, GEP 2.1.6 can only build on Windows and Linux, but fail to build on Mac. Because eclipse 3.6 no longer support carbon and maven-eclipsepde-plugin doesn't support new cocoa package, GEP can't build successfully on Mac until a new maven-eclipsepde-plugin is released. It's not a problem of GEP itself, so I think it's not a big issue blocking the release. Please see GERONIMODEVTOOLS-649 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649 for details. The source code zip is here: _ https://repository.apache.org/content/repositories/orgapachegeronimo-043/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.6/geronimo-eclipse-plugin-2.1.6-source-release.tar.gz_ _ https://repository.apache.org/content/repositories/orgapachegeronimo-043/org/apache/geronimo/devtools/geronimo-eclipse-plugin/2.1.6/geronimo-eclipse-plugin-2.1.6-source-release.zip_ The deployable zip file is here: _ http://people.apache.org/builds/geronimo/eclipse/2.1.6/geronimo-eclipse-plugin-2.1.6-deployable.zip_ The update site zip file is here: _ http://people.apache.org/builds/geronimo/eclipse/2.1.6/geronimo-eclipse-plugin-2.1.6-updatesite.zip_ http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC2/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip The tag is here: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-2.1.6/ If you would like to review and/or comment on the release notes, they are here: http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-2.1.6.txt Finally, I've created a Staging Site that can be used to test the update manager functions (i.e., p2 in Halios or Galileo) of Eclipse for downloading the GEP itself. http://people.apache.org/builds/geronimo/eclipse/updates/ Please let me know if there are any questions and/or problems. -- Best Regards, Delos -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] Geronimo Eclipse Plugin 3.0M1 - second try
We only have one PMC voting. Could anyone else help to review it? 2010/7/13 Delos dait...@gmail.com Thanks, Donald! For the Download menu, Bill thought it should be obvious to users. So we add the top menu in eclipse. Do you have any other ideas for this? You're right, the osgi tools is only applicable for 3.6, I think we can disable the menu in eclipse 3.5. Thanks again! 2010/7/13 Donald Woods dwo...@apache.org +1 Was able to build the tag on Win7, use the built update site to install GEP into a clean Eclipse 3.5.2 using Java 1.6.0 and start/stop a Geronimo 3.0-M1 Tomcat assembly. Some thoughts - I don't like how we add a new Download menu in the Eclipse IDE, considering the Download Servers option is available when creating a new Server runtime and the link to the OSGi tools is only applicable to 3.6 users. -Donald On 7/6/10 12:18 PM, Delos wrote: Hi everyone, Please review and vote on the release of the Geronimo Eclipse Plugin 3.0M1 *RC2*. *Note*: Now, GEP 3.0M1 can only build on Windows and Linux, but fail to build on Mac. Because eclipse 3.6 no longer support carbon and maven-eclipsepde-plugin doesn't support new cocoa package, GEP can't build successfully on Mac until a new maven-eclipsepde-plugin is released. It's not a problem of GEP itself, so I think it's not a big issue blocking the release. Please see GERONIMODEVTOOLS-649 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649 for details. The source code zip is here: https://repository.apache.org/content/repositories/orgapachegeronimo-039/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0_M1/geronimo-eclipse-plugin-3.0_M1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-039/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0_M1/geronimo-eclipse-plugin-3.0_M1-source-release.zip The deployable zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0M1/geronimo-eclipse-plugin-3.0_M1-deployable.zip The update site zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0M1/geronimo-eclipse-plugin-3.0_M1-updatesite.zip http://people.apache.org/dist/geronimo/eclipse/2.2.0/RC2/staging_site/geronimo-eclipse-plugin-2.2.0-updatesite.zip The tag is here: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0_M1/ If you would like to review and/or comment on the release notes, they are here: http://people.apache.org/builds/geronimo/eclipse/3.0M1/PLUGIN_RELEASE-NOTES-3.0_M1.txt Finally, I've created a Staging Site that can be used to test the update manager functions (i.e., p2 in Halios or Galileo) of Eclipse for downloading the GEP itself. http://people.apache.org/builds/geronimo/eclipse/updates/ Please let me know if there are any questions and/or problems. -- Best Regards, Delos -- Best Regards, Delos -- Best Regards, Delos
[BUILD] trunk: Failed for Revision: 964271
Geronimo Revision: 964271 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20100714/unit-test-reports 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-ajp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-ajp:jar:8.0.0.M1-SNAPSHOT 3) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-jaspi -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-jaspi:jar:8.0.0.M1-SNAPSHOT 4) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-webapp -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-webapp:jar:8.0.0.M1-SNAPSHOT 5) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-security -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-security:jar:8.0.0.M1-SNAPSHOT 6) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.eclipse.jetty -DartifactId=jetty-servlet -Dversion=8.0.0.M1-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT 2) org.eclipse.jetty:jetty-servlet:jar:8.0.0.M1-SNAPSHOT -- 6 required artifacts are missing. for artifact: org.apache.geronimo.modules:geronimo-jetty8:bundle:3.0-SNAPSHOT from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), local (file:///home/geronimo/.m2/jtidy.repository), ibiblio.org (http://maven.rtp.raleigh.ibm.com/nexus-proxy/), java.net.2 (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:360) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively
[jira] Created: (GERONIMO-5448) Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website
Update news for Geronimo 2.1.6 and 3.0M1 on Geronimo website Key: GERONIMO-5448 URL: https://issues.apache.org/jira/browse/GERONIMO-5448 Project: Geronimo Issue Type: Task Security Level: public (Regular issues) Components: documentation Affects Versions: 2.1.6, 3.0-M1 Reporter: Chi Runhua Geronimo 2.1.6 and 3.0M1 have been released for some time, but the news on GMOxSITE is still showing the latest version is 2.1.5 I think we should update the news. See http://geronimo.apache.org/index.html http://geronimo.apache.org/news-archive.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5418) Console testsuite failures are caused by the new DOJO navigation tree
[ https://issues.apache.org/jira/browse/GERONIMO-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] janel Zhang updated GERONIMO-5418: -- Attachment: (was: console-testsuite.patch) Console testsuite failures are caused by the new DOJO navigation tree - Key: GERONIMO-5418 URL: https://issues.apache.org/jira/browse/GERONIMO-5418 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2.2, 3.0-M1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Fix For: 2.2.2 Attachments: GERONIMO-5418.patch From Geronimo 2.2.1, the console navigation tree is rendered by DOJO, by default, all link items are folded after login. This cause selenium failed to get the right link information. We shall find a way to conquer the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5418) Console testsuite failures are caused by the new DOJO navigation tree
[ https://issues.apache.org/jira/browse/GERONIMO-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] janel Zhang updated GERONIMO-5418: -- Attachment: console-testsuite.patch This is a solution to navigation tree test. Console testsuite failures are caused by the new DOJO navigation tree - Key: GERONIMO-5418 URL: https://issues.apache.org/jira/browse/GERONIMO-5418 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2.2, 3.0-M1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Fix For: 2.2.2 Attachments: console-testsuite.patch, GERONIMO-5418.patch From Geronimo 2.2.1, the console navigation tree is rendered by DOJO, by default, all link items are folded after login. This cause selenium failed to get the right link information. We shall find a way to conquer the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5418) Console testsuite failures are caused by the new DOJO navigation tree
[ https://issues.apache.org/jira/browse/GERONIMO-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] janel Zhang updated GERONIMO-5418: -- Attachment: (was: console-testsuite.patch) Console testsuite failures are caused by the new DOJO navigation tree - Key: GERONIMO-5418 URL: https://issues.apache.org/jira/browse/GERONIMO-5418 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2.2, 3.0-M1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Fix For: 2.2.2 Attachments: GERONIMO-5418.patch From Geronimo 2.2.1, the console navigation tree is rendered by DOJO, by default, all link items are folded after login. This cause selenium failed to get the right link information. We shall find a way to conquer the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-5418) Console testsuite failures are caused by the new DOJO navigation tree
[
https://issues.apache.org/jira/browse/GERONIMO-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
janel Zhang updated GERONIMO-5418:
--
Attachment: console-testsuite.patch
This is solution to Dojo navigation tree.
1.To get tree node id,we can use dojo script methods.The main method is as
following:var
navigationTree=this.browserbot.getCurrentWindow().dijit.byId('navigationTree');
var wrapperNode
=navigationTree._itemNodesMap[+navigationTreeLabel2Index.get(navigationTreeLabel).intValue()+];
wrapperNode[0].id;
The wrapperNode[0].id is the tree node id.
2.Because the dojo tree is cached in memory in very short time,we should
collapase the tree node at first before click the tree node. To solve it ,we
can use the method:navigationTree._collapseNode(wrapperNode[0]);
Console testsuite failures are caused by the new DOJO navigation tree
-
Key: GERONIMO-5418
URL: https://issues.apache.org/jira/browse/GERONIMO-5418
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Affects Versions: 2.2.2, 3.0-M1, 3.0
Reporter: Forrest Xia
Assignee: Forrest Xia
Priority: Minor
Fix For: 2.2.2
Attachments: console-testsuite.patch, GERONIMO-5418.patch
From Geronimo 2.2.1, the console navigation tree is rendered by DOJO, by
default, all link items are folded after login. This cause selenium failed to
get the right link information.
We shall find a way to conquer the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: ${project.version} is a problem..
2010/7/15 David Jencks david_jen...@yahoo.com
On Jul 13, 2010, at 7:56 PM, Rex Wang wrote:
Hi,
I suggest we stop using ${project.version} in 3.0's pom.
This maven variable will magicly change when I create a new sub-project
which has it own version.
For example,
When I create a new server assembly abc under the assemblies project, and
the abc's pom has it own version 3.0.0.0:
parent
groupIdorg.apache.geronimo.assemblies/groupId
artifactIdassemblies/artifactId
version3.0-M1/version
/parent
groupIdc.i.w.assemblies/groupId
artifactIdabc/artifactId
version3.0.0.0/version
packagingserver-assembly/packaging
Then, in its effective pom, maven will replace all the ${project.version}
defined in parent pom with 3.0.0.0
I think we use ${geronimoVersion} instead and specify geronimoVersion
explicitly in root pom.
Thoughts?
I think this is a really bad idea. In your example above, you should not
have the explicit version version3.0.0.0/version
Generally, if you want a different version for a particular project, put
the project in a different tree without a file system parent pom.
It will save a lot of time to create a custom assembly with geronimo's
parent pom..and if all the sub-poms can not have its version and must use
{project.version}, which is actually the geronimo root pom's version. What's
the difference/risk between using a geronimoVersion property and that?
Actually, geronimoVersion has already been used in 3.0-m1 trunk...
-Rex
There are a few special cases like the bundles even those probably
shouldn't have a file system parent pom (not actually sure if they do right
now).
thanks
david jencks
--
Lei Wang (Rex)
rwonly AT apache.org
--
Lei Wang (Rex)
rwonly AT apache.org
[jira] Commented: (GERONIMO-5418) Console testsuite failures are caused by the new DOJO navigation tree
[ https://issues.apache.org/jira/browse/GERONIMO-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12888689#action_12888689 ] Forrest Xia commented on GERONIMO-5418: --- Committed revision 964294. Thank you janel for this patch! Console testsuite failures are caused by the new DOJO navigation tree - Key: GERONIMO-5418 URL: https://issues.apache.org/jira/browse/GERONIMO-5418 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 2.2.2, 3.0-M1, 3.0 Reporter: Forrest Xia Assignee: Forrest Xia Priority: Minor Fix For: 2.2.2 Attachments: console-testsuite.patch, GERONIMO-5418.patch From Geronimo 2.2.1, the console navigation tree is rendered by DOJO, by default, all link items are folded after login. This cause selenium failed to get the right link information. We shall find a way to conquer the problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5403) G 3.0-M1 car-maven-plugin generated plugin dependecies do not have version, that causes plugin installation are panic
[ https://issues.apache.org/jira/browse/GERONIMO-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Forrest Xia closed GERONIMO-5403. - Fix Version/s: 3.0 Resolution: Invalid The plugin project I compiled missed a configuration property of car-maven-plugin: useMavenDependencies valuetrue/value includeVersiontrue/includeVersion useTransitiveDependenciestrue/useTransitiveDependencies /useMavenDependencies So this jira is not valid for 3.0-M1. G 3.0-M1 car-maven-plugin generated plugin dependecies do not have version, that causes plugin installation are panic - Key: GERONIMO-5403 URL: https://issues.apache.org/jira/browse/GERONIMO-5403 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 3.0-M1 Reporter: Forrest Xia Priority: Critical Fix For: 3.0 G 3.0-M1 car-maven-plugin generates geronimo-plugin.xml and geronimo-plugins.xml, in which there are no version info for plugin's dependencies. This may cause problem. Saying geronimo plugin A depends on artifact B. The B has two different versions in the local repository, saying B-v1 and B-v2. now issue command $ bin/deploy install-plugin A-v2 to install plugin from local, The A-v2 should depends on B-v2. But when installation happens, the B-v1 is pulled from the local repository, that leads the installation failed. I checked G 2.2 and see the versions there in the dependencies, but why not for G 3.0-M1? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
