[BUILD] 2.2: Failed for Revision: 629381
Geronimo Revision: 629381 built with tests included See the full build-0300.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080220/build-0300.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/trunk/20080220/unit-test-reports codehaus-snapshots (http://snapshots.repository.codehaus.org), java.net (http://download.java.net/maven/1/), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.pluto:pluto-container:jar:1.2.0-G601061 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -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.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) org.apache.pluto:pluto-container:jar:1.2.0-G601061 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), module-local (file:///home/geronimo/geronimo/trunk/repository/), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), java.net (http://download.java.net/maven/1/), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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.pluto:pluto-container:jar:1.2.0-G601061 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -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.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) org.apache.pluto:pluto-container:jar:1.2.0-G601061 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), module-local (file:///home/geronimo/geronimo/trunk/repository/), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), java.net (http://download.java.net/maven/1/), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), apache.snapshots
[jira] Assigned: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma reassigned GERONIMO-3865: Assignee: YunFeng Ma unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: YunFeng Ma There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-285) Handling multiple schema versions creating a test application that can output say geronimo-web.xml in different versions
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma updated GERONIMODEVTOOLS-285: Attachment: testapp.zip A test application testapp.zip. In this test application, v1.1 and v2.0 jaxb classes are generated according to their schema files, and also includes two simple test cases for the generated classes. One question: I can not figure out how to handle multiple schema version in one test application ( there are two test application for different schema version), or this is not necessary. Thoughts? Handling multiple schema versions creating a test application that can output say geronimo-web.xml in different versions -- Key: GERONIMODEVTOOLS-285 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-285 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: YunFeng Ma Assignee: YunFeng Ma Attachments: testapp.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo in year 2008
On Feb 16, 2008 8:30 AM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Feb 15, 2008 1:30 AM, Shiva Kumar H R [EMAIL PROTECTED] wrote: GEP Task https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278 is created for this. We can use this, as well as IRC chats dev-list mails, for collaborating! Please use [EMAIL PROTECTED] for any important stuff around it. I'd be glad to learn a bit about Eclipse plugin development following your conversations. Okey? I have generally found discussions on IRC leading to quicker better understanding of problems. All discussions on #geronimo get logged in http://servlet.uwyn.com/drone/log/bevinbot/geronimo/mmdd and I typically paste those links into relevant JIRAs. So no discussions are lost. Now duplicating this effort by again posting mails on dev-list would be very time consuming :( -- Thanks, Shiva Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: G v2.1 and liferay
On Feb 19, 2008 1:30 PM, Peter Petersson [EMAIL PROTECTED] wrote: Hi Ever now and then configuration questions about setting up liferay with G is popping up on the user list and soon it is time for G v2.1 to come out of the closet. As it would be great to see a liferay bundle (upgrade) that works out of the box with G v2.1 my question is if anyone of you knows the status of liferays Geronimo 2.1 support or even if someone is helping them out ? As I understand it at least the liferay Geronimo plan needs some revamping. A user on user-list was facing issues with deploying liferay war onto Geronimo. I attempted to come up the Geronimo plan but realized that there are other things like database-pool etc. to be set up. Can you help? Plz correct me if I am posting in the wrong list. regards peter p -- Thanks, Shiva
[jira] Updated: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma updated GERONIMO-3865: - Attachment: GERONIMO-3865.patch Thanks for pointing this out, a patch for this. unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: YunFeng Ma Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo in year 2008
On Feb 20, 2008, at 5:31 AM, Shiva Kumar H R wrote: On Feb 16, 2008 8:30 AM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Feb 15, 2008 1:30 AM, Shiva Kumar H R [EMAIL PROTECTED] wrote: GEP Task https://issues.apache.org/jira/browse/ GERONIMODEVTOOLS-278 is created for this. We can use this, as well as IRC chats dev-list mails, for collaborating! Please use [EMAIL PROTECTED] for any important stuff around it. I'd be glad to learn a bit about Eclipse plugin development following your conversations. Okey? I have generally found discussions on IRC leading to quicker better understanding of problems. All discussions on #geronimo get logged in http://servlet.uwyn.com/drone/log/bevinbot/geronimo/ mmdd and I typically paste those links into relevant JIRAs. So no discussions are lost. Now duplicating this effort by again posting mails on dev-list would be very time consuming :( Shiva, Duplicating info from IRC onto our dev list may be a bit time consuming for you, but not for the community... Jacek is right. IRC conversations are certainly fast and convenient. However, they aren't read by everyone. People that are not online aren't given a chance to participate. Any significant discussions that occur on IRC should be reitereated on our dev list. Even Jira's are not read by everyone... --kevan
Re: G v2.1 and liferay
The latest problem he has with the plan you provided for him seems to be the following Caused by: org.apache.geronimo.kernel.repository.MissingDependencyException: Missing dependency: org.apache.geronimo.configs/j2ee-security//car I havent looked at the latest liferay geronimo plan (or the one you updated to G v2.1 for him) but he also have to download and install the liferay-portal-geronimo-derby-pool-4.4.1.car to be able continue. regards peter p Shiva Kumar H R wrote: On Feb 19, 2008 1:30 PM, Peter Petersson [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Ever now and then configuration questions about setting up liferay with G is popping up on the user list and soon it is time for G v2.1 to come out of the closet. As it would be great to see a liferay bundle (upgrade) that works out of the box with G v2.1 my question is if anyone of you knows the status of liferays Geronimo 2.1 support or even if someone is helping them out ? As I understand it at least the liferay Geronimo plan needs some revamping. A user on user-list was facing issues with deploying liferay war onto Geronimo. I attempted to come up the Geronimo plan but realized that there are other things like database-pool etc. to be set up. Can you help? Plz correct me if I am posting in the wrong list. regards peter p -- Thanks, Shiva
[BUILD] 2.1: Failed for Revision: 629443
Geronimo Revision: 629443 built with tests included See the full build-0800.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080220/build-0800.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/2.1/20080220/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.pluto:pluto-portal-driver-impl:jar:1.2.0-G601061 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-portal-driver-impl \ -Dversion=1.2.0-G601061 -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.pluto -DartifactId=pluto-portal-driver-impl \ -Dversion=1.2.0-G601061 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.1.1-SNAPSHOT 2) org.apache.pluto:pluto-portal-driver-impl:jar:1.2.0-G601061 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.1.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/2.1/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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.pluto:pluto-portal-driver-impl:jar:1.2.0-G601061 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-portal-driver-impl \ -Dversion=1.2.0-G601061 -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.pluto -DartifactId=pluto-portal-driver-impl \ -Dversion=1.2.0-G601061 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.1.1-SNAPSHOT 2) org.apache.pluto:pluto-portal-driver-impl:jar:1.2.0-G601061 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.1.1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org
Re: Geronimo in year 2008
Alright there is no option left now I guess ;-) -- Thanks, Shiva On Feb 20, 2008 6:34 PM, Kevan Miller [EMAIL PROTECTED] wrote: On Feb 20, 2008, at 5:31 AM, Shiva Kumar H R wrote: On Feb 16, 2008 8:30 AM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Feb 15, 2008 1:30 AM, Shiva Kumar H R [EMAIL PROTECTED] wrote: GEP Task https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-278 is created for this. We can use this, as well as IRC chats dev-list mails, for collaborating! Please use [EMAIL PROTECTED] for any important stuff around it. I'd be glad to learn a bit about Eclipse plugin development following your conversations. Okey? I have generally found discussions on IRC leading to quicker better understanding of problems. All discussions on #geronimo get logged in http://servlet.uwyn.com/drone/log/bevinbot/geronimo/mmdd and I typically paste those links into relevant JIRAs. So no discussions are lost. Now duplicating this effort by again posting mails on dev-list would be very time consuming :( Shiva, Duplicating info from IRC onto our dev list may be a bit time consuming for you, but not for the community... Jacek is right. IRC conversations are certainly fast and convenient. However, they aren't read by everyone. People that are not online aren't given a chance to participate. Any significant discussions that occur on IRC should be reitereated on our dev list. Even Jira's are not read by everyone... --kevan
Re: svn commit: r629312 - in /geronimo/server/branches/2.1: ./ repository/org/apache/pluto/ repository/org/apache/pluto/pluto-container/1.2.0-G601060/ repository/org/apache/pluto/pluto-container/1.2.0
Jay,
It looks like you missed a file
pluto-portal-driver-impl-1.2.0-G601061.jar
Thanks,
Joe
[EMAIL PROTECTED] wrote:
Author: jaydm
Date: Tue Feb 19 17:52:12 2008
New Revision: 629312
URL: http://svn.apache.org/viewvc?rev=629312view=rev
Log:
GERONIMO-3855
Replace pinned copy of Pluto to stop the exception that is being thrown
whenever the admin console is being accessed over https and a two (or more)
page deep portlet is accessed.
Added:
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
geronimo/server/branches/2.1/repository/org/apache/pluto/geronimo-3855.patch
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-container/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-container/1.2.0-G601061/pluto-container-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/pluto-descriptor-api-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/pluto-descriptor-impl-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/pluto-portal-driver-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/pluto-taglib-1.2.0-G601061.jar
(with props)
Removed:
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601060.README.TXT
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-container/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-taglib/1.2.0-G601060/
Modified:
geronimo/server/branches/2.1/pom.xml
Modified: geronimo/server/branches/2.1/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/pom.xml?rev=629312r1=629311r2=629312view=diff
==
--- geronimo/server/branches/2.1/pom.xml (original)
+++ geronimo/server/branches/2.1/pom.xml Tue Feb 19 17:52:12 2008
@@ -97,7 +97,7 @@
axis2Version1.3/axis2Version
axiomVersion1.2.5/axiomVersion
springVersion2.0.5/springVersion
-plutoVersion1.2.0-G601060/plutoVersion
+plutoVersion1.2.0-G601061/plutoVersion
gbeanDeployerBootstraporg.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/${version}/car/gbeanDeployerBootstrap
gbeanDeployerorg.apache.geronimo.framework/geronimo-gbean-deployer/${version}/car/gbeanDeployer
Added:
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
URL:
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT?rev=629312view=auto
==
---
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
(added)
+++
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
Tue Feb 19 17:52:12 2008
@@ -0,0 +1,33 @@
+Private Build of Pluto for Geronimo.
+
+How to build Pluto 1.2.0 (w/ local modification to disable throwing of
PortletSecurityException) for Geronimo:
+
+Checkout pluto 1.2.0
+ svn co -r 601061 https://svn.apache.org/repos/asf/portals/pluto/trunk pluto
+
+svn info for Pluto image:
+Path: .
+URL: http://svn.apache.org/repos/asf/portals/pluto/trunk
+Repository Root: http://svn.apache.org/repos/asf
+Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
+Revision: 601061
+Node Kind: directory
+Schedule: normal
+Last Changed Author: cdoremus
+Last Changed Rev: 586586
+Last Changed Date: 2007-10-19 14:33:58 -0500 (Fri, 19 Oct 2007)
+
+Build pluto
+ cd pluto
+ patch -Np0 -i geronimo-3855.patch
+ mvn install
+
+Copy to appropriate jars and rename into geronimo/repository
+ cd pluto
+ cp pluto-container/target/pluto-container-1.2.0-SNAPSHOT.jar
geronimo-root/repository/org/apache/pluto/pluto-container/1.2.0-G601061/pluto-container-1.2.0-G601061.jar
+ cp
Re: svn commit: r629300 - in /geronimo/server/trunk: ./ repository/org/apache/pluto/ repository/org/apache/pluto/pluto-container/1.2.0-G601060/ repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G
Jay,
It looks like you missed a file
pluto-container-1.2.0-G601061.jar
Thanks,
Joe
[EMAIL PROTECTED] wrote:
Author: jaydm
Date: Tue Feb 19 17:18:26 2008
New Revision: 629300
URL: http://svn.apache.org/viewvc?rev=629300view=rev
Log:
GERONIMO-3855
Replace pinned copy of Pluto to stop the exception that is being thrown
whenever the admin console is being accessed over https and a two (or more)
page deep portlet is accessed.
Added:
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT
- copied, changed from r629193,
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT
geronimo/server/trunk/repository/org/apache/pluto/geronimo-3855.patch
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/pluto-descriptor-api-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/pluto-descriptor-impl-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601061/pluto-portal-driver-impl-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/pluto-portal-driver-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/pluto-taglib-1.2.0-G601061.jar
(with props)
Removed:
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT
geronimo/server/trunk/repository/org/apache/pluto/pluto-container/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-taglib/1.2.0-G601060/
Modified:
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=629300r1=629299r2=629300view=diff
==
--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Tue Feb 19 17:18:26 2008
@@ -97,7 +97,7 @@
axis2Version1.3/axis2Version
axiomVersion1.2.5/axiomVersion
springVersion2.0.5/springVersion
-plutoVersion1.2.0-G601060/plutoVersion
+plutoVersion1.2.0-G601061/plutoVersion
gbeanDeployerBootstraporg.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/${version}/car/gbeanDeployerBootstrap
gbeanDeployerorg.apache.geronimo.framework/geronimo-gbean-deployer/${version}/car/gbeanDeployer
Copied:
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT
(from r629193,
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT)
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT?p2=geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXTp1=geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXTr1=629193r2=629300rev=629300view=diff
==
--- geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT
(original)
+++ geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT
Tue Feb 19 17:18:26 2008
@@ -1,34 +1,33 @@
Private Build of Pluto for Geronimo.
-How to build Pluto 1.2.0 (no local modification) for Geronimo:
+How to build Pluto 1.2.0 (w/ local modification to disable throwing of
PortletSecurityException) for Geronimo:
Checkout pluto 1.2.0
- svn co https://svn.apache.org/repos/asf/portals/pluto/trunk pluto
+ svn co -r 601061 https://svn.apache.org/repos/asf/portals/pluto/trunk pluto
svn info for Pluto image:
Path: .
-URL: https://svn.apache.org/repos/asf/portals/pluto/trunk
-Repository Root: https://svn.apache.org/repos/asf
+URL: http://svn.apache.org/repos/asf/portals/pluto/trunk
+Repository Root: http://svn.apache.org/repos/asf
Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
-Revision: 601060
+Revision: 601061
Node Kind: directory
Schedule: normal
Last Changed Author: cdoremus
Last Changed Rev: 586586
-Last
[BUILD] 2.2: Failed for Revision: 629462
Geronimo Revision: 629462 built with tests included See the full build-0900.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080220/build-0900.log See the unit test reports at http://geronimo.apache.org/maven/server/binaries/trunk/20080220/unit-test-reports apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.pluto:pluto-container:jar:1.2.0-G601061 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -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.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) org.apache.pluto:pluto-container:jar:1.2.0-G601061 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/), module-local (file:///home/geronimo/geronimo/trunk/repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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.pluto:pluto-container:jar:1.2.0-G601061 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -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.pluto -DartifactId=pluto-container \ -Dversion=1.2.0-G601061 -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo:repository:jar:2.2-SNAPSHOT 2) org.apache.pluto:pluto-container:jar:1.2.0-G601061 -- 1 required artifact is missing. for artifact: org.apache.geronimo:repository:jar:2.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), java.net (http://download.java.net/maven/1/), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating
Re: svn commit: r629312 - in /geronimo/server/branches/2.1: ./ repository/org/apache/pluto/ repository/org/apache/pluto/pluto-container/1.2.0-G601060/ repository/org/apache/pluto/pluto-container/1.2.0
Thanks Joe,
Hopefully I got them all now.
Jay
Joe Bohn wrote:
Jay,
It looks like you missed a file
pluto-portal-driver-impl-1.2.0-G601061.jar
Thanks,
Joe
[EMAIL PROTECTED] wrote:
Author: jaydm
Date: Tue Feb 19 17:52:12 2008
New Revision: 629312
URL: http://svn.apache.org/viewvc?rev=629312view=rev
Log:
GERONIMO-3855
Replace pinned copy of Pluto to stop the exception that is being thrown
whenever the admin console is being accessed over https and a two (or
more)
page deep portlet is accessed.
Added:
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
geronimo/server/branches/2.1/repository/org/apache/pluto/geronimo-3855.patch
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-container/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-container/1.2.0-G601061/pluto-container-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/pluto-descriptor-api-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/pluto-descriptor-impl-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/pluto-portal-driver-1.2.0-G601061.jar
(with props)
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/pluto-taglib-1.2.0-G601061.jar
(with props)
Removed:
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601060.README.TXT
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-container/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601060/
geronimo/server/branches/2.1/repository/org/apache/pluto/pluto-taglib/1.2.0-G601060/
Modified:
geronimo/server/branches/2.1/pom.xml
Modified: geronimo/server/branches/2.1/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/pom.xml?rev=629312r1=629311r2=629312view=diff
==
--- geronimo/server/branches/2.1/pom.xml (original)
+++ geronimo/server/branches/2.1/pom.xml Tue Feb 19 17:52:12 2008
@@ -97,7 +97,7 @@
axis2Version1.3/axis2Version
axiomVersion1.2.5/axiomVersion
springVersion2.0.5/springVersion
-plutoVersion1.2.0-G601060/plutoVersion
+plutoVersion1.2.0-G601061/plutoVersion
gbeanDeployerBootstraporg.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/${version}/car/gbeanDeployerBootstrap
gbeanDeployerorg.apache.geronimo.framework/geronimo-gbean-deployer/${version}/car/gbeanDeployer
Added:
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
URL:
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT?rev=629312view=auto
==
---
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
(added)
+++
geronimo/server/branches/2.1/repository/org/apache/pluto/1.2.0-G601061.README.TXT
Tue Feb 19 17:52:12 2008
@@ -0,0 +1,33 @@
+Private Build of Pluto for
Geronimo. +
+How to build Pluto 1.2.0 (w/ local modification to disable throwing
of PortletSecurityException) for Geronimo:
+
+Checkout pluto 1.2.0
+ svn co -r 601061
https://svn.apache.org/repos/asf/portals/pluto/trunk pluto
+
+svn info for Pluto image:
+Path: .
+URL: http://svn.apache.org/repos/asf/portals/pluto/trunk
+Repository Root: http://svn.apache.org/repos/asf
+Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
+Revision: 601061
+Node Kind: directory
+Schedule: normal
+Last Changed Author: cdoremus
+Last Changed Rev: 586586
+Last Changed Date: 2007-10-19 14:33:58 -0500 (Fri, 19 Oct 2007)
+
+Build pluto
+ cd pluto
+ patch -Np0 -i geronimo-3855.patch
+ mvn install
+
+Copy to appropriate jars and rename into geronimo/repository
+ cd pluto
+ cp
pluto-container/target/pluto-container-1.2.0-SNAPSHOT.jar
Re: svn commit: r629300 - in /geronimo/server/trunk: ./ repository/org/apache/pluto/ repository/org/apache/pluto/pluto-container/1.2.0-G601060/ repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G
Thanks Joe,
Hopefully I got them all now.
Jay
Joe Bohn wrote:
Jay,
It looks like you missed a file
pluto-container-1.2.0-G601061.jar
Thanks,
Joe
[EMAIL PROTECTED] wrote:
Author: jaydm
Date: Tue Feb 19 17:18:26 2008
New Revision: 629300
URL: http://svn.apache.org/viewvc?rev=629300view=rev
Log:
GERONIMO-3855
Replace pinned copy of Pluto to stop the exception that is being thrown
whenever the admin console is being accessed over https and a two (or
more)
page deep portlet is accessed.
Added:
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT
- copied, changed from r629193,
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT
geronimo/server/trunk/repository/org/apache/pluto/geronimo-3855.patch
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601061/pluto-descriptor-api-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601061/pluto-descriptor-impl-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601061/pluto-portal-driver-impl-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601061/pluto-portal-driver-1.2.0-G601061.jar
(with props)
geronimo/server/trunk/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/
geronimo/server/trunk/repository/org/apache/pluto/pluto-taglib/1.2.0-G601061/pluto-taglib-1.2.0-G601061.jar
(with props)
Removed:
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT
geronimo/server/trunk/repository/org/apache/pluto/pluto-container/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-api/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-descriptor-impl/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver-impl/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-portal-driver/1.2.0-G601060/
geronimo/server/trunk/repository/org/apache/pluto/pluto-taglib/1.2.0-G601060/
Modified:
geronimo/server/trunk/pom.xml
Modified: geronimo/server/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=629300r1=629299r2=629300view=diff
==
--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Tue Feb 19 17:18:26 2008
@@ -97,7 +97,7 @@
axis2Version1.3/axis2Version
axiomVersion1.2.5/axiomVersion
springVersion2.0.5/springVersion
-plutoVersion1.2.0-G601060/plutoVersion
+plutoVersion1.2.0-G601061/plutoVersion
gbeanDeployerBootstraporg.apache.geronimo.framework/geronimo-gbean-deployer-bootstrap/${version}/car/gbeanDeployerBootstrap
gbeanDeployerorg.apache.geronimo.framework/geronimo-gbean-deployer/${version}/car/gbeanDeployer
Copied:
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT
(from r629193,
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT)
URL:
http://svn.apache.org/viewvc/geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT?p2=geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXTp1=geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXTr1=629193r2=629300rev=629300view=diff
==
---
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601060.README.TXT
(original)
+++
geronimo/server/trunk/repository/org/apache/pluto/1.2.0-G601061.README.TXT
Tue Feb 19 17:18:26 2008
@@ -1,34 +1,33 @@
Private Build of Pluto for
Geronimo.
-How to build Pluto 1.2.0 (no local modification) for Geronimo:
+How to build Pluto 1.2.0 (w/ local modification to disable throwing
of PortletSecurityException) for Geronimo:
Checkout pluto 1.2.0
- svn co https://svn.apache.org/repos/asf/portals/pluto/trunk pluto
+ svn co -r 601061
https://svn.apache.org/repos/asf/portals/pluto/trunk pluto
svn info for Pluto image:
Path: .
-URL: https://svn.apache.org/repos/asf/portals/pluto/trunk
-Repository Root: https://svn.apache.org/repos/asf
+URL: http://svn.apache.org/repos/asf/portals/pluto/trunk
+Repository Root: http://svn.apache.org/repos/asf
Repository UUID:
[jira] Assigned: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3865: - Assignee: Jarek Gawor (was: YunFeng Ma) unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3865. --- Resolution: Fixed Fix Version/s: 2.2 2.1.1 Committed the patch to trunk (revision 629507) and branches/2.1 (revision 629524). Thanks a lot! unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
TCK Dog
I've been the TCK Dog for about a year now, through 2.0, 2.0.1, 2.0.2 and most recently 2.1. I think it's time for a change. This activity primarily involves: 1) Building the images and accounting for changes in the various branches that require comparable changes in the test harness. 2) Applying updated Sun patches, exclude lists, etc... as necessary (this was a bigger issue when we were initially getting certified for Java EE 5 but has since dropped off. I expect it will pick up again with Java EE 6 in the future). 3) Running tests as necessary for various releases, projects, components, specs, etc... 4) Monitoring/advertising test results 5) Fixing problems in either the harness, test plans, and/or Geronimo code as necessary. 6) Working with other teams that sometimes rely on the Geronimo TCK validation (such as OpenEJB and MyFaces) 7) Summarizing results and criteria for Sun Certification We've discussed automating some of these activities in the past (such as running tests with GBuild). However, I don't believe that is working at the moment so it's pretty much a manual effort. Fortunately we now have automated Geronimo Builds and a limited number of tck tests to highlight pervasive problems. We've also had terrific involvement from the whole team in resolving tck failure issues (thank you to all those that monitor and respond to the TCK list :-) ). With 2.1.1 coming up it would be a great time for some new blood to get involved. Joe
[jira] Resolved: (GERONIMO-3859) Provide toString method to StartupMonitorUtil to aid monitoring, logging, debugging
[ https://issues.apache.org/jira/browse/GERONIMO-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-3859. --- Resolution: Fixed Fix Version/s: 2.2 2.1.1 Committed the patch to trunk (revision 629529) and branches/2.1 (revision 629529). Thanks! Provide toString method to StartupMonitorUtil to aid monitoring, logging, debugging --- Key: GERONIMO-3859 URL: https://issues.apache.org/jira/browse/GERONIMO-3859 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Affects Versions: 2.1, 2.1.1, 2.2 Environment: All Java platforms Reporter: Dan Becker Assignee: Jarek Gawor Priority: Minor Fix For: 2.1.1, 2.2 Attachments: Geronimo-3859.patch Original Estimate: 24h Remaining Estimate: 24h Provide toString method to StartupMonitorUtil$AddressHolder class to aid monitoring, logging, and debugging. Currently, a println on this class with no toString method produces this kind of output: port 0: [EMAIL PROTECTED] port 1: [EMAIL PROTECTED] port 2: [EMAIL PROTECTED] port 3: [EMAIL PROTECTED] By adding a toString method, any printlns, logging, or debugging will produce this kind of output: port 0: AddressHolder: name=Derby Connector, address=/0.0.0.0:0. port 1: AddressHolder: name=CORBA Naming Service, address=localhost/127.0.0.1:1050. port 2: AddressHolder: name=RMI Naming, address=/0.0.0.0:1099. port 3: AddressHolder: name=OpenEJB ORB Adapter, address=localhost/127.0.0.1:2001. The second method is much more informative, user-friendly, and requires less clicks to see the information in a debugger. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-3859) Provide toString method to StartupMonitorUtil to aid monitoring, logging, debugging
[ https://issues.apache.org/jira/browse/GERONIMO-3859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-3859: - Assignee: Jarek Gawor Provide toString method to StartupMonitorUtil to aid monitoring, logging, debugging --- Key: GERONIMO-3859 URL: https://issues.apache.org/jira/browse/GERONIMO-3859 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Affects Versions: 2.1, 2.1.1, 2.2 Environment: All Java platforms Reporter: Dan Becker Assignee: Jarek Gawor Priority: Minor Fix For: 2.1.1, 2.2 Attachments: Geronimo-3859.patch Original Estimate: 24h Remaining Estimate: 24h Provide toString method to StartupMonitorUtil$AddressHolder class to aid monitoring, logging, and debugging. Currently, a println on this class with no toString method produces this kind of output: port 0: [EMAIL PROTECTED] port 1: [EMAIL PROTECTED] port 2: [EMAIL PROTECTED] port 3: [EMAIL PROTECTED] By adding a toString method, any printlns, logging, or debugging will produce this kind of output: port 0: AddressHolder: name=Derby Connector, address=/0.0.0.0:0. port 1: AddressHolder: name=CORBA Naming Service, address=localhost/127.0.0.1:1050. port 2: AddressHolder: name=RMI Naming, address=/0.0.0.0:1099. port 3: AddressHolder: name=OpenEJB ORB Adapter, address=localhost/127.0.0.1:2001. The second method is much more informative, user-friendly, and requires less clicks to see the information in a debugger. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3780) MDB unable to access JNDI in ejbPostCreate
[
https://issues.apache.org/jira/browse/GERONIMO-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570780#action_12570780
]
Jarek Gawor commented on GERONIMO-3780:
---
If I'm understanding the code correctly, there is a chance with this patch
where the notifyAll() is called before another thread enters wait() and
therefore that thread will block until another notifyAll() is called.
Assume thread A gets suspended just before executing
deploymentInfo.set(EjbDeployment.class, this); line and thread B gets
suspended right after executing if (deploymentInfo.get(EjbDeployment.class) ==
null ){ line. Now, A gets awaken and it finishes executing the start() method
(and notifyAll() is called) then thread B awakens and continues executing and
it enters the wait() method. Since notifyAll() was already called, thread B
will just block until some other thread calls notifyAll() (which might not
happen for a while or at all).
MDB unable to access JNDI in ejbPostCreate
--
Key: GERONIMO-3780
URL: https://issues.apache.org/jira/browse/GERONIMO-3780
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: OpenEJB
Affects Versions: 2.1
Environment: All
Reporter: Manu T George
Attachments: G3780-r628632.patch
An MDB is unable to access JNDI in ejbPostCreate if there are messages in the
queue to which it is listening during server startup, say after a server
crash
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: TCK Dog
I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Jay Joe Bohn wrote: I've been the TCK Dog for about a year now, through 2.0, 2.0.1, 2.0.2 and most recently 2.1. I think it's time for a change. This activity primarily involves: 1) Building the images and accounting for changes in the various branches that require comparable changes in the test harness. 2) Applying updated Sun patches, exclude lists, etc... as necessary (this was a bigger issue when we were initially getting certified for Java EE 5 but has since dropped off. I expect it will pick up again with Java EE 6 in the future). 3) Running tests as necessary for various releases, projects, components, specs, etc... 4) Monitoring/advertising test results 5) Fixing problems in either the harness, test plans, and/or Geronimo code as necessary. 6) Working with other teams that sometimes rely on the Geronimo TCK validation (such as OpenEJB and MyFaces) 7) Summarizing results and criteria for Sun Certification We've discussed automating some of these activities in the past (such as running tests with GBuild). However, I don't believe that is working at the moment so it's pretty much a manual effort. Fortunately we now have automated Geronimo Builds and a limited number of tck tests to highlight pervasive problems. We've also had terrific involvement from the whole team in resolving tck failure issues (thank you to all those that monitor and respond to the TCK list :-) ). With 2.1.1 coming up it would be a great time for some new blood to get involved. Joe
Re: TCK Dog
I'd be glad to help you transition ... maybe even eager, enthusiastic, exuberant :-) ! Thanks Jay! Joe Jay D. McHugh wrote: I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Jay Joe Bohn wrote: I've been the TCK Dog for about a year now, through 2.0, 2.0.1, 2.0.2 and most recently 2.1. I think it's time for a change. This activity primarily involves: 1) Building the images and accounting for changes in the various branches that require comparable changes in the test harness. 2) Applying updated Sun patches, exclude lists, etc... as necessary (this was a bigger issue when we were initially getting certified for Java EE 5 but has since dropped off. I expect it will pick up again with Java EE 6 in the future). 3) Running tests as necessary for various releases, projects, components, specs, etc... 4) Monitoring/advertising test results 5) Fixing problems in either the harness, test plans, and/or Geronimo code as necessary. 6) Working with other teams that sometimes rely on the Geronimo TCK validation (such as OpenEJB and MyFaces) 7) Summarizing results and criteria for Sun Certification We've discussed automating some of these activities in the past (such as running tests with GBuild). However, I don't believe that is working at the moment so it's pretty much a manual effort. Fortunately we now have automated Geronimo Builds and a limited number of tck tests to highlight pervasive problems. We've also had terrific involvement from the whole team in resolving tck failure issues (thank you to all those that monitor and respond to the TCK list :-) ). With 2.1.1 coming up it would be a great time for some new blood to get involved. Joe
module builders/deployers in plugins
I have a couple of questions about module builders/deployers and plugin support in Geronimo: 1) I have a plugin that contains a NamingBuilder. Once I install this plugin, that NamingBuilder will not be called during module deployment until I 'register' it with the NamingBuilders gbean (e.g. in plugins/j2ee/j2ee-deployer/src/main/plan/plan.xml or config.xml). The questions is, can we make this more dynamic? It would be great just to install the plugin and have the NamingBuilder to be invoked automatically without any additional configuration steps. 2) The AdminObjectRefBuilder is always trying to process _all_ resource-env-ref entries (AdminObjectRefBuilder is just an example in this case). However, as things evolve (Java EE 5 - 6) and new resource env. types are added, it does not scale to keep updating the AdminObjectRefBuilder to handle these new types. So I think it would be nice to install a new builder that would handle these new types only. But that would require communicating with the AdminObjectRefBuilder and somehow telling it to ignore the new types. The question is, what would be the best way of doing it? Or maybe we need a different way of processing the DDs? Jarek
Re: Release Roller plugin soon?
David Jencks wrote: On Feb 16, 2008, at 9:51 AM, Peter Petersson wrote: David Jencks wrote: Now that 2.1 is released (I think :-) I'd like to move toward releasing the Roller plugin pretty soon. The major obstacle I know of is that the source of the roller war used as input is rather mysterious and is certainly not released by roller. I can build it locally but I've forgotten what roller modifications if any are in it. You are right about that ;). If you chose the local build strategy, checking out the roller 4.0 tag and use ant mvn-install (also before first time build ant mvn-get) should build and install the roller artifacs. My impression is that this should produce the same stuff as is released by the roller teem as mvn-install depends on build and I cant find any other ant release related sections but maybe the actuall release is done some other way (?). No extra patches should be needed every necessary patch we provided and wanted to get in for the plugin to work smoothly has been included by the roller teem before the svn branching to 4.1. I'm not exactly happy with the idea but think the most practical solution is to check any necessary roller patch and the built war into svn. I don't know if we could convince the roller project to release maven-compatible artifacts in a reasonable amount of time. There is a mvn-deploy section in the roller projects ant build.xml file but I don't know if anybody has pulled the trigger ;) but releasing artifacts may not be that far away. But as you say a more practical solution is probably to add the war by setting up a extra roller-war-mvn-install section in the roller plugin code base that puts the war in your local maven repos. Another possible improvement is to remove the jars from WEB-INF/lib and put them into our repository. This would greatly reduce the size of the war we'd have to keep in svn. In the long run, if we cant convince the roller teem to pick up maven which dosen't seem likely, this would be something to consider although during my work on a maven build system for roller I found that 4 of the roller used lib jars is not present in maven, but that may have changed. One way to accomplish this would be to pick up and maintain the maven build patch for roller but maybe that would be to go over the river for water. It might be worth it :-) after spending some time working on a roller security refactoring I remember so many of the reasons I don't like ant :-) I've confirmed that we don't need additional roller patches with the current plugin to get something installable. I've also played around with a no-libs roller without anything in its WEB-INF/lib, all these jars being dependencies in the geronimo repo. See the GERONIMO-2994-nolibs.patch and GERONIMO-2994-roller-patch patches. These seem to work fine (only tried jetty so far) but introduce the question of how to make the 4-5 unpublished jars and roller jars available to someone who wants to download and install the plugin. Maybe I can cook up a way to get just these jars into the WEB-INF/lib. One of the jars, commons-id-1.0-SNAPSHOT has never been released in any form whatsoever, so I kinda wonder about including it in any apache projects. Great! I hope to get some time this weekend to do some testing on the patches. Taking a quick peek at the nolibs patch I notice it uses G:s openjpa and I have a faint memory of there being a issue that prevents roller from using anything jpa newer than 0.9.7 or .8 so there may be some problem lurking inside ;-). On the none maven jars topic, commons-id at least the project has some sporadic activity see http://commons.apache.org/sandbox/id/. What surprise me a bit is that, although widely used, none of the rome jars is found in a public maven repo, although the rome stuff is clearly built with maven see http://wiki.java.net/bin/view/Javawsxml/HowToBuild Another idea I had before releasing this is to try to get logging working. So far everything I've tried has not allowed any logging from roller in any form I can find. Anyone have any ideas? Have you looked in jetty's log? I don't know way I haven't mentioned this but at least logging is somehow working using roller on tomcat but roller seem to hijack parts of the logging and place it in catalina/logs/roller.log. Looks like this INFO 2008-02-20 19:38:20,977 GeronimoLog:info - SUCCESS: Got parameters. Using configuration type JNDI_NAME INFO 2008-02-20 19:38:20,979 GeronimoLog:info - -- Using JNDI datasource name: java:comp/env/jdbc/rollerdb INFO 2008-02-20 19:38:20,981 GeronimoLog:info - SUCCESS: located JNDI DataSource [java:comp/env/jdbc/rollerdb] WARN 2008-02-20 19:38:23,336 GeronimoLog:warn - Failed to setup mail provider, continuing anways. Does anyone else want improvements before we release? If the how to build section in the readme file is not enough I would vote for including the war as is in a
Re: Geronimo in year 2008
On Feb 20, 2008 5:35 AM, Shiva Kumar H R [EMAIL PROTECTED] wrote: Alright there is no option left now I guess ;-) No and thanks for your understanding. I'm pretty certain people would appreciate it (I will certainly). Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: Release Roller plugin soon?
I found where jpa 1.0 was mentioned not to work with roller take a look at the Roller 4.0 RC8 on Geronimo 2.0.2 - tread in rollers dev list (Daves replay to fp). Apparently you will be able to set up the derby db but you will get a Foreign-Key-Vailolation wile creating a new weblog, but maybe this issue have been fixed. regards peter petersson Peter Petersson wrote: David Jencks wrote: On Feb 16, 2008, at 9:51 AM, Peter Petersson wrote: David Jencks wrote: Now that 2.1 is released (I think :-) I'd like to move toward releasing the Roller plugin pretty soon. The major obstacle I know of is that the source of the roller war used as input is rather mysterious and is certainly not released by roller. I can build it locally but I've forgotten what roller modifications if any are in it. You are right about that ;). If you chose the local build strategy, checking out the roller 4.0 tag and use ant mvn-install (also before first time build ant mvn-get) should build and install the roller artifacs. My impression is that this should produce the same stuff as is released by the roller teem as mvn-install depends on build and I cant find any other ant release related sections but maybe the actuall release is done some other way (?). No extra patches should be needed every necessary patch we provided and wanted to get in for the plugin to work smoothly has been included by the roller teem before the svn branching to 4.1. I'm not exactly happy with the idea but think the most practical solution is to check any necessary roller patch and the built war into svn. I don't know if we could convince the roller project to release maven-compatible artifacts in a reasonable amount of time. There is a mvn-deploy section in the roller projects ant build.xml file but I don't know if anybody has pulled the trigger ;) but releasing artifacts may not be that far away. But as you say a more practical solution is probably to add the war by setting up a extra roller-war-mvn-install section in the roller plugin code base that puts the war in your local maven repos. Another possible improvement is to remove the jars from WEB-INF/lib and put them into our repository. This would greatly reduce the size of the war we'd have to keep in svn. In the long run, if we cant convince the roller teem to pick up maven which dosen't seem likely, this would be something to consider although during my work on a maven build system for roller I found that 4 of the roller used lib jars is not present in maven, but that may have changed. One way to accomplish this would be to pick up and maintain the maven build patch for roller but maybe that would be to go over the river for water. It might be worth it :-) after spending some time working on a roller security refactoring I remember so many of the reasons I don't like ant :-) I've confirmed that we don't need additional roller patches with the current plugin to get something installable. I've also played around with a no-libs roller without anything in its WEB-INF/lib, all these jars being dependencies in the geronimo repo. See the GERONIMO-2994-nolibs.patch and GERONIMO-2994-roller-patch patches. These seem to work fine (only tried jetty so far) but introduce the question of how to make the 4-5 unpublished jars and roller jars available to someone who wants to download and install the plugin. Maybe I can cook up a way to get just these jars into the WEB-INF/lib. One of the jars, commons-id-1.0-SNAPSHOT has never been released in any form whatsoever, so I kinda wonder about including it in any apache projects. Great! I hope to get some time this weekend to do some testing on the patches. Taking a quick peek at the nolibs patch I notice it uses G:s openjpa and I have a faint memory of there being a issue that prevents roller from using anything jpa newer than 0.9.7 or .8 so there may be some problem lurking inside ;-). On the none maven jars topic, commons-id at least the project has some sporadic activity see http://commons.apache.org/sandbox/id/. What surprise me a bit is that, although widely used, none of the rome jars is found in a public maven repo, although the rome stuff is clearly built with maven see http://wiki.java.net/bin/view/Javawsxml/HowToBuild Another idea I had before releasing this is to try to get logging working. So far everything I've tried has not allowed any logging from roller in any form I can find. Anyone have any ideas? Have you looked in jetty's log? I don't know way I haven't mentioned this but at least logging is somehow working using roller on tomcat but roller seem to hijack parts of the logging and place it in catalina/logs/roller.log. Looks like this INFO 2008-02-20 19:38:20,977 GeronimoLog:info - SUCCESS: Got parameters. Using configuration type JNDI_NAME INFO 2008-02-20 19:38:20,979 GeronimoLog:info - -- Using JNDI datasource name: java:comp/env/jdbc/rollerdb INFO
Re: G v2.1 and liferay
Peter Petersson wrote: The latest problem he has with the plan you provided for him seems to be the following Caused by: org.apache.geronimo.kernel.repository.MissingDependencyException: Missing dependency: org.apache.geronimo.configs/j2ee-security//car I havent looked at the latest liferay geronimo plan (or the one you updated to G v2.1 for him) but he also have to download and install the liferay-portal-geronimo-derby-pool-4.4.1.car to be able continue. regards peter p Before mentioning the liferay derby pool car to the user maybe you or someone else that have knowledge of security configuration changes in G between v2.0 and v2.1 can help tweak the plan? see the Geronimo v2.1 Plan Creator = Deploy Liferay 4.1.1 - thread in the user list. regards peter petersson Shiva Kumar H R wrote: On Feb 19, 2008 1:30 PM, Peter Petersson [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi Ever now and then configuration questions about setting up liferay with G is popping up on the user list and soon it is time for G v2.1 to come out of the closet. As it would be great to see a liferay bundle (upgrade) that works out of the box with G v2.1 my question is if anyone of you knows the status of liferays Geronimo 2.1 support or even if someone is helping them out ? As I understand it at least the liferay Geronimo plan needs some revamping. A user on user-list was facing issues with deploying liferay war onto Geronimo. I attempted to come up the Geronimo plan but realized that there are other things like database-pool etc. to be set up. Can you help? Plz correct me if I am posting in the wrong list. regards peter p -- Thanks, Shiva
[jira] Created: (GERONIMODEVTOOLS-288) Errors when deploying webservice from GEP 2.1.0 to Geronimo server
Errors when deploying webservice from GEP 2.1.0 to Geronimo server -- Key: GERONIMODEVTOOLS-288 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-288 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.0 Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.1.0 Stacktrace below: Geronimo Application Server started 15:00:37,528 ERROR [EngineConfigurationFactoryServlet] Unable to find config file. Creating new servlet engine config file: /WEB-INF/server-config.wsdd 15:00:39,137 ERROR [WarBasedAxisConfigurator] org/apache/commons/fileupload/FileUploadException org.apache.axis2.deployment.DeploymentException: org/apache/commons/fileupload/FileUploadException at org.apache.axis2.deployment.AxisConfigBuilder.processMessageBuilders(AxisConfigBuilder.java:623) at org.apache.axis2.deployment.AxisConfigBuilder.populateConfig(AxisConfigBuilder.java:186) at org.apache.axis2.deployment.DeploymentEngine.populateAxisConfiguration(DeploymentEngine.java:615) at org.apache.axis2.deployment.WarBasedAxisConfigurator.init(WarBasedAxisConfigurator.java:146) at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:500) at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:420) at org.apache.axis2.transport.http.AxisAdminServlet.init(AxisAdminServlet.java:54) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1053) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:955) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4038) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4341) at org.apache.geronimo.tomcat.GeronimoStandardContext.access$201(GeronimoStandardContext.java:60) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:388) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.GeronimoStandardContext.start(GeronimoStandardContext.java:241) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.geronimo.tomcat.TomcatContainer.addContext(TomcatContainer.java:359) at org.apache.geronimo.tomcat.TomcatWebAppContext.doStart(TomcatWebAppContext.java:512) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:998) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:541) at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111) at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146) at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.fireRunningEvent(BasicLifecycleMonitor.java:176) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor.access$300(BasicLifecycleMonitor.java:44) at org.apache.geronimo.kernel.basic.BasicLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(BasicLifecycleMonitor.java:254) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:294) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:555) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:456) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:493) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:534) at
Re: Release Roller plugin soon?
I haven't found any problems using openjpa 1.0 against roller trunk. I'll try again with the released roller 4.0 soon. If I remove roller's log4j.properties file and override a couple properties in our roller-custom.properties file then logging starts working. I'm wondering if there's a way to keep log4j from jumping on the latest bandwagon whenever you deploy a new app that has the misguided idea that it owns the universe thanks david jencks - Original Message From: Peter Petersson [EMAIL PROTECTED] To: dev@geronimo.apache.org Sent: Wednesday, February 20, 2008 12:49:42 PM Subject: Re: Release Roller plugin soon? I found where jpa 1.0 was mentioned not to work with roller take a look at the Roller 4.0 RC8 on Geronimo 2.0.2 - tread in rollers dev list (Daves replay to fp). Apparently you will be able to set up the derby db but you will get a Foreign-Key-Vailolation wile creating a new weblog, but maybe this issue have been fixed. regards peter petersson Peter Petersson wrote: David Jencks wrote: On Feb 16, 2008, at 9:51 AM, Peter Petersson wrote: David Jencks wrote: Now that 2.1 is released (I think :-) I'd like to move toward releasing the Roller plugin pretty soon. The major obstacle I know of is that the source of the roller war used as input is rather mysterious and is certainly not released by roller. I can build it locally but I've forgotten what roller modifications if any are in it. You are right about that ;). If you chose the local build strategy, checking out the roller 4.0 tag and use ant mvn-install (also before first time build ant mvn-get) should build and install the roller artifacs. My impression is that this should produce the same stuff as is released by the roller teem as mvn-install depends on build and I cant find any other ant release related sections but maybe the actuall release is done some other way (?). No extra patches should be needed every necessary patch we provided and wanted to get in for the plugin to work smoothly has been included by the roller teem before the svn branching to 4.1. I'm not exactly happy with the idea but think the most practical solution is to check any necessary roller patch and the built war into svn. I don't know if we could convince the roller project to release maven-compatible artifacts in a reasonable amount of time. There is a mvn-deploy section in the roller projects ant build.xml file but I don't know if anybody has pulled the trigger ;) but releasing artifacts may not be that far away. But as you say a more practical solution is probably to add the war by setting up a extra roller-war-mvn-install section in the roller plugin code base that puts the war in your local maven repos. Another possible improvement is to remove the jars from WEB-INF/lib and put them into our repository. This would greatly reduce the size of the war we'd have to keep in svn. In the long run, if we cant convince the roller teem to pick up maven which dosen't seem likely, this would be something to consider although during my work on a maven build system for roller I found that 4 of the roller used lib jars is not present in maven, but that may have changed. One way to accomplish this would be to pick up and maintain the maven build patch for roller but maybe that would be to go over the river for water. It might be worth it :-) after spending some time working on a roller security refactoring I remember so many of the reasons I don't like ant :-) I've confirmed that we don't need additional roller patches with the current plugin to get something installable. I've also played around with a no-libs roller without anything in its WEB-INF/lib, all these jars being dependencies in the geronimo repo. See the GERONIMO-2994-nolibs.patch and GERONIMO-2994-roller-patch patches. These seem to work fine (only tried jetty so far) but introduce the question of how to make the 4-5 unpublished jars and roller jars available to someone who wants to download and install the plugin. Maybe I can cook up a way to get just these jars into the WEB-INF/lib. One of the jars, commons-id-1.0-SNAPSHOT has never been released in any form whatsoever, so I kinda wonder about including it in any apache projects. Great! I hope to
[jira] Created: (GERONIMO-3866) Export Plugin from web console contains empty, non-editiable 'Unique ID field
Export Plugin from web console contains empty, non-editiable 'Unique ID field -- Key: GERONIMO-3866 URL: https://issues.apache.org/jira/browse/GERONIMO-3866 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn When attempting to export a plugin the UI appears to present a screen that, among other things, should contain a Unique ID that was created based upon the component information. However, there is no input or display field included in the presented UI ... just the tag of Unique ID: and nothing else. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3867) Export Plugin in Web Console results in NullPointerException
Export Plugin in Web Console results in NullPointerException - Key: GERONIMO-3867 URL: https://issues.apache.org/jira/browse/GERONIMO-3867 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.1 Reporter: Joe Bohn Assignee: Joe Bohn When attempting to export a component as a plugin in the web console, a second screen is presented after the initial component is selected. It is at this point in time that a NullPointerException appears in the command console. 16:19:37,170 ERROR [MultiPagePortlet] Unable to render portlet java.lang.NullPointerException at org.apache.geronimo.console.car.ExportConfigHandler.renderView(ExportConfigHandler.java:71) at org.apache.geronimo.console.MultiPagePortlet.doView(MultiPagePortlet.java:144) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) at org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101) at org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173) at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152) at jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:87) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:557) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:481) at org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968) at jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:196) at jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:101) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:445) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292) at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:142) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at
Re: Release Roller plugin soon?
David Jencks wrote: I haven't found any problems using openjpa 1.0 against roller trunk. I'll try again with the released roller 4.0 soon. If I remove roller's log4j.properties file and override a couple properties in our roller-custom.properties file then logging starts working. I'm wondering if there's a way to keep log4j from jumping on the latest bandwagon whenever you deploy a new app that has the misguided idea that it owns the universe lol, beats me, but good to hear you found a way around it, btw the following contains a link to issues fixed in roller v4.0.1 http://cwiki.apache.org/confluence/display/ROLLER/February+2008+Board+Report regards peter petersson thanks david jencks - Original Message From: Peter Petersson [EMAIL PROTECTED] To: dev@geronimo.apache.org Sent: Wednesday, February 20, 2008 12:49:42 PM Subject: Re: Release Roller plugin soon? I found where jpa 1.0 was mentioned not to work with roller take a look at the Roller 4.0 RC8 on Geronimo 2.0.2 - tread in rollers dev list (Daves replay to fp). Apparently you will be able to set up the derby db but you will get a Foreign-Key-Vailolation wile creating a new weblog, but maybe this issue have been fixed. regards peter petersson Peter Petersson wrote: David Jencks wrote: On Feb 16, 2008, at 9:51 AM, Peter Petersson wrote: David Jencks wrote: Now that 2.1 is released (I think :-) I'd like to move toward releasing the Roller plugin pretty soon. The major obstacle I know of is that the source of the roller war used as input is rather mysterious and is certainly not released by roller. I can build it locally but I've forgotten what roller modifications if any are in it. You are right about that ;). If you chose the local build strategy, checking out the roller 4.0 tag and use ant mvn-install (also before first time build ant mvn-get) should build and install the roller artifacs. My impression is that this should produce the same stuff as is released by the roller teem as mvn-install depends on build and I cant find any other ant release related sections but maybe the actuall release is done some other way (?). No extra patches should be needed every necessary patch we provided and wanted to get in for the plugin to work smoothly has been included by the roller teem before the svn branching to 4.1. I'm not exactly happy with the idea but think the most practical solution is to check any necessary roller patch and the built war into svn. I don't know if we could convince the roller project to release maven-compatible artifacts in a reasonable amount of time. There is a mvn-deploy section in the roller projects ant build.xml file but I don't know if anybody has pulled the trigger ;) but releasing artifacts may not be that far away. But as you say a more practical solution is probably to add the war by setting up a extra roller-war-mvn-install section in the roller plugin code base that puts the war in your local maven repos. Another possible improvement is to remove the jars from WEB-INF/lib and put them into our repository. This would greatly reduce the size of the war we'd have to keep in svn. In the long run, if we cant convince the roller teem to pick up maven which dosen't seem likely, this would be something to consider although during my work on a maven build system for roller I found that 4 of the roller used lib jars is not present in maven, but that may have changed. One way to accomplish this would be to pick up and maintain the maven build patch for roller but maybe that would be to go over the river for water. It might be worth it :-) after spending some time working on a roller security refactoring I remember so many of the reasons I don't like ant :-) I've confirmed that we don't need additional roller patches with the current plugin to get something installable. I've also played around with a no-libs roller without anything in its WEB-INF/lib, all these jars being dependencies in the geronimo repo. See the GERONIMO-2994-nolibs.patch and GERONIMO-2994-roller-patch patches. These seem to work fine (only tried jetty so far) but introduce the question of how to make the 4-5 unpublished jars and roller jars
[jira] Assigned: (GERONIMO-3806) CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB jar
[
https://issues.apache.org/jira/browse/GERONIMO-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy reassigned GERONIMO-3806:
-
Assignee: Manu T George (was: Vamsavardhana Reddy)
CLONE -Extraneous WARN messages during deployment of resource-env-refs in EJB
jar
-
Key: GERONIMO-3806
URL: https://issues.apache.org/jira/browse/GERONIMO-3806
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: deployment
Affects Versions: 2.0.2
Environment: Windows XP SP2
Reporter: toby cabot
Assignee: Manu T George
Priority: Minor
Attachments: bug3806-patch.txt
During deployment of one of my EJB jar files in my EAR, I get the following
WARN messages:
{code}
14:29:37,425 WARN [AdminObjectRefBuilder] Failed to build reference to Admin
object reference [jms/UnsequencedDestination, jms/MailQueue,
jms/InboundEventQueue, jms/OutboundQueue, jms/SystemQueue, jms/ActionQueue,
jms/SequencedDestination, jms/InboundIntegrationQueue,
jms/OutboundEventQueue] defined in plan file, reason - corresponding entry in
deployment descriptor missing.
14:29:37,440 WARN [ResourceRefBuilder] Failed to build reference to resource
reference [jms/ConnectionFactory, jms/QueueConnectionFactory,
mail/MailSession, jms/TopicConnectionFactory] defined in plan file, reason -
corresponding entry in deployment descriptor missing.
{code}
This occurs at the point in the following point in the stack:
{code}
AdminObjectRefBuilder.buildNaming(XmlObject, XmlObject, Module, Map) line: 160
{code}
The specDD that is passed in is a XML fragment for a specific session bean.
However, the plan that is passed in contains all the resource-ref and
resource-env-ref elements in the openejb-jar.xml plan. Therefore, the
refMap variable does not get completely emptied out, since the specific
session bean will only contain a subset of the resource-env-refs that are
defined in the plan.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[BUILD] 2.1: Failed for Revision: 629570
Geronimo Revision: 629570 built with tests included See the full build-1400.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080220/build-1400.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/2.1/20080220 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 51 minutes 6 seconds [INFO] Finished at: Wed Feb 20 15:27:44 EST 2008 [INFO] Final Memory: 342M/887M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080220/logs-1400-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080220/logs-1400-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 76.518 sec FAILURE!
Re: TCK Dog
On Feb 20, 2008, at 1:15 PM, Jay D. McHugh wrote: I've been referred to as a puppy before :) But I'd be happy to graduate to TCK Dog. And, I already have my NDA registered. I am still trying to get my local TCK build environment set up though. But as long as I was able to transition into the role with some help, I'll volunteer. Cool. Thanks a lot Jay! I think we all owe Joe a big thanks. He's done a great job keeping our TCK status in the green... --kevan
[jira] Updated: (GERONIMO-3860) HttpResponseDecoder does not handle folded headers properly
[ https://issues.apache.org/jira/browse/GERONIMO-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangjin Lee updated GERONIMO-3860: -- Attachment: GERONIMO-3860.patch I'm attaching a suggested fix for this. I've added a different method for decoding folded header lines to HttpDecoder. It properly takes into account CRLF followed by (SP|HT) and continues if that combination is encountered. Later CRLF is removed when the name and value are parsed. HttpResponseDecoder does not handle folded headers properly --- Key: GERONIMO-3860 URL: https://issues.apache.org/jira/browse/GERONIMO-3860 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: AsyncHttpClient Affects Versions: 1.x Reporter: Sangjin Lee Assignee: Rick McGuire Priority: Minor Attachments: GERONIMO-3860.patch HttpResponseDecoder makes an assumption that headers complete in a single line ended by CRLF. The HTTP RFC (along with RFC 822) permits a single header spanning multiple lines. Such folding can be detected by detecting the leading LWSP char (either a space or a horizontal tab). HttpResponseDecoder needs to handle this properly. Currently it throws a ProtocolDecoderException (StringIndexOutOfBoundsException underneath). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo in year 2008
I know kevan already responded but this is important... so I'm saying the same thing again... On Feb 20, 2008, at 2:31 AM, Shiva Kumar H R wrote: On Feb 16, 2008 8:30 AM, Jacek Laskowski [EMAIL PROTECTED] wrote: On Feb 15, 2008 1:30 AM, Shiva Kumar H R [EMAIL PROTECTED] wrote: GEP Task https://issues.apache.org/jira/browse/ GERONIMODEVTOOLS-278 is created for this. We can use this, as well as IRC chats dev- list mails, for collaborating! Please use [EMAIL PROTECTED] for any important stuff around it. I'd be glad to learn a bit about Eclipse plugin development following your conversations. Okey? I have generally found discussions on IRC leading to quicker better understanding of problems. All discussions on #geronimo get logged in http://servlet.uwyn.com/drone/log/bevinbot/geronimo/ mmdd and I typically paste those links into relevant JIRAs. So no discussions are lost. Now duplicating this effort by again posting mails on dev-list would be very time consuming :( umm, tough :-) All development decisions MUST be documented and preferably made on the mailing lists. In addition, relying on a third party website is NOT ACCEPTABLE. If you choose to use IRC to come up with an idea for how to implement something you have to document that proposal on the mailing lists. In my experience IRC conversations about design are incomprehensible after the fact so its usually necessary to actually write an email describing what you are proposing rather than quote IRC. thanks david jencks -- Thanks, Shiva Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[BUILD] 2.2: Failed for Revision: 629673
Geronimo Revision: 629673 built with tests included See the full build-2100.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080220/build-2100.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/trunk/20080220 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 34 minutes 20 seconds [INFO] Finished at: Wed Feb 20 21:47:21 EST 2008 [INFO] Final Memory: 304M/1011M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080220/logs-2100-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080220/logs-2100-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.973 sec FAILURE!
Re: Geronimo Tomcat 2.0.3-SNAPSHOT: SESSIONS.ser written to workDir
On Tue, Feb 19, 2008 at 3:37 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: With Geronimo Tomcat 2.0.3-SNAPSHOT, when a web app is stopped, I am noticing that the call to stop() in GeronimoStandardContext.kill() is making the sessions to be written to a SESSIONS.ser under the workDir for the application. But then destroy() called immediately is resulting in the deletion of the workDir altogether. Under what situations will this workDir be not deleted and how this SESSIONS.ser will be used/supposed to be used? What's 2.0.3-SNAPSHOT? I have never seen it mentioned before. Should we care about it rather than pushing 2.1 to our end users? Why are you working with the older version? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: G2.1: tranql-connector-derby-embed-xa version 1.3 not 1.4
On Tue, Feb 19, 2008 at 1:13 PM, Vasily Zakharov [EMAIL PROTECTED] wrote: In G2.0.2 tranql-connector-derby-embed-xa was version 1.4, and in G2.1 it's version 1.3, is it ok? Does anyone know the answer to it? I've just checked G2.1 and it is 1.3. Were there any changes in 1.4 that were incompatible with G2.1? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Updated: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma updated GERONIMO-3865: - Attachment: GERONIMO-3865-1.patch GERONIMO-3865-1.patch fixed the unresolved keys in Security - Keystores - (open a keystore and edit the keystore) - Change keystore password unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3865-1.patch, GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMO-3865) unresolved i18n keys
[ https://issues.apache.org/jira/browse/GERONIMO-3865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YunFeng Ma reopened GERONIMO-3865: -- Another unresolved i18n keys unresolved i18n keys Key: GERONIMO-3865 URL: https://issues.apache.org/jira/browse/GERONIMO-3865 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1, 2.1.1, 2.2 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 2.1.1, 2.2 Attachments: GERONIMO-3865.patch There are still a few places in the console where the i18n keys are displayed instead of the actual text: 1) Users and Groups, Console Realm Groups help screen 2) JMX viewer help screen 3) Server Log Viewer help screen Also, Database Pools help screen does not work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3858) start-server.bat fails to start server if there is a space in the path
[ https://issues.apache.org/jira/browse/GERONIMO-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570969#action_12570969 ] YunFeng Ma commented on GERONIMO-3858: -- The Ant trunk build fixed this problem, but I can not find the latest ant build from any Maven repository site. start-server.bat fails to start server if there is a space in the path -- Key: GERONIMO-3858 URL: https://issues.apache.org/jira/browse/GERONIMO-3858 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 2.1, 2.1.1, 2.2 Environment: Windows XP Reporter: YunFeng Ma start-server.bat fails to start server if there is a space in the install path, but startup.bat works fine. Looks like it's an Ant bug. H:\myf\Apache Geronimo\binstart-server.bat --- constituent[0]: file:/H:/myf/Apache Geronimo/etc/ constituent[1]: file:/H:/myf/Apache Geronimo/lib/gshell/geronimo-commands-2.1-SN APSHOT.jar constituent[2]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant/1.7.0 /ant-1.7.0.jar constituent[3]: file:/H:/myf/Apache Geronimo/repository/org/apache/ant/ant-launc her/1.7.0/ant-launcher-1.7.0.jar constituent[4]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-cli/1.0-alpha-1-SNAPSHOT/gshell-cli-1.0-alpha-1-SNAPSHOT.jar constituent[5]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-embeddable/1.0-alpha-1-SNAPSHOT/gshell-embeddable-1.0-alpha-1-SNAPSHOT .jar constituent[6]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-client/1.0-alpha-1-SNAPSHOT/gshell-remote-client-1.0-alp ha-1-SNAPSHOT.jar constituent[7]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-common/1.0-alpha-1-SNAPSHOT/gshell-remote-common-1.0-alp ha-1-SNAPSHOT.jar constituent[8]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/remote/gshell-remote-server/1.0-alpha-1-SNAPSHOT/gshell-remote-server-1.0-alp ha-1-SNAPSHOT.jar constituent[9]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/gshe ll/gshell-whisper/1.0-alpha-1-SNAPSHOT/gshell-whisper-1.0-alpha-1-SNAPSHOT.jar constituent[10]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-co re/1.1.2/mina-core-1.1.2.jar constituent[11]: file:/H:/myf/Apache Geronimo/repository/org/apache/mina/mina-fi lter-ssl/1.1.2/mina-filter-ssl-1.1.2.jar constituent[12]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/groovy/gro ovy-all/1.1-rc-1/groovy-all-1.1-rc-1.jar constituent[13]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/slf4j-log4j12 /1.4.3/slf4j-log4j12-1.4.3.jar constituent[14]: file:/H:/myf/Apache Geronimo/repository/org/slf4j/jcl104-over-s lf4j/1.4.3/jcl104-over-slf4j-1.4.3.jar constituent[15]: file:/H:/myf/Apache Geronimo/lib/geronimo-kernel-2.1-SNAPSHOT.j ar constituent[16]: file:/H:/myf/Apache Geronimo/lib/log4j-1.2.14.jar constituent[17]: file:/H:/myf/Apache Geronimo/lib/cglib-nodep-2.1_3.jar constituent[18]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/spe cs/geronimo-javaee-deployment_1.1MR3_spec/1.0/geronimo-javaee-deployment_1.1MR3_ spec-1.0.jar constituent[19]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-cli/2.1-SNAPSHOT/geronimo-cli-2.1-SNAPSHOT.jar constituent[20]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-config/2.1-SNAPSHOT/geronimo-deploy-config-2.1-SNAPSHOT.jar constituent[21]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-jsr88/2.1-SNAPSHOT/geronimo-deploy-jsr88-2.1-SNAPSHOT.jar constituent[22]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-deploy-tool/2.1-SNAPSHOT/geronimo-deploy-tool-2.1-SNAPSHOT.jar constituent[23]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-system/2.1-SNAPSHOT/geronimo-system-2.1-SNAPSHOT.jar constituent[24]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-plugin/2.1-SNAPSHOT/geronimo-plugin-2.1-SNAPSHOT.jar constituent[25]: file:/H:/myf/Apache Geronimo/repository/org/apache/geronimo/mod ules/geronimo-common/2.1-SNAPSHOT/geronimo-common-2.1-SNAPSHOT.jar constituent[26]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple xus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar constituent[27]: file:/H:/myf/Apache Geronimo/repository/org/codehaus/plexus/ple xus-utils/1.4.1/plexus-utils-1.4.1.jar --- java.lang.IllegalArgumentException at
