Re: eclipse as a top-level directory in GEP zip file?
On Thu, Apr 3, 2008 at 3:34 AM, Tim McConnell [EMAIL PROTECTED] wrote: Hi Jacek, just to be certain I fully understand what you're asking. Are you suggesting that when the deployable.zip (or updatesite.zip) is unzipped it would create this directory structure ?? \eclipse\features \eclipse\plugins instead of: \features \plugins Yes, that's exactly that. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
Re: [ANNOUNCE] Jason Warner as Geronimo's most recent committer
Welcome Congratulations Jason! On Wed, Apr 2, 2008 at 11:52 PM, Joe Bohn [EMAIL PROTECTED] wrote: All, It is my privilege to announce that Jason has recently accepted an invitation to join the Apache Geronimo project. Jason has been working on Geronimo for a while now in multiple areas including J2G, javamail, G-shell commands, samples, and many more things. He is always eager to help users and goes the extra mile to ensure issues are addressed. We're grateful to have him on the project. Please give it up for Jason. Joe -- Thanks, Shiva
Re: eclipse as a top-level directory in GEP zip file?
I too agree. Would be consistent across other plug-ins. On Thu, Apr 3, 2008 at 2:06 AM, Jacek Laskowski [EMAIL PROTECTED] wrote: Hi, Just noticed that all Eclipse plugins I've recently worked with had their deployable zip files with eclipse as the top-level directory. I think we should change how GEP is assembled with eclipse as its top-level directory. What do you think? Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl -- Thanks, Shiva
[jira] Closed: (YOKO-425) POA.destroy() should not be an error if called multiple times.
[ https://issues.apache.org/jira/browse/YOKO-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed YOKO-425. - Resolution: Fixed POA.destroy() should not be an error if called multiple times. --- Key: YOKO-425 URL: https://issues.apache.org/jira/browse/YOKO-425 Project: Yoko - CORBA Server Issue Type: Bug Security Level: public(Regular issues) Components: orb core Affects Versions: v1.0.0 Reporter: Rick McGuire Assignee: Rick McGuire Priority: Minor Fix For: v1.0.0 Currently, POA.destroy() throws an exception if it is called more than once for a POA instance. This behavior is not compatible with the Sun and IBM orbs, which can cause problems for applications written for the other implementations that ensure they're performing cleanup in all situations. destroy() should just silently return if the POA has already been destroyed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-253) The Geronimo Eclipse Plugin is automatically generating deployment plans with outdated and/or incorrect namespaces
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R resolved GERONIMODEVTOOLS-253. -- Resolution: Fixed Fixed in trunk. The Geronimo Eclipse Plugin is automatically generating deployment plans with outdated and/or incorrect namespaces -- Key: GERONIMODEVTOOLS-253 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-253 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (YOKO-426) Switch exception stack traces back to caller's thread.
Switch exception stack traces back to caller's thread. --- Key: YOKO-426 URL: https://issues.apache.org/jira/browse/YOKO-426 Project: Yoko - CORBA Server Issue Type: Improvement Security Level: public (Regular issues) Components: orb core Affects Versions: v1.0.0 Reporter: Rick McGuire Assignee: Rick McGuire Priority: Minor Fix For: v1.0.0 Currently, exceptions that are sent back from the server to the client have the stack trace of the thread that receives the response from the client rather than the stack of the application code that sent the request. This can make debugging of user problems more difficult because there's no tie-back to the original code causing the exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (YOKO-426) Switch exception stack traces back to caller's thread.
[ https://issues.apache.org/jira/browse/YOKO-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire closed YOKO-426. - Resolution: Fixed Committed revision 644283. Switch exception stack traces back to caller's thread. --- Key: YOKO-426 URL: https://issues.apache.org/jira/browse/YOKO-426 Project: Yoko - CORBA Server Issue Type: Improvement Security Level: public(Regular issues) Components: orb core Affects Versions: v1.0.0 Reporter: Rick McGuire Assignee: Rick McGuire Priority: Minor Fix For: v1.0.0 Currently, exceptions that are sent back from the server to the client have the stack trace of the thread that receives the response from the client rather than the stack of the application code that sent the request. This can make debugging of user problems more difficult because there's no tie-back to the original code causing the exception. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-247) SharedLib dependency incorrectly generated for 2.0.x version of the Geronimo server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R resolved GERONIMODEVTOOLS-247. -- Resolution: Fixed Fixed in trunk. SharedLib dependency incorrectly generated for 2.0.x version of the Geronimo server --- Key: GERONIMODEVTOOLS-247 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-247 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.1.0 The SharedLib dependency is getting created as below in the web.xml, which is the old 1.1.1 format: sys:dependencies sys:dependency sys:groupIdgeronimo/sys:groupId sys:artifactIdsharedlib/sys:artifactId sys:typecar/sys:type /sys:dependency /sys:dependencies It should be as below for the 2.0.x format: sys:dependencies sys:dependency sys:groupIdorg.apache.geronimo.configs/sys:groupId sys:artifactIdsharedlib/sys:artifactId sys:typecar/sys:type /sys:dependency /sys:dependencies -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Java Service Wrapper
Roy pointed out two docs we have where we define Geronimo as a service in Windows. We may not have this doc included in the Geronimo v2.1 documentation as it seems JSP does not get along very well with G. Dan B. is working on this doc, I'd wait for his update. Cheers! Hernan Alan D. Cabrera wrote: Something that we might need to look into. Regards, Alan -- Forwarded message -- From: *Roy T. Fielding* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Date: Wed, Apr 2, 2008 at 3:20 PM Subject: Java Service Wrapper To: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] The Java Service Wrapper is being used (and sometimes redistributed) by many of our Java projects (ActiveMQ, ServiceMix, Geronimo, OFBiz, Tomcat). It was formerly available under an MIT/BSD style license, as can be seen in the 3.2.3 version at http://sourceforge.net/projects/wrapper/ More recent versions of the product are currently under dual GPLv2 and commercial licensing. http://wrapper.tanukisoftware.org/doc/english/licenseOverview.html And yet no mention of its license is found in our documentation. http://activemq.apache.org/java-service-wrapper.html http://docs.ofbiz.org/display/OFBIZ/How+to+Run+OFBiz+as+Windows+Service+with+Java+Service+Wrapper http://people.apache.org/~fhanik/wrapper.html http://people.apache.org/%7Efhanik/wrapper.html http://wiki.apache.org/db-derby/DerbyWindowsService and the only pages we have that refer to the old version are in Geronimo http://cwiki.apache.org/GMOxDOC11/configuring-geronimo-as-a-windows-service.html http://cwiki.apache.org/GMOxDOC20/configuring-geronimo-as-a-windows-service.html If your project is currently distributing or telling users to make use of the Java Service Wrapper, please be sure that we only use the old licensed version, that our documentation points to the old site, and that when we do point folks to wrapper.tanukisoftware.org http://wrapper.tanukisoftware.org/ (which we should do because some users are not allergic to GPLv2) we should also point out that the newer versions are under different licenses (GPLv2/commercial). Roy - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
[jira] Closed: (GERONIMO-3837) allowLinking Tomcat atttibute in StandardContext not configurable through Geronimo
[ https://issues.apache.org/jira/browse/GERONIMO-3837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vamsavardhana Reddy closed GERONIMO-3837. - Resolution: Fixed Added doc at http://cwiki.apache.org/confluence/display/GMOxDEV/Configure+allowLinking+for+Tomcat+contexts allowLinking Tomcat atttibute in StandardContext not configurable through Geronimo --- Key: GERONIMO-3837 URL: https://issues.apache.org/jira/browse/GERONIMO-3837 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 2.0.2, 2.0.x, 2.1, 2.2 Environment: G 2.0.2 Tomcat on Linux Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: 2.0.x, 2.1.1, 2.2 Tomcat provides an allowLinking attribute in the StandardContext which when set to true will enable tomcat running on Linux platform to serve paths associated with the symbolic links. Configuring this attribute through Geronimo is not possible currently. Link to a query posted on user-list is given below. http://www.mail-archive.com/[EMAIL PROTECTED]/msg08509.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.1: Failed for Revision: 644273
Geronimo Revision: 644273 built with tests included See the full build-0800.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080403/build-0800.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/2.1/20080403 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 32 minutes 56 seconds [INFO] Finished at: Thu Apr 03 08:54:19 EDT 2008 [INFO] Final Memory: 306M/984M [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/20080403/logs-0800-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080403/logs-0800-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.261 sec FAILURE! Samples: branches/2.1 = Log: http://geronimo.apache.org/maven/server/binaries/2.1/20080403/samples-0800.log Build status: OK
Re: [ANNOUNCE] Jason Warner as Geronimo's most recent committer
Congratulations and welcome! Jay Paul McMahan wrote: Jason, congrats!! Best wishes, Paul On Apr 2, 2008, at 2:22 PM, Joe Bohn wrote: All, It is my privilege to announce that Jason has recently accepted an invitation to join the Apache Geronimo project. Jason has been working on Geronimo for a while now in multiple areas including J2G, javamail, G-shell commands, samples, and many more things. He is always eager to help users and goes the extra mile to ensure issues are addressed. We're grateful to have him on the project. Please give it up for Jason. Joe
Re: eclipse as a top-level directory in GEP zip file?
Jacek Laskowski wrote: Just noticed that all Eclipse plugins I've recently worked with had their deployable zip files with eclipse as the top-level directory. I think we should change how GEP is assembled with eclipse as its top-level directory. What do you think? It is also nice to have just plugins and features rather than eclipse\plugins and eclipse\features when you have different versions of eclipse and change the directory to eclipse3.2 eclipse3.3 eclipse7.1 etc. -- Thanks, Dan Becker
Re: Java Service Wrapper
G 2.1 now working with JSP 3.2.3. Thanks Dan for looking into this. http://cwiki.apache.org/GMOxDOC21/configuring-geronimo-as-a-windows-service.html Cheers! Hernan Hernan Cunico wrote: Roy pointed out two docs we have where we define Geronimo as a service in Windows. We may not have this doc included in the Geronimo v2.1 documentation as it seems JSP does not get along very well with G. Dan B. is working on this doc, I'd wait for his update. Cheers! Hernan Alan D. Cabrera wrote: Something that we might need to look into. Regards, Alan -- Forwarded message -- From: *Roy T. Fielding* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Date: Wed, Apr 2, 2008 at 3:20 PM Subject: Java Service Wrapper To: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] The Java Service Wrapper is being used (and sometimes redistributed) by many of our Java projects (ActiveMQ, ServiceMix, Geronimo, OFBiz, Tomcat). It was formerly available under an MIT/BSD style license, as can be seen in the 3.2.3 version at http://sourceforge.net/projects/wrapper/ More recent versions of the product are currently under dual GPLv2 and commercial licensing. http://wrapper.tanukisoftware.org/doc/english/licenseOverview.html And yet no mention of its license is found in our documentation. http://activemq.apache.org/java-service-wrapper.html http://docs.ofbiz.org/display/OFBIZ/How+to+Run+OFBiz+as+Windows+Service+with+Java+Service+Wrapper http://people.apache.org/~fhanik/wrapper.html http://people.apache.org/%7Efhanik/wrapper.html http://wiki.apache.org/db-derby/DerbyWindowsService and the only pages we have that refer to the old version are in Geronimo http://cwiki.apache.org/GMOxDOC11/configuring-geronimo-as-a-windows-service.html http://cwiki.apache.org/GMOxDOC20/configuring-geronimo-as-a-windows-service.html If your project is currently distributing or telling users to make use of the Java Service Wrapper, please be sure that we only use the old licensed version, that our documentation points to the old site, and that when we do point folks to wrapper.tanukisoftware.org http://wrapper.tanukisoftware.org/ (which we should do because some users are not allergic to GPLv2) we should also point out that the newer versions are under different licenses (GPLv2/commercial). Roy - To unsubscribe, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Re: [BUILD] branches/2.1: Failed for Revision: 644273
Jarek, I can access the Tomcat test.log, but not the Jetty test.log. Is there a permissions problem? --kevan On Apr 3, 2008, at 10:25 AM, [EMAIL PROTECTED] wrote: Geronimo Revision: 644273 built with tests included See the full build-0800.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080403/build-0800.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/2.1/20080403 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 32 minutes 56 seconds [INFO] Finished at: Thu Apr 03 08:54:19 EDT 2008 [INFO] Final Memory: 306M/984M [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/20080403/logs-0800-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/2.1/20080403/logs-0800-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 72.261 sec FAILURE! Samples: branches/2.1 = Log: http://geronimo.apache.org/maven/server/binaries/2.1/20080403/samples-0800.log Build status: OK
[jira] Resolved: (GERONIMODEVTOOLS-209) Hello World JSP does not open in Eclipse browser when invoked with run as, run on server from within Eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shiva Kumar H R resolved GERONIMODEVTOOLS-209. -- Resolution: Fixed Assignee: Shiva Kumar H R (was: Tim McConnell) Haven't encountered this in all my tests so far with GEP trunk. Looks like WTP latest levels or some other change in GEP has fixed this. Hence closing this. Hello World JSP does not open in Eclipse browser when invoked with run as, run on server from within Eclipse -- Key: GERONIMODEVTOOLS-209 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-209 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Assignee: Shiva Kumar H R Fix For: 2.1.0 This appears to be a WTP 2.0.x bug, not a problem with the Eclipse plugin. The Eclipse plugin is passing a valid HttpLaunchable object, with the correct url, to the WTP web client launcher class ([org.eclipse.wst.server.ui.web). But when it is ultimately ready to be launched that launchable object is null causing a NPE (stack trace below). Moving the JIRA to 2.1, and will open a bugzilla report against WTP 2.0.x. java.lang.NullPointerException at org.eclipse.wst.server.ui.internal.WebLaunchableClient.launch(WebLaunchableClient.java:39) at org.eclipse.wst.server.core.internal.Client.launch(Client.java:114) at org.eclipse.wst.server.ui.internal.LaunchClientJob$1.run(LaunchClientJob.java:79) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3659) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3296) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) at org.eclipse.equinox.launcher.Main.main(Main.java:1148) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [DISCUSS] Geronimo 2.1.1 release
Donald Woods wrote: Also, it seems that we need an updated tranql-connector-db2-xa-1.2 build, to fix a known problem with the trace file setting. See http://www.nabble.com/forum/ViewPost.jtp?post=16404097framed=yskin=134 Thanks Donald. I asked on that thread if updating to the newer connector actually resolved the issue. Does anybody happen to know if there is a release planned in the near future for this connector should it prove to be the solution for this issue? If not, how hard would it be to add create one (I guess that's a question for you David)? Also, I'm not sure how these connectors are typically released ... would we upgrade all of the connectors or just the db2-xa connector? Perhaps it would suffice to just include documentation on how to upgrade the connector to resolve the issue and deliver the released connector in 2.1.2 and/or 2.2. Joe -Donald Joe Bohn wrote: I think it's about time we got a 2.1.1 release out. The main motivation is to deliver a fix for the PortletSecurityException when using https on the admin console (https://issues.apache.org/jira/browse/GERONIMO-3855). but there are a lot of other fixes that have been integrated as well. The TCK looked good with a recent run ... so I think that should not be an issue. As far as snapshots go, it looks like we're now pulling in a snapshot for javamail that we would need to resolve (geronimo-javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one. Are there any other changes/fixes that we should be looking to include prior to a release? I am willing to get my feet wet as the release manager unless somebody else wants to pick it up. Joe
Re: [DISCUSS] Geronimo 2.1.1 release
On Apr 3, 2008, at 9:02 AM, Joe Bohn wrote: Donald Woods wrote: Also, it seems that we need an updated tranql-connector-db2-xa-1.2 build, to fix a known problem with the trace file setting. See http://www.nabble.com/forum/ViewPost.jtp? post=16404097framed=yskin=134 Thanks Donald. I asked on that thread if updating to the newer connector actually resolved the issue. Does anybody happen to know if there is a release planned in the near future for this connector should it prove to be the solution for this issue? If not, how hard would it be to add create one (I guess that's a question for you David)? Also, I'm not sure how these connectors are typically released ... would we upgrade all of the connectors or just the db2-xa connector? Just that one. I'll try for today or tomorrow. IIRC we haven't been having votes on tranql stuff so I think I just need to review the build state and release it. thanks david jencks Perhaps it would suffice to just include documentation on how to upgrade the connector to resolve the issue and deliver the released connector in 2.1.2 and/or 2.2. Joe -Donald Joe Bohn wrote: I think it's about time we got a 2.1.1 release out. The main motivation is to deliver a fix for the PortletSecurityException when using https on the admin console (https://issues.apache.org/ jira/browse/GERONIMO-3855). but there are a lot of other fixes that have been integrated as well. The TCK looked good with a recent run ... so I think that should not be an issue. As far as snapshots go, it looks like we're now pulling in a snapshot for javamail that we would need to resolve (geronimo- javamail_1.4_mail-1.4-SNAPSHOT.jar). I think that's the only one. Are there any other changes/fixes that we should be looking to include prior to a release? I am willing to get my feet wet as the release manager unless somebody else wants to pick it up. Joe
Re: eclipse as a top-level directory in GEP zip file?
On Thu, Apr 3, 2008 at 4:42 PM, Dan Becker [EMAIL PROTECTED] wrote: It is also nice to have just plugins and features rather than eclipse\plugins and eclipse\features when you have different versions of eclipse and change the directory to eclipse3.2 eclipse3.3 eclipse7.1 etc. The real solution to the issue is to use Eclipse's extension locations so you define a link file in links directory (beneath the Eclipse home directory) where you point out the directory with plugins to be included, i.e. [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l links/ total 9 -rwx--+ 1 jlaskowski None 44 Feb 11 08:49 GEF.link -rwx--+ 1 jlaskowski None 35 Mar 27 13:54 ajdt.link -rwx--+ 1 jlaskowski None 45 Feb 11 08:53 dtp.link -rwx--+ 1 jlaskowski None 54 Feb 11 08:49 emf-sdo-xsd.link -rwx--+ 1 jlaskowski None 54 Mar 31 10:50 geronimo-eclipse-plugin.link -rwx--+ 1 jlaskowski None 40 Feb 14 04:20 m2eclipse.link -rwx--+ 1 jlaskowski None 53 Feb 23 23:32 openejb-eclipse-plugin.link -rwx--+ 1 jlaskowski None 43 Feb 14 09:01 wicket-bench.link -rwx--+ 1 jlaskowski None 42 Feb 14 09:01 wtp.link [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ cat links/geronimo-eclipse-plugin.link path=C:/apps/eclipse-plugins/geronimo-eclipse-plugin [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l C:/apps/eclipse-plugins/geronimo-eclipse-plugin total 0 drwx--+ 4 jlaskowski None 0 Mar 31 10:17 eclipse [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l C:/apps/eclipse-plugins/geronimo-eclipse-plugin/eclipse total 24 -rwx--+ 1 jlaskowski None 19125 Oct 29 14:06 LICENSE -rwx--+ 1 jlaskowski None 3298 Oct 29 14:06 NOTICE drwx--+ 8 jlaskowski None 0 Mar 31 09:06 features drwx--+ 2 jlaskowski None 0 Mar 31 09:06 plugins No matter how hard you'd try updates are always very painful, but Extension Locations feature of Eclipse made it a breeze. Jacek -- Jacek Laskowski http://www.JacekLaskowski.pl
[jira] Created: (GERONIMO-3949) Problem creating a DB2 datasource
Problem creating a DB2 datasource - Key: GERONIMO-3949 URL: https://issues.apache.org/jira/browse/GERONIMO-3949 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: connector, console Affects Versions: 2.1 Reporter: Hernan Cunico Geronimo 2.1 comes with tranql-connector-db2-xa 1.1 which has some issues. The pool created with the wizard deploys but the database can not get accessed. I tested with tranql-connector-db2-xa 1.2-20080326.214959-2 available from http://snapshots.repository.codehaus.org/org/tranql/tranql-connector-db2-xa/1.2-SNAPSHOT/tranql-connector-db2-xa-1.2-20080326.214959-2.rar With 1.2 snapshot I can use the wizard, create a plan and deploy the pool; all from the admin console but I fail to access the database defined in the pool. (for the record it deploys OK from the console) The weird thing is that if I use the wizard just to create a plan but then deploy it from the command line it also deploys OK but also I CAN access the DB. See thread [Problem creating a DB2 datasource] on the user list (I'll add a link once nabble gets updated) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-3950) Mconsole - Change graphs to display mildly curved as they did in first iteration
Mconsole - Change graphs to display mildly curved as they did in first iteration Key: GERONIMO-3950 URL: https://issues.apache.org/jira/browse/GERONIMO-3950 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Minor Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 1.x -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3950) Mconsole - Change graphs to display mildly curved as they did in first iteration
[ https://issues.apache.org/jira/browse/GERONIMO-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig updated GERONIMO-3950: Description: Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 0.4.3 (was: Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 1.x) Mconsole - Change graphs to display mildly curved as they did in first iteration Key: GERONIMO-3950 URL: https://issues.apache.org/jira/browse/GERONIMO-3950 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Minor Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 0.4.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-3950) Mconsole - Change graphs to display mildly curved as they did in first iteration
[ https://issues.apache.org/jira/browse/GERONIMO-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik B. Craig closed GERONIMO-3950. --- Resolution: Fixed Committed revision 644462. Mconsole - Change graphs to display mildly curved as they did in first iteration Key: GERONIMO-3950 URL: https://issues.apache.org/jira/browse/GERONIMO-3950 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: monitoring Affects Versions: 2.2 Reporter: Erik B. Craig Assignee: Erik B. Craig Priority: Minor Mconsole - Change graphs to display mildly curved as they did in first iteration using dojo 0.4.3 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: eclipse as a top-level directory in GEP zip file?
Yes, I use this function as well and it simplifies management of my various Eclipse plugins much simpler. Jacek Laskowski wrote: On Thu, Apr 3, 2008 at 4:42 PM, Dan Becker [EMAIL PROTECTED] wrote: It is also nice to have just plugins and features rather than eclipse\plugins and eclipse\features when you have different versions of eclipse and change the directory to eclipse3.2 eclipse3.3 eclipse7.1 etc. The real solution to the issue is to use Eclipse's extension locations so you define a link file in links directory (beneath the Eclipse home directory) where you point out the directory with plugins to be included, i.e. [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l links/ total 9 -rwx--+ 1 jlaskowski None 44 Feb 11 08:49 GEF.link -rwx--+ 1 jlaskowski None 35 Mar 27 13:54 ajdt.link -rwx--+ 1 jlaskowski None 45 Feb 11 08:53 dtp.link -rwx--+ 1 jlaskowski None 54 Feb 11 08:49 emf-sdo-xsd.link -rwx--+ 1 jlaskowski None 54 Mar 31 10:50 geronimo-eclipse-plugin.link -rwx--+ 1 jlaskowski None 40 Feb 14 04:20 m2eclipse.link -rwx--+ 1 jlaskowski None 53 Feb 23 23:32 openejb-eclipse-plugin.link -rwx--+ 1 jlaskowski None 43 Feb 14 09:01 wicket-bench.link -rwx--+ 1 jlaskowski None 42 Feb 14 09:01 wtp.link [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ cat links/geronimo-eclipse-plugin.link path=C:/apps/eclipse-plugins/geronimo-eclipse-plugin [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l C:/apps/eclipse-plugins/geronimo-eclipse-plugin total 0 drwx--+ 4 jlaskowski None 0 Mar 31 10:17 eclipse [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l C:/apps/eclipse-plugins/geronimo-eclipse-plugin/eclipse total 24 -rwx--+ 1 jlaskowski None 19125 Oct 29 14:06 LICENSE -rwx--+ 1 jlaskowski None 3298 Oct 29 14:06 NOTICE drwx--+ 8 jlaskowski None 0 Mar 31 09:06 features drwx--+ 2 jlaskowski None 0 Mar 31 09:06 plugins No matter how hard you'd try updates are always very painful, but Extension Locations feature of Eclipse made it a breeze. Jacek -- Thanks, Tim McConnell
Re: eclipse as a top-level directory in GEP zip file?
Jacek Laskowski wrote: The real solution to the issue is to use Eclipse's extension locations so you define a link file in links directory (beneath the Eclipse home directory) where you point out the directory with plugins to be included, i.e. [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l links/ total 9 -rwx--+ 1 jlaskowski None 44 Feb 11 08:49 GEF.link [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ cat links/geronimo-eclipse-plugin.link path=C:/apps/eclipse-plugins/geronimo-eclipse-plugin Thanks Jacek! A very useful solution. -- Thanks, Dan Becker
[BUILD] trunk: Failed for Revision: 644443
Geronimo Revision: 63 built with tests included See the full build-1500.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080403/build-1500.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/trunk/20080403 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 34 minutes 40 seconds [INFO] Finished at: Thu Apr 03 15:51:09 EDT 2008 [INFO] Final Memory: 314M/998M [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/20080403/logs-1500-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080403/logs-1500-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.246 sec FAILURE! Samples: trunk = Log: http://geronimo.apache.org/maven/server/binaries/trunk/20080403/samples-1500.log Build status: OK
Fwd: [VOTE] Release ActiveIO 3.0.1
Begin forwarded message: From: David Jencks [EMAIL PROTECTED] Date: April 3, 2008 2:29:41 PM PDT To: [EMAIL PROTECTED] Subject: [VOTE] Release ActiveIO 3.0.1 Reply-To: [EMAIL PROTECTED] ActiveIO is still used by activemq 4.1.x and had a couple annoying bugs like AMQ-704 This release is to a certain extent to test out the proposed release process using the maven release and staging plugins. Geronimo also needs it. Please check it out and vote. Staging repo: http://people.apache.org/~djencks/staging-repo/activeio/ Staging site: http://people.apache.org/~djencks/staging-site/activeio/maven/3.0.1 Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 Many thanks david jencks
Re: eclipse as a top-level directory in GEP zip file?
FYI, a good article on the subject that I used to learn about Eclipse links. Jacek Laskowski wrote: On Thu, Apr 3, 2008 at 4:42 PM, Dan Becker [EMAIL PROTECTED] wrote: It is also nice to have just plugins and features rather than eclipse\plugins and eclipse\features when you have different versions of eclipse and change the directory to eclipse3.2 eclipse3.3 eclipse7.1 etc. The real solution to the issue is to use Eclipse's extension locations so you define a link file in links directory (beneath the Eclipse home directory) where you point out the directory with plugins to be included, i.e. [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l links/ total 9 -rwx--+ 1 jlaskowski None 44 Feb 11 08:49 GEF.link -rwx--+ 1 jlaskowski None 35 Mar 27 13:54 ajdt.link -rwx--+ 1 jlaskowski None 45 Feb 11 08:53 dtp.link -rwx--+ 1 jlaskowski None 54 Feb 11 08:49 emf-sdo-xsd.link -rwx--+ 1 jlaskowski None 54 Mar 31 10:50 geronimo-eclipse-plugin.link -rwx--+ 1 jlaskowski None 40 Feb 14 04:20 m2eclipse.link -rwx--+ 1 jlaskowski None 53 Feb 23 23:32 openejb-eclipse-plugin.link -rwx--+ 1 jlaskowski None 43 Feb 14 09:01 wicket-bench.link -rwx--+ 1 jlaskowski None 42 Feb 14 09:01 wtp.link [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ cat links/geronimo-eclipse-plugin.link path=C:/apps/eclipse-plugins/geronimo-eclipse-plugin [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l C:/apps/eclipse-plugins/geronimo-eclipse-plugin total 0 drwx--+ 4 jlaskowski None 0 Mar 31 10:17 eclipse [EMAIL PROTECTED] /cygdrive/c/apps/eclipse $ ls -l C:/apps/eclipse-plugins/geronimo-eclipse-plugin/eclipse total 24 -rwx--+ 1 jlaskowski None 19125 Oct 29 14:06 LICENSE -rwx--+ 1 jlaskowski None 3298 Oct 29 14:06 NOTICE drwx--+ 8 jlaskowski None 0 Mar 31 09:06 features drwx--+ 2 jlaskowski None 0 Mar 31 09:06 plugins No matter how hard you'd try updates are always very painful, but Extension Locations feature of Eclipse made it a breeze. Jacek -- Thanks, Tim McConnell
[jira] Resolved: (GERONIMODEVTOOLS-316) intermittent Geronimo Deployment 1.2 cannot be installed. error message from the Eclipse Project Facets wizard
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell resolved GERONIMODEVTOOLS-316. Resolution: Fixed Fix Version/s: 2.1.0 The problem was a classic race condition. Using the same action type id for a Geronimo Deployment project facet across multiple plugins was ill-advised on my part. As a result, the first project facet loaded by Eclipse would work just fine, but others loaded subquently by Eclipse would fail. Now each version of the Geronimo Deployment project facet has a unique action type id to fix the problem. intermittent Geronimo Deployment 1.2 cannot be installed. error message from the Eclipse Project Facets wizard Key: GERONIMODEVTOOLS-316 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-316 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 2.1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-222) Warning messages at Eclipse Plugin startup
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim McConnell resolved GERONIMODEVTOOLS-222. Resolution: Fixed Fixed with GERONIMODEVTOOLS-316. We should get in th habit of cleaning up warning messages emitted from the GEP whenever possible. Warning messages at Eclipse Plugin startup -- Key: GERONIMODEVTOOLS-222 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-222 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Assignee: Tim McConnell Priority: Minor Fix For: 2.1.0 These warning messages should be eliminated at Eclipse plugin startup. They are located in \workspaces\.metadata\.log file. !ENTRY org.eclipse.emf.ecore 2 0 2007-09-21 17:37:42.265 !MESSAGE Both 'org.apache.geronimo.deployment.model' and 'org.apache.geronimo.v11.deployment.model' register an extension parser for 'deployment' !ENTRY org.eclipse.emf.ecore 2 0 2007-09-21 17:37:42.281 !MESSAGE Both 'org.apache.geronimo.deployment.model' and 'org.apache.geronimo.v11.deployment.model' register an extension parser for 'naming' !ENTRY org.eclipse.emf.ecore 2 0 2007-09-21 17:37:42.281 !MESSAGE Both 'org.apache.geronimo.deployment.model' and 'org.apache.geronimo.v11.deployment.model' register an extension parser for 'web' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 644568
Geronimo Revision: 644568 built with tests included See the full build-2100.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080403/build-2100.log Download the binaries from http://geronimo.apache.org/maven/server/binaries/trunk/20080403 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 30 minutes 29 seconds [INFO] Finished at: Thu Apr 03 21:39:26 EDT 2008 [INFO] Final Memory: 314M/1000M [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/20080403/logs-2100-tomcat/test.log Assembly: jetty = See the full test.log file at http://geronimo.apache.org/maven/server/binaries/trunk/20080403/logs-2100-jetty/test.log [INFO] Running console-testsuite.advance-test [INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 70.762 sec FAILURE! Samples: trunk = Log: http://geronimo.apache.org/maven/server/binaries/trunk/20080403/samples-2100.log Build status: OK
