[jira] Commented: (GERONIMODEVTOOLS-705) No target platform defined for use when new a OSGi bundle project
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995831#comment-12995831 ] Ted Kirby commented on GERONIMODEVTOOLS-705: I recall that I could import the CounterApp EBA OK, but when I imported the HelloWorld EBA, I did get the target platform message. Comparing those two EBAs may provide some clue. No target platform defined for use when new a OSGi bundle project - Key: GERONIMODEVTOOLS-705 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-705 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0-M2, 3.0 Environment: windows 7 eclipse helios sr1 Oracle jdk 1.6.0_20 Reporter: Forrest Xia Assignee: Han Hong Fang Priority: Minor Fix For: 3.0-M2 Steps: 1. Install ibm osgi tool plugin 2. Install GEP 3.0-SNAPSHOT 3. Define a geronimo runtime and server 4. New an OSGi project, in the wizard page, select the defined geronimo runtime 5. On the next page, an message like this will be shown: Targeting Apache Geronimo v3.0 will change the active Target Platform for this workspace. This will affect existing OSGi bundles and plug-in projects in your workspace. These projects will be rebuilt against the new target platform, which may cause validation or compilation errors if they are not compatible with the new target platform. If not check Change the active Target platform, you cannot go ahead to next step to finish the project creation. After checking it, you can go next. Actually, GEP does not define a target platform for OSGi project use. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-711) Changes takes place on server editor even if the user does not save
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12995835#comment-12995835 ] Ted Kirby commented on GERONIMODEVTOOLS-711: Yes, it seems all properties work this way, probably because the initial version of GEP did this, and everyone has extended that approach. It seems that the changed values should only be saved in ServerDelegate.saveConfiguration(), which is seems we have not implemented to date. Changes takes place on server editor even if the user does not save --- Key: GERONIMODEVTOOLS-711 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-711 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: Eclipse Helios SR1 + GEP 3.0 Reporter: Han Hong Fang 1. Install GEP in Helios SR1 2. Create geronimo server 3.0 3. Double click geronimo server to open the server editor 4. Change the value such as user ID/Password, or HTTP Port, and then close the editor, answer NO when eclipse asks to save the changes or not. 5. Double click geronimo server to reopen the server editor, the changed value shows in the editor. The original value instead of the changed ones is expected. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994632#comment-12994632 ] Ted Kirby commented on GERONIMODEVTOOLS-706: I have added the option for a local console. However, a long term solution might need to leverage Eclipse ssh terminal to connect to Karaf (for remote server support). We need to find a way to extend ssh terminal. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994645#comment-12994645 ] Ted Kirby commented on GERONIMODEVTOOLS-706: I have added a check box to the server options to turn this on and off. If you enable the local Karaf console, -Dkaraf.startLocalConsole=true and -Dkaraf.startLocalConsole=true are added to the VM args for launching. If you disable the local Karaf console via the checkbox, those options are removed, and -Dkaraf.startLocalConsole=false is set instead. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby reassigned GERONIMODEVTOOLS-706: -- Assignee: Ted Kirby (was: Delos Dai) Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-5803) EBA cannot work after server restart
[ https://issues.apache.org/jira/browse/GERONIMO-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12993162#comment-12993162 ] Ted Kirby commented on GERONIMO-5803: - I presume you got the eba from here? http://www.ibm.com/developerworks/rational/downloads/10/rationaldevtoolsforosgiapplications.html EBA cannot work after server restart Key: GERONIMO-5803 URL: https://issues.apache.org/jira/browse/GERONIMO-5803 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 3.0-M2, 3.0 Environment: windows 7 Reporter: LiWenQin Attachments: CounterApp_1.0.0.eba 1.deploy CounterApp_1.0.0.eba through Deployer Portlet. 2.There is a copy CounterApp_1.0.0.eba in repository. 3. In the cache, there are CounterApp, CounterWebBundle, CounterServiceBundle, CounterWorldBundle and their states are all Active in the OSGi Portlet 4. We can access http://localhost:8080/CounterWebBundle/CounterServlet. 5. hard stop the server. 6. In the OSGi Portlet, states of CounterWebBundle, CounterServiceBundle, CounterWorldBundle are Resolved (CounterApp is Active) so that EBA cannot work. We cannot access url http://localhost:8080/CounterWebBundle/CounterServlet. 7. In the Application EBAs Portlet, state of application/CounterApp/1.0.0/eba is running but the app does not work. Stop application/CounterApp/1.0.0/eba in the Application EBAs Portlet will remove CounterApp in OSGi Portlet but not remove other three related bundles. (CounterApp EBA will work well after normal stop.) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMODEVTOOLS-704) Provide a check box to clean server cache when start server from GEP.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12992243#comment-12992243 ] Ted Kirby commented on GERONIMODEVTOOLS-704: FYI, I have developed code to fix this issue. Provide a check box to clean server cache when start server from GEP. - Key: GERONIMODEVTOOLS-704 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-704 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Shawn Jiang Assignee: Delos Dai Fix For: 3.0 see https://issues.apache.org/jira/browse/GERONIMO-5527, some code added to support -c/--clean switch to clean server cache from startup script. we need to add the same function in GEP. - RepositoryRevisionDateUserMessage ASF #1025840Thu Oct 21 02:05:53 EDT 2010genspring GERONIMO-5527 provide a way to clean osgi bundle cache when starting the server. Files Changed MODIFY /geronimo/server/trunk/framework/configs/karaf-framework/src/main/distribution/windows-text/bin/geronimo.bat MODIFY /geronimo/server/trunk/framework/modules/geronimo-system/src/main/java/org/apache/geronimo/system/main/EmbeddedDaemon.java MODIFY /geronimo/server/trunk/framework/modules/geronimo-cli/src/main/java/org/apache/geronimo/cli/daemon/DaemonCLParser.java MODIFY /geronimo/server/trunk/framework/configs/karaf-framework/src/main/distribution/unix-shell/bin/geronimo -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMODEVTOOLS-709) Unhandled event loop exception
Unhandled event loop exception -- Key: GERONIMODEVTOOLS-709 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-709 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 3.0-M2 Reporter: Ted Kirby Assignee: Delos Dai Priority: Minor Open G server. In overview pane, click the link Open launch configuration. Click the arguments tab. Click OK. Nothing happens, but this error log record: Unhandled event loop exception java.lang.NullPointerException at org.eclipse.wst.server.core.model.ServerDelegate.setAttribute(ServerDelegate.java:334) at org.apache.geronimo.st.v30.core.GeronimoServerDelegate.setServerInstanceProperties(GeronimoServerDelegate.java:507) at org.apache.geronimo.st.v30.core.GeronimoServerDelegate.setInstanceProperty(GeronimoServerDelegate.java:499) at org.apache.geronimo.st.v30.core.GeronimoServerDelegate.setVMArgs(GeronimoServerDelegate.java:373) at org.apache.geronimo.st.v30.ui.internal.GeronimoLaunchConfigurationTabGroup.performApply(GeronimoLaunchConfigurationTabGroup.java:74) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.performApply(LaunchConfigurationTabGroupWrapper.java:220) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1352) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.okPressed(LaunchConfigurationPropertiesDialog.java:194) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.buttonPressed(LaunchConfigurationsDialog.java:318) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1133) at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:203) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:448) at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:425) at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:588) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233) at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327) at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311) at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) I suspect this problem has been
Re: Strange GEP branch versions.
I had the same question, tho I never asked it. I think the branches should be named 2.1 and 2.2 as well. As Kevan points out, this works for server. I think GEP should do it this way too. Ted On Fri, Nov 5, 2010 at 6:36 AM, Shawn Jiang genspr...@gmail.com wrote: https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/branches/ * .. * 2.1.7/ * 2.2.1/ Is there any special reasons that we have to use this kind of version way ? I think we should name them 2.1 and 2.2 instead of 2.1.7 and 2.2.1. Upgrade the branch name for each release will lose the full svn history view of a branch. -- Shawn
Suggestions for improving new G and GEP user experiences
I have recently returned to community activity after a period of inactivity. I have played with some of the introductory material, and things have not gone that well. :-( I think G and GEP 3.0 have very exciting content: JEE 6 and OSGi, and we are on track to be early to market with our certified server. I think we want to attract new users, and we want to be ready and attractive and easy to use when they come. To that end, I offer these suggestions and feedback: 1. Geronimo v3.0, or at least v3.0-M1, should be listed on the main page Documentation link http://geronimo.apache.org/documentation.html. v3.0 is on the wiki page: https://cwiki.apache.org/geronimo/ 2. I think we should have a Getting Started or Quick Start link on the home page for folks to download and start running Geronimo quickly. This page in the doc seems good: https://cwiki.apache.org/GMOxDOC30/quick-start-apache-geronimo-for-the-impatient.html. (This page comes up first on the documentation, so maybe item 3 would address this.) 3. I don't think a version should be released unless the Quick Start actually works. If this is the entry point for new users, it should work for each release. For 3.0-M1, there are two JIRAs on this: GERONIMO-5488 and GERONIMO-5658. 4. Ditto for GEP. http://geronimo.apache.org/development-tools.html is pretty good, but there is no mention of 3.0-M1. 3.0 is an exciting release for JEE 6 and OSGi. Folks want to play with the technology. We should help them get started. 5. The 1-minute Hello World Web Application Tutorial http://cwiki.apache.org/GMOxDOC22/how-to-use-geronimo-eclipse-plugin.html#HowtoUseGeronimoEclipsePlugin-DeployRunUndeployandRedeployanApplication for GEP does not work for 3.0-M1. There is a deploy problem, and a missing message problem. I think both the 1-minute and 5-minute tutorial are part of the testsuite, and hence these errors should have been caught if the testsuite were run. I recommend adding these tutorials to the testsuite if they are not there. Again, before a GEP version is released, someone should verify these tutorials work. 6. No GEP version should be released unless the testsuite passes. 7. News items on the main page http://geronimo.apache.org/ should have dates. Currently, 1 of 5 does. When was 3.0-M1 released? It takes two clicks to find out. I think dates on the download page http://geronimo.apache.org/downloads.html (the first click) would be nice. 8. There are no news items for the two recent GEP releases: 2.1.6 and 3.0-M1. I think all G and GEP releases should have news items, including dates. I think these suggestions will improve our product. Thanks, Ted Kirby
[jira] Updated: (GERONIMODEVTOOLS-606) Support Eclipse Helios
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-606: --- Description: 1) We need to track the dev progress of eclipse Helios and make GEP 3.0 support Helios 2) GEP 3.0 has to define the new facets in latest WTP to support JavaEE 6 was: 1) We need to track the dev progress of eclipse Halios and make GEP 3.0 support Halios 2) GEP 3.0 has to define the new facets in latest WTP to support JavaEE 6 Summary: Support Eclipse Helios (was: Support Eclipse Halios ) correct spelling of eclipse release: Helios, not Halios Support Eclipse Helios --- Key: GERONIMODEVTOOLS-606 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-606 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0_M1 1) We need to track the dev progress of eclipse Helios and make GEP 3.0 support Helios 2) GEP 3.0 has to define the new facets in latest WTP to support JavaEE 6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Suggestions for improving new G and GEP user experiences
Yes, there are various testsuite options, including os (windows, unix, mac) and 32 v 64 bit. Perhaps ideally it would run on all of them. There are platform differences on the mac. A big one is Eclipse-preferences on mac vs. window-preferences on windows. This affects the testsuite test cases. The testsuite was developed on windows 32. I would say initially running the testsuite on windows 32 is a good start, and probably sufficient, certainly until it works on mac. I am not familiar with SWTBOT. I did some investigation with some knowledgeable folks, and Abbot still seems a reasonable choice. However, I think we are using an older level of Abbot. I think we should upgrade to the latest Abbot levels, which are early 2009, but this is also a future item, I think. If SWTBOT is better or folks want to use it, that seems fine with me. We do have an investment in Abbot for the existing testsuite. See https://cwiki.apache.org/GMOxDEV/geronimo-eclipse-plugin-gep-testsuite.html for testuite info. Ted Kirby On Thu, Nov 4, 2010 at 10:45 AM, Delos dait...@gmail.com wrote: As for testsuite, it's not required before so I agree it's necessary for a new GEP release. But it's difficult to assure the testsuite is runnable all the time, because Abbot always have some unknown issues when it's running on various OS. If possible, maybe we can consider to leverage other library such as SWTBOT. On Thu, Nov 4, 2010 at 8:19 PM, Ted Kirby ted.ki...@gmail.com wrote: I have recently returned to community activity after a period of inactivity. I have played with some of the introductory material, and things have not gone that well. :-( I think G and GEP 3.0 have very exciting content: JEE 6 and OSGi, and we are on track to be early to market with our certified server. I think we want to attract new users, and we want to be ready and attractive and easy to use when they come. To that end, I offer these suggestions and feedback: 1. Geronimo v3.0, or at least v3.0-M1, should be listed on the main page Documentation link http://geronimo.apache.org/documentation.html. v3.0 is on the wiki page: https://cwiki.apache.org/geronimo/ 2. I think we should have a Getting Started or Quick Start link on the home page for folks to download and start running Geronimo quickly. This page in the doc seems good: https://cwiki.apache.org/GMOxDOC30/quick-start-apache-geronimo-for-the-impatient.html. (This page comes up first on the documentation, so maybe item 3 would address this.) 3. I don't think a version should be released unless the Quick Start actually works. If this is the entry point for new users, it should work for each release. For 3.0-M1, there are two JIRAs on this: GERONIMO-5488 and GERONIMO-5658. 4. Ditto for GEP. http://geronimo.apache.org/development-tools.html is pretty good, but there is no mention of 3.0-M1. 3.0 is an exciting release for JEE 6 and OSGi. Folks want to play with the technology. We should help them get started. 5. The 1-minute Hello World Web Application Tutorial http://cwiki.apache.org/GMOxDOC22/how-to-use-geronimo-eclipse-plugin.html#HowtoUseGeronimoEclipsePlugin-DeployRunUndeployandRedeployanApplication for GEP does not work for 3.0-M1. There is a deploy problem, and a missing message problem. I think both the 1-minute and 5-minute tutorial are part of the testsuite, and hence these errors should have been caught if the testsuite were run. I recommend adding these tutorials to the testsuite if they are not there. Again, before a GEP version is released, someone should verify these tutorials work. 6. No GEP version should be released unless the testsuite passes. 7. News items on the main page http://geronimo.apache.org/ should have dates. Currently, 1 of 5 does. When was 3.0-M1 released? It takes two clicks to find out. I think dates on the download page http://geronimo.apache.org/downloads.html (the first click) would be nice. 8. There are no news items for the two recent GEP releases: 2.1.6 and 3.0-M1. I think all G and GEP releases should have news items, including dates. I think these suggestions will improve our product. Thanks, Ted Kirby -- Best Regards, Delos
[jira] Commented: (GERONIMODEVTOOLS-673) Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12924320#action_12924320 ] Ted Kirby commented on GERONIMODEVTOOLS-673: I question this change on two grounds: 1. I get these two errors in eclipse: Description ResourcePathLocationType Unknown extension point: 'org.eclipse.hyades.trace.ui.launchConfigMechanismAssociator' plugin.xml /org.apache.geronimo.st.coreline 178Plug-in Problem Description ResourcePathLocationType Unknown extension point: 'org.eclipse.hyades.trace.ui.launchConfigMechanismAssociator' plugin.xml /org.apache.geronimo.st.v30.coreline 351Plug-in Problem Note the tptp references in org.apache.geronimo.st.core/plugin.xml: extension point=org.eclipse.hyades.trace.ui.launchConfigMechanismAssociator association launchConfigID = org.apache.geronimo.st.core.launchConfigurationType mechanism mechanismID = org.eclipse.tptp.trace.ui.jvmpiMechanism configuration launchDelegate = org.eclipse.tptp.trace.ui.internal.launcher.deleg.application.PIAttachLauncherDelegate configurationId = org.eclipse.tptp.trace.ui.jvmpiConfiguration associatedAgent = org.eclipse.tptp.trace.ui.jvmpiAgent filter = org.eclipse.tptp.platform.profile.server.core.internal.PICollectorFiltration /configuration /mechanism mechanism mechanismID = org.eclipse.tptp.trace.jvmti.jvmtiMechanism configuration launchDelegate = org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIAttachLauncherDelegate configurationId = org.eclipse.tptp.trace.jvmti.tiConfiguration associatedAgent = org.eclipse.tptp.platform.jvmti.TIAgent filter = org.eclipse.tptp.platform.profile.server.core.internal.TICollectorFiltration /configuration /mechanism /association /extension Does org.eclipse.hyades come from TPTP? 2. The test suite fails here: windows: [echo] Launching Equinox with -Dos=win32 -Dws=win32 -Darch=x86 [java] Buildfile: testsuite.xml [java] [java] all: [java] [java] testsuite.v30: [java] [java] junit: [java] [java] init: [java] [java] suite: [java] [mkdir] Created dir: C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\eclipse\e clipse\jdt_folder\src [java] [copy] Copying 36 files to C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\ec lipse\eclipse\jdt_folder\src [java] [java] init: [java] [mkdir] Created dir: C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\results\j unit [java] [java] ui-test: [java] [java] java-test: [java] [echo] Running org.apache.geronimo.testsuite.v30.ui.EclipseUITest. Result file: C:\ svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher/results/junit/org.apache.geronimo.testsuite.v30.u i.EclipseUITest.xml. [java] [java] abbot.swt.finder.generic.NotFoundException [java] [java] at abbot.swt.finder.generic.FinderImpl.found(FinderImpl.java:74) [java] [java] at abbot.swt.finder.generic.FinderImpl.find(FinderImpl.java:65) [java] [java] at org.apache.geronimo.testsuite.common.ui.AbbotHelper.rightClickIte m(AbbotHelper.java:131) [java] [java] at org.apache.geronimo.testsuite.common.ui.ServerTasks.startServer(S erverTasks.java:100) [java] [java] at org.apache.geronimo.testsuite.v30.ui.EclipseUITest.installServer( EclipseUITest.java:94) [java] [java] at org.apache.geronimo.testsuite.v30.ui.EclipseUITest.testEclipseUI( EclipseUITest.java:65) [java] [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [java] [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI mpl.java:39) [java] [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA ccessorImpl.java:25) [java] [java] at java.lang.reflect.Method.invoke(Method.java:597) [java] [java] at junit.framework.TestCase.runTest(TestCase.java:168) [java] [java] at junit.framework.TestCase.runBare(TestCase.java:134) [java] [java] at abbot.swt.junit.extensions.SWTTestCase.runBareWrapper(SWTTestCase .java:278) [java] [java] at abbot.swt.junit.extensions.SWTTestCase.access$2(SWTTestCase.java: 275) [java] [java
[jira] Commented: (GERONIMODEVTOOLS-677) Testsuite not working on Mac cocoa
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12923994#action_12923994
]
Ted Kirby commented on GERONIMODEVTOOLS-677:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=303869 has some info on the
warning:
1. It suggests a jvm arg of -XstartOnFirstThread may be a bypass
2. Apple: Bug ID# 7840189 may fix it.
The bug fixed it for them on Mac OS 10.6 (Snow Leopard).
The bug is in this update:
http://developer.apple.com/library/mac/#releasenotes/CrossPlatform/JavaSnowLeopardUpdate2LeopardUpdate7RN/ResolvedIssues/ResolvedIssues.html#//apple_ref/doc/uid/TP40009967-CH3-DontLinkElementID_28
The update is also Java for Mac OS X 10.5 Update 7, taking java 6 to 1.6.0_20.
I have Leopard (10.5), and java 6 1.6.0_22, and I still have the problem.
However, the good news is that a jvm arg of -XstartOnFirstThread gets past this
problem!
I used it in testsuite/plugins/org.apache.geronimo.testsuite.common/library.xml:
target name=java-test
jvmarg line=${vmargs} ${extraVMargs} *-XstartOnFirstThread*/
This did launch and eclipse instance on my Mac. An initial test failed,
however, since the menus are different on Mac v. Windows. In windows, it's
Help-About Eclipse. On Mac, it's Eclipse-About Eclipse, but I could see the
code open the Apple Icon in top left corner, and just hang, with this error in
testsuite/launcher/results/junit/org.apache.geronimo.testsuite.v30.ui.EclipseUITest.xml:
eclipse.buildId=M20100909-0800
java.version=1.6.0_22
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
Framework arguments: -application org.eclipse.test.uitestapplication
formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/eclipse/eclipse/org.apache.geronimo.testsuite.v30.ui.EclipseUITest.xml
-testPluginName org.apache.geronimo.testsuite.v30 -className
org.apache.geronimo.testsuite.v30.ui.EclipseUITest
Command-line arguments: -application org.eclipse.test.uitestapplication -data
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/eclipse/eclipse/jdt_folder
formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/eclipse/eclipse/org.apache.geronimo.testsuite.v30.ui.EclipseUITest.xml
-testPluginName org.apache.geronimo.testsuite.v30 -className
org.apache.geronimo.testsuite.v30.ui.EclipseUITest -os macosx -ws cocoa -arch
x86_64 -consolelog
!ENTRY org.eclipse.core.net 1 0 2010-10-22 15:37:54.023
!MESSAGE System property http.nonProxyHosts has been set to
local|*.local|169.254/16|*.169.254/16 by an external source. This value will be
overwritten using the values from the preferences
testEclipseUI: Activating Shell {Resource - Eclipse Platform}
initial validation and set up
testEclipseUI: 61.494 sec.
!ENTRY org.eclipse.ui 4 0 2010-10-22 15:39:05.878
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTException: Failed to execute runnable
(abbot.swt.tester.ActionFailedException: java.lang.NoSuchFieldException: menus)
at org.eclipse.swt.SWT.error(SWT.java:4083)
at org.eclipse.swt.SWT.error(SWT.java:3998)
at
org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3586)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3279)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at
org.eclipse.ui.internal.about.AboutHandler.execute(AboutHandler.java:32)
at
org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476)
at
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at
org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169)
at
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241)
at
org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at
org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171)
at
org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runAction(CocoaUIEnhancer.java:416)
at
org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.aboutMenuItemSelected(CocoaUIEnhancer.java:520)
at
org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:540)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at
org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4483
Re: Welcome Janet Hong Fang Han as a new committer
Congratulations Janet! Welcome aboard! Ted On Wed, Oct 20, 2010 at 9:11 PM, Ivan xhh...@gmail.com wrote: I would like to welcome Janet aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (hanhongfang), so you should start seeing some commits from her soon. -- Ivan
[jira] Updated: (GERONIMODEVTOOLS-658) Update maven-eclipsepde-plugin to meet new requirement
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-658: --- Description: update the plugin to accommodate new requirements. 1) Eclipse on Mac There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse 3.6, only cocoa is supported. But maven-eclipsepde-plugin can only recognize carbon eclipse on Mac, so we have to fix it to make GEP build successfully on Mac. You may see details in GERONIMODEVTOOLS-649. 2)Optional bundles There are some optional required bundles in MANIFEST.MF for some extended functions, such as TPTP and Free Aires Tools. They're not mandatory for GEP and actually GEP don't need these bundles in build process. They're marked as optional because user may get these extra plugins by themselves for some advanced functions. So these optional bundles shouldn't block the build process of GEP. Unfortunately, current maven-eclipsepde-plugin does block GEP build process because of these optional bundles. was: update the plugin to accommodate new requirements. 1) Eclipse on Mac There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse 3.6, only cocoa is supported. But maven-eclipsepde-plugin can only recognize carbon eclipse on Mac, so we have to fix it to make GEP build successfully on Mac. You may see details in 2)Optional bundles There are some optional required bundles in MANIFEST.MF for some extended functions, such as TPTP and Free Aires Tools. They're not mandatory for GEP and actually GEP don't need these bundles in build process. They're marked as optional because user may get these extra plugins by themselves for some advanced functions. So these optional bundles shouldn't block the build process of GEP. Unfortunately, current maven-eclipsepde-plugin does block GEP build process because of these optional bundles. Completed last sentence in 1) with what I think is the proper value: GERONIMODEVTOOLS-649. Update maven-eclipsepde-plugin to meet new requirement -- Key: GERONIMODEVTOOLS-658 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 Project: Geronimo-Devtools Issue Type: Improvement Components: maven-eclipsepde-plugin Affects Versions: 2.0.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.0.0, 3.0 update the plugin to accommodate new requirements. 1) Eclipse on Mac There are two edition of eclipse on Mac, carbon and cocoa. From Eclipse 3.6, only cocoa is supported. But maven-eclipsepde-plugin can only recognize carbon eclipse on Mac, so we have to fix it to make GEP build successfully on Mac. You may see details in GERONIMODEVTOOLS-649. 2)Optional bundles There are some optional required bundles in MANIFEST.MF for some extended functions, such as TPTP and Free Aires Tools. They're not mandatory for GEP and actually GEP don't need these bundles in build process. They're marked as optional because user may get these extra plugins by themselves for some advanced functions. So these optional bundles shouldn't block the build process of GEP. Unfortunately, current maven-eclipsepde-plugin does block GEP build process because of these optional bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922148#action_12922148 ] Ted Kirby commented on GERONIMODEVTOOLS-675: for missing 2.1.5 artifacts in my repo, I updated testsuite/pom.xml thusly: -idgeronimo-server-trunk/id -namePrivate Geronimo 2.2 Repo/name - urlhttps://svn.apache.org/repos/asf/geronimo/server/trunk/repository//url +idgeronimo-server-2.1.5/id +namePrivate Geronimo 2.1.5 Repo/name + urlhttps://svn.apache.org/repos/asf/geronimo/server/tags/geronimo-2.1.5/repository//url With rev 1022988, I fixed a bug I introduced in GERONIMODEVTOOLS-599: don't delete test eclipse directory after putting needed stuff in it. GEP TestSuite not working in 3.0 trunk -- Key: GERONIMODEVTOOLS-675 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Ted Kirby Assignee: Delos Dai Fix For: 3.0 ~/svn/gdvtls/eclipse-plugin/trunk $ mvn clean install -Ptestsuite [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.geronimo.devtools:testsuite:pom:3.0.0 Reason: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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.project.ProjectBuildingException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391) ... 12 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.geronimo.devtools:geronimo-eclipse-plugin' not found in repository: Unable to download the artifact from any repository org.apache.geronimo.devtools:geronimo-eclipse-plugin:pom:3.0_M1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), geronimo-server-trunk (https://svn.apache.org/repos/asf/geronimo/server/trunk/repository/), geronimo-server-2.0.2 (https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/) for project org.apache.geronimo.devtools:geronimo-eclipse-plugin
[jira] Updated: (GERONIMODEVTOOLS-599) Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-599: --- Fix Version/s: 3.0 Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes - Key: GERONIMODEVTOOLS-599 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: linux x86_64 Reporter: Johannes Weberhofer Assignee: Tim McConnell Fix For: 3.0 Attachments: gep-x86_64_and_simplifications.patch * Since revision 832984 build on x86_64 systems was broken again. I have fixed the pom.xml file again and replaced i386 architecture by x86; hope, this works on your build environments, too. * simplified the build.xml files by replacing the galileo parameters by a more general eclipse parameter, which makes changes between eclipse releases much easier (changes have to be done in the header sections only). At the same time I have upgraded to galileo version 3.5.1 (SR1) * a bug has been fixed in the testsuite, which made the x86_64 target not to depend on the common target. The testsuite runs much better now on x86_64 (but still produces an error) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-677) Testsuite not working on Mac cocoa
Testsuite not working on Mac cocoa
--
Key: GERONIMODEVTOOLS-677
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-677
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Environment: Mac OS X
Reporter: Ted Kirby
Assignee: Delos Dai
It looks like there is a fatal cocoa restriction currently blocking the
testsuite from running on Mac OS X, based on this message:
***WARNING: Display must be created on main thread due to Cocoa restrictions.
details:
[INFO]
[INFO] Building Geronimo Eclipse Plugin :: Testsuite :: Launcher
[INFO]task-segment: [install]
[INFO]
...
[INFO] [antrun:run {execution: run-testsuite}]
[INFO] Executing tasks
init:
Please install Aries tools manually for eclipse under
testsuite/launcher/eclipse,
Free Aries tools download URL is
http://www.ibm.com/developerworks/rational/downloads/10/rationaldevtoolsforosgiapplications.html
Press Enter to continue...
mac:
[echo] Launching Equinox with -Dos=macosx -Dws=cocoa
[java] Buildfile: testsuite.xml
[java]
[java] all:
[java]
[java] testsuite.v30:
[java]
[java] junit:
[java]
[java] init:
[java]
[java] suite:
[java][delete] Deleting directory
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/eclipse/eclipse/jdt_folder
[java] [mkdir] Created dir:
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/eclipse/eclipse/jdt_folder/src
[java] [copy] Copying 13 files to
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/eclipse/eclipse/jdt_folder/src
[java]
[java] init:
[java]
[java] ui-test:
[java]
[java] java-test:
[java] [echo] Running
org.apache.geronimo.testsuite.v30.ui.aries.NewOSGiBundleTest. Result file:
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/results/junit/org.apache.geronimo.testsuite.v30.ui.aries.NewOSGiBundleTest.xml.
[java]
[java] BUILD FAILED
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/testsuite.xml:72:
The following error occurred while executing this line:
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/testsuite.xml:56:
The following error occurred while executing this line:
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/testsuite.xml:38:
The following error occurred while executing this line:
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/testsuite.xml:46:
The following error occurred while executing this line:
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/eclipse/eclipse/plugins/org.apache.geronimo.testsuite.v30-3.0.0/test.xml:94:
The following error occurred while executing this line:
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/plugins/org.apache.geronimo.testsuite.common/library.xml:74:
The following error occurred while executing this line:
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/plugins/org.apache.geronimo.testsuite.common/library.xml:89:
Java returned: 13
[java]
[java] Total time: 19 seconds
[java] An error has occurred. See the log file
[java]
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/workspace/.metadata/.log.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An Ant BuildException has occured: The following error occurred while
executing this line:
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/build.xml:99:
The following error occurred while executing this line:
/Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/launcher/build.xml:83:
Java returned: 13
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 9 minutes 5 seconds
[INFO] Finished at: Mon Oct 18 11:30:49 EDT 2010
[INFO] Final Memory: 427M/507M
[INFO]
from
testsuite/launcher/results/junit/org.apache.geronimo.testsuite.v30.ui.aries.NewOSGiBundleTest.txt
:
***WARNING: Display must be created on main thread due to Cocoa restrictions.
!SESSION 2010-10-18 11:30:29.172 ---
eclipse.buildId=M20100909-0800
java.version=1.6.0_20
java.vendor=Apple Inc.
BootLoader constants: OS=macosx, ARCH=x86_64
[jira] Commented: (GERONIMODEVTOOLS-599) Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12922152#action_12922152 ] Ted Kirby commented on GERONIMODEVTOOLS-599: fix testsuite launching on 64-bit machines with rev 1023908. Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes - Key: GERONIMODEVTOOLS-599 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: linux x86_64 Reporter: Johannes Weberhofer Assignee: Tim McConnell Fix For: 3.0 Attachments: gep-x86_64_and_simplifications.patch * Since revision 832984 build on x86_64 systems was broken again. I have fixed the pom.xml file again and replaced i386 architecture by x86; hope, this works on your build environments, too. * simplified the build.xml files by replacing the galileo parameters by a more general eclipse parameter, which makes changes between eclipse releases much easier (changes have to be done in the header sections only). At the same time I have upgraded to galileo version 3.5.1 (SR1) * a bug has been fixed in the testsuite, which made the x86_64 target not to depend on the common target. The testsuite runs much better now on x86_64 (but still produces an error) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMODEVTOOLS-637) Implement full testsuite automation on all supported Geronimo runtime platforms (i.e., Windows, Mac, Linux, etc.) and all major usage scenarios
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby reopened GERONIMODEVTOOLS-637: I found more files that were not added before the commit: org.apache.geronimo.testsuite.v30.ui.aries Delos, can you add the proper files in that directory? Thanks, Ted More details from the testsuite build failure: [INFO] Executing tasks init: Please install Aries tools manually for eclipse under testsuite/launcher/eclipse, Free Aries tools download URL is http://www.ibm.com/developerworks/rational/downloads/10/rationaldev toolsforosgiapplications.html Press Enter to continue... windows: [echo] Launching Equinox with -Dos=win32 -Dws=win32 [java] Buildfile: testsuite.xml [java] [java] all: [java] [java] testsuite.v30: [java] [java] junit: [java] [java] init: [java] [java] suite: [java][delete] Deleting directory C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\ecl ipse\eclipse\jdt_folder [java] [mkdir] Created dir: C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\eclipse\e clipse\jdt_folder\src [java] [copy] Copying 13 files to C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\ec lipse\eclipse\jdt_folder\src [java] [java] init: [java] [java] ui-test: [java] [java] java-test: [java] [echo] Running org.apache.geronimo.testsuite.v30.ui.aries.NewOSGiBundleTest. Result file: C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher/results/junit/org.apache.geronimo.tests uite.v30.ui.aries.NewOSGiBundleTest.xml. [java] [java] Class not found org.apache.geronimo.testsuite.v30.ui.aries.NewOSGiBundleTest [java] [java] BUILD FAILED [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\testsuite.xml:72: The following er ror occurred while executing this line: [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\testsuite.xml:56: The following er ror occurred while executing this line: [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\testsuite.xml:38: The following er ror occurred while executing this line: [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\testsuite.xml:46: The following er ror occurred while executing this line: [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\eclipse\eclipse\plugins\org.apache .geronimo.testsuite.v30-3.0.0\test.xml:94: The following error occurred while executing this line: [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\plugins\org.apache.geronimo.testsuite.commo n\library.xml:74: The following error occurred while executing this line: [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\plugins\org.apache.geronimo.testsuite.commo n\library.xml:89: Java returned: 2 [java] [java] Total time: 1 minute 12 seconds [java] An error has occurred. See the log file [java] C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\workspace\.metadata\.log. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: The following error occurred while executing this line: C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\build.xml:92: The following error occurred while executing this line: C:\svn\gdvtls\eclipse-plugin\trunk\testsuite\launcher\build.xml:68: Java returned: 13 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 7 minutes 56 seconds [INFO] Finished at: Fri Oct 15 17:55:15 EDT 2010 [INFO] Final Memory: 260M/622M [INFO] Implement full testsuite automation on all supported Geronimo runtime platforms (i.e., Windows, Mac, Linux, etc.) and all major usage scenarios --- Key: GERONIMODEVTOOLS-637 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-637 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r1022868 - in /geronimo/devtools/eclipse-plugin/branches/2.1.7: eclipse/pom.xml plugins/org.apache.geronimo.runtime.common/pom.xml plugins/org.apache.geronimo.runtime.v21/pom.xml pom.x
Delos,
I know you thanked Hong Fang Han for the patch in the JIRA, but is it
not also the practice to include the thanks in the svn commit log
message? I have been dormant in the community for a while, and need
to get up to speed with current practice.
Thanks,
Ted
On Fri, Oct 15, 2010 at 5:36 AM, de...@apache.org wrote:
Author: delos
Date: Fri Oct 15 09:36:28 2010
New Revision: 1022868
URL: http://svn.apache.org/viewvc?rev=1022868view=rev
Log:
GERONIMODEVTOOLS-676 update version number of dependency and moduels to make
2.1 branch build successfully
Modified:
geronimo/devtools/eclipse-plugin/branches/2.1.7/eclipse/pom.xml
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.common/pom.xml
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.v21/pom.xml
geronimo/devtools/eclipse-plugin/branches/2.1.7/pom.xml
Modified: geronimo/devtools/eclipse-plugin/branches/2.1.7/eclipse/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/branches/2.1.7/eclipse/pom.xml?rev=1022868r1=1022867r2=1022868view=diff
==
--- geronimo/devtools/eclipse-plugin/branches/2.1.7/eclipse/pom.xml (original)
+++ geronimo/devtools/eclipse-plugin/branches/2.1.7/eclipse/pom.xml Fri Oct
15 09:36:28 2010
@@ -21,14 +21,14 @@
groupIdorg.apache.geronimo.devtools/groupId
artifactIdeclipse/artifactId
- version3.0.0/version
+ version2.1.7/version
packagingpom/packaging
nameGeronimo Eclipse Plugin :: Eclipse/name
parent
groupIdorg.apache.geronimo.devtools/groupId
artifactIdgeronimo-eclipse-plugin/artifactId
- version3.0.0-SNAPSHOT/version
+ version2.1.7-SNAPSHOT/version
relativePath../pom.xml/relativePath
/parent
Modified:
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.common/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.common/pom.xml?rev=1022868r1=1022867r2=1022868view=diff
==
---
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.common/pom.xml
(original)
+++
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.common/pom.xml
Fri Oct 15 09:36:28 2010
@@ -190,7 +190,7 @@
dependency
groupIdorg.apache.geronimo.devtools/groupId
artifactIdeclipse/artifactId
- version${version}/version
+ version${pom.version}/version
typepom/type
/dependency
dependency
Modified:
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.v21/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.v21/pom.xml?rev=1022868r1=1022867r2=1022868view=diff
==
---
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.v21/pom.xml
(original)
+++
geronimo/devtools/eclipse-plugin/branches/2.1.7/plugins/org.apache.geronimo.runtime.v21/pom.xml
Fri Oct 15 09:36:28 2010
@@ -27,7 +27,7 @@
relativePath../pom.xml/relativePath
/parent
properties
- geronimoVersion2.1.6/geronimoVersion
+ geronimoVersion2.1.7-SNAPSHOT/geronimoVersion
/properties
build
resources
Modified: geronimo/devtools/eclipse-plugin/branches/2.1.7/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/branches/2.1.7/pom.xml?rev=1022868r1=1022867r2=1022868view=diff
==
--- geronimo/devtools/eclipse-plugin/branches/2.1.7/pom.xml (original)
+++ geronimo/devtools/eclipse-plugin/branches/2.1.7/pom.xml Fri Oct 15
09:36:28 2010
@@ -263,7 +263,7 @@
plugin
groupIdorg.apache.geronimo.devtools/groupId
artifactIdmaven-eclipsepde-plugin/artifactId
- version1.0/version
+ version1.1/version
configuration
eclipseHome${settings.localRepository}/eclipse/eclipse//eclipseHome
/configuration
Re: windows build problem with trunk Plugins, BVal :: Core
Thanks Kevan. I did try the build with JRE 1.6.0 IBM Windows 32 build
pwi3260sr8fp1-20100624_01 (SR8 FP1), and think I got past this
problem. I got out of memory:
[INFO]
[INFO] Building Geronimo Plugins, Connector 1.6 :: Builder
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set:
C:\svn\g\trunk\plugins\connector-1_6\geronimo-connector-builder-1_6\target
(included: [**], excluded: [])
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [geronimo-property:set-property {execution: set-property}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
Time to build schema type system: 0.921 seconds
Time to generate code: 9.844 seconds
JVMDUMP006I Processing dump event systhrow, detail
java/lang/OutOfMemoryError - please wait.
JVMDUMP032I JVM requested Snap dump using
'C:\svn\g\trunk\Snap.20101015.111238.8152.0001.trc' in res
ponse to an event
JVMDUMP010I Snap dump written to
C:\svn\g\trunk\Snap.20101015.111238.8152.0001.trc
JVMDUMP032I JVM requested Heap dump using
'C:\svn\g\trunk\heapdump.20101015.111238.8152.0002.phd' in
response to an event
JVMDUMP010I Heap dump written to
C:\svn\g\trunk\heapdump.20101015.111238.8152.0002.phd
JVMDUMP032I JVM requested Java dump using
'C:\svn\g\trunk\javacore.20101015.111238.8152.0003.txt' in
response to an event
JVMDUMP010I Java dump written to
C:\svn\g\trunk\javacore.20101015.111238.8152.0003.txt
JVMDUMP013I Processed dump event systhrow, detail
java/lang/OutOfMemoryError.
java.lang.OutOfMemoryError: Failed to create a thread: retVal
-1073741830, errno 12
null
java.lang.OutOfMemoryError: Failed to create a thread: retVal
-1073741830, errno 12
I was using MAVEN_OPTS=-Xmx1500m -XX:MaxPermSize=512m
I then went back to the Sun JDK and the build ran successfully with
MAVEN_OPTS=-Xmx1024m -Xms256m -XX:PermSize=64m -XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
On Thu, Oct 14, 2010 at 11:14 PM, Kevan Miller kevan.mil...@gmail.com wrote:
On Oct 14, 2010, at 7:48 PM, Ted Kirby wrote:
Thanks Shawn and Janet. I switched to Sun JDK, and not only got by
this problem, but, after a couple others, I got a successful build!
WooHoo!
I was getting the error with JRE 1.6.0 IBM Windows 32 build
pwi3260sr7-20091217_01 (SR7). Do we support building only with Sun
JDK?
Umm. No. I can't think why we'd say that. Would seem there are two
possibilities:
1) IBM JDK has more strict validation and we should fix our source (I'm not
sure if Shawn and Janet are using Sun or IBM JDK), or
2) There's a compiler bug
Google 'inconvertible types' and you'll get a number of hits for compiler
bugs in this area. Your IBM JDK is nearly a year old. I'd guess there's a
decent chance that upgrading would fix your problem.
--kevan
trunk build problem: out of space in CodeCache for adapters
Revision: 1022182
Sun JDK
[INFO]
[INFO] Building Geronimo Build Support :: Plugin
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [groovy:compile {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] out of space in CodeCache for adapters
[INFO]
trunk build problem: Failed to resolve artifact. org.apache.geronimo.components:geronimo-connector:jar:3.1-20101008.144555-2
from plugins\connector-1_6 [INFO] [INFO] Building Geronimo Plugins, Connector 1.6 :: Connector wrappers [INFO]task-segment: [clean, install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Error transferring file: Server returned HTTP response code: 502 for URL: http://repository.apache.o rg/snapshots/org/apache/geronimo/components/geronimo-connector/3.1-SNAPSHOT/geronimo-connector-3.1-2 0101008.144555-2.jar org.apache.geronimo.components:geronimo-connector:jar:3.1-20101008.144555-2 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), central (http://repo1.maven.org/maven2), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), java.net (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) Path to dependency: 1) org.apache.geronimo.modules:geronimo-connector-1_6:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-connector:jar:3.1-SNAPSHOT any ideas? Thanks, Ted
Re: trunk build problem: Failed to resolve artifact. org.apache.geronimo.components:geronimo-connector:jar:3.1-20101008.144555-2
I retried the build about an hour later, and it ran. I am happy to have a succesful g3 build now! On Thu, Oct 14, 2010 at 2:26 PM, Ted Kirby ted.ki...@gmail.com wrote: from plugins\connector-1_6 [INFO] [INFO] Building Geronimo Plugins, Connector 1.6 :: Connector wrappers [INFO] task-segment: [clean, install] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Error transferring file: Server returned HTTP response code: 502 for URL: http://repository.apache.o rg/snapshots/org/apache/geronimo/components/geronimo-connector/3.1-SNAPSHOT/geronimo-connector-3.1-2 0101008.144555-2.jar org.apache.geronimo.components:geronimo-connector:jar:3.1-20101008.144555-2 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org), central (http://repo1.maven.org/maven2), openqa-snapshots (http://nexus.openqa.org/content/repositories/snapshots), java.net (http://download.java.net/maven/1/), jetty.oss.sonatype.org (http://oss.sonatype.org/content/repositories/jetty/), openqa-releases (http://nexus.openqa.org/content/repositories/releases), smx.svn (http://svn.apache.org/repos/asf/servicemix/m2-repo/) Path to dependency: 1) org.apache.geronimo.modules:geronimo-connector-1_6:bundle:3.0-SNAPSHOT 2) org.apache.geronimo.components:geronimo-connector:jar:3.1-SNAPSHOT any ideas? Thanks, Ted
Re: windows build problem with trunk Plugins, BVal :: Core
Thanks Shawn and Janet. I switched to Sun JDK, and not only got by this problem, but, after a couple others, I got a successful build! WooHoo! I was getting the error with JRE 1.6.0 IBM Windows 32 build pwi3260sr7-20091217_01 (SR7). Do we support building only with Sun JDK? On Thu, Oct 14, 2010 at 2:06 AM, han hongfang hanhongf...@gmail.com wrote: I successfully built trunk on windows XP SP3 with JDK 1.6.0_20 this Turesday (on Revision: 1021600). -- Best regards, Han Hong Fang
windows build problem with trunk Plugins, BVal :: Core
my trunk build is fine on the mac, but I keep getting this failure on windows:
[INFO]
[INFO] Building Geronimo Plugins, BVal :: Core
[INFO]task-segment: [clean, install]
[INFO]
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 3 source files to
C:\svn\g\trunk\plugins\bval\geronimo-bval\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\svn\g\trunk\plugins\bval\geronimo-bval\src\main\java\org\apache\geronimo\bval\ValidatorFactoryGBean.java:[132,103]
inconvertible types
found : javax.validation.Configurationcapture#320 of ?
required: org.apache.bval.jsr303.ConfigurationImpl
I get the failure after I cleaned out my local repo. Any help would
be appreciated.
I am on rev 1022066 in trunk.
Ted Kirby
[jira] Commented: (GERONIMODEVTOOLS-599) Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12920366#action_12920366 ] Ted Kirby commented on GERONIMODEVTOOLS-599: with rev 1021938, I finished off my reworked version of Johannes enhancements with the testsuite pieces: Call /eclipse/build.xml to get eclipse, don't replicate its code in /testsuite/eclipse/build.xml Simplify /testsuite/eclipse/pom.xml by having ant os family determine environment, don't need maven to. Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes - Key: GERONIMODEVTOOLS-599 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: linux x86_64 Reporter: Johannes Weberhofer Assignee: Tim McConnell Attachments: gep-x86_64_and_simplifications.patch * Since revision 832984 build on x86_64 systems was broken again. I have fixed the pom.xml file again and replaced i386 architecture by x86; hope, this works on your build environments, too. * simplified the build.xml files by replacing the galileo parameters by a more general eclipse parameter, which makes changes between eclipse releases much easier (changes have to be done in the header sections only). At the same time I have upgraded to galileo version 3.5.1 (SR1) * a bug has been fixed in the testsuite, which made the x86_64 target not to depend on the common target. The testsuite runs much better now on x86_64 (but still produces an error) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919889#action_12919889 ] Ted Kirby commented on GERONIMODEVTOOLS-675: I tried: mvn dependency:purge-local-repository but that did not help. mvn dependency:list did not work either. Need to find those artifacts. The problem seems to be with: org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.4 That is an old level. What levels of g should we be using? A search on geronimoVersion in the poms shows: plugins/org.apache.geronimo.runtime.v11/pom.xml: geronimoVersion1.1.1/geronimoVersion plugins/org.apache.geronimo.runtime.v20/pom.xml: geronimoVersion2.0.2/geronimoVersion plugins/org.apache.geronimo.runtime.v21/pom.xml: geronimoVersion2.1.5/geronimoVersion plugins/org.apache.geronimo.runtime.v22/pom.xml: geronimoVersion2.2/geronimoVersion plugins/org.apache.geronimo.runtime.v30/pom.xml: geronimoVersion3.0-M1/geronimoVersion testsuite/pom.xml:geronimoVersion_13.0-SNAPSHOT/geronimoVersion_1 testsuite/pom.xml:geronimoVersion_22.2.1-SNAPSHOT/geronimoVersion_2 testsuite/pom.xml:geronimoVersion_32.1.4/geronimoVersion_3 testsuite/pom.xml:geronimoVersion_42.0.2/geronimoVersion_4 testsuite/server/pom.xml:property name=geronimoVersion_1 value=3.0-SNAPSHOT/ testsuite/server/pom.xml:property name=geronimoVersion_2 value=2.2.1-SNAPSHOT/ testsuite/server/pom.xml:property name=geronimoVersion_3 value=2.1.4/ testsuite/server/pom.xml:property name=geronimoVersion_4 value=2.0.2/ I am trying a testsuite run upgrading it from 2.1.4 to 2.1.5. Since 2.1.6 is out, it seems we should upgrade to that level. What about the plugin/testsuite discrepancy for 2.2 and 3.0? GEP TestSuite not working in 3.0 trunk -- Key: GERONIMODEVTOOLS-675 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Ted Kirby Assignee: Delos Dai Fix For: 3.0 ~/svn/gdvtls/eclipse-plugin/trunk $ mvn clean install -Ptestsuite [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.geronimo.devtools:testsuite:pom:3.0.0 Reason: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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.project.ProjectBuildingException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508) at org.apache.maven.project.DefaultMavenProjectBuilder.build
[jira] Commented: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919901#action_12919901 ] Ted Kirby commented on GERONIMODEVTOOLS-675: using 2.1.5 gives these missing artifacts: 1) org.directwebremoting:dwr:jar:2.0.5 2) org.apache.activemq:activemq-core:jar:4.1.2-G20100308 3) org.apache.axis2:axis2-jaxws:jar:1.3-G20090406 4) org.apache.axis2:axis2-kernel:jar:1.3-G20090406 5) org.apache.axis2:axis2-metadata:jar:1.3-G20090406 6) org.apache.axis2:axis2-saaj:jar:1.3-G20090406 Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.5 I downloaded and installed/extracted g2.1.5, and manually installed the artifacts, and I think I got past all the missing artifact messages. GEP TestSuite not working in 3.0 trunk -- Key: GERONIMODEVTOOLS-675 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Ted Kirby Assignee: Delos Dai Fix For: 3.0 ~/svn/gdvtls/eclipse-plugin/trunk $ mvn clean install -Ptestsuite [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.geronimo.devtools:testsuite:pom:3.0.0 Reason: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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.project.ProjectBuildingException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391) ... 12 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.geronimo.devtools:geronimo-eclipse-plugin' not found in repository: Unable to download the artifact from any repository org.apache.geronimo.devtools:geronimo-eclipse-plugin:pom:3.0_M1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), geronimo-server-trunk (https://svn.apache.org/repos/asf/geronimo/server/trunk/repository/), geronimo-server-2.0.2 (https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/) for project org.apache.geronimo.devtools:geronimo-eclipse-plugin
[jira] Commented: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919984#action_12919984 ] Ted Kirby commented on GERONIMODEVTOOLS-675: eclipse-test-framework.zip URL apparently changed, so I changed the URL to one that works, so the zip can be found and downloaded from the web, in rev 1021504. The next issue is then: [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: The following error occurred while executing this line: /Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/eclipse/build.xml:171: The following error occurred while executing this line: /Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/eclipse/build.xml:246: Warning: Could not find file /Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/eclipse/metadata_abbot_swt/MANIFEST.MF to copy. I think Delos forgot to add this directory to svn before his checkin for GERONIMODEVTOOLS-637. GEP TestSuite not working in 3.0 trunk -- Key: GERONIMODEVTOOLS-675 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Ted Kirby Assignee: Delos Dai Fix For: 3.0 ~/svn/gdvtls/eclipse-plugin/trunk $ mvn clean install -Ptestsuite [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.geronimo.devtools:testsuite:pom:3.0.0 Reason: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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.project.ProjectBuildingException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391) ... 12 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.geronimo.devtools:geronimo-eclipse-plugin' not found in repository: Unable to download the artifact from any repository org.apache.geronimo.devtools:geronimo-eclipse-plugin:pom:3.0_M1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), geronimo-server-trunk (https://svn.apache.org/repos/asf/geronimo/server
[jira] Commented: (GERONIMODEVTOOLS-637) Implement full testsuite automation on all supported Geronimo runtime platforms (i.e., Windows, Mac, Linux, etc.) and all major usage scenarios
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919987#action_12919987 ] Ted Kirby commented on GERONIMODEVTOOLS-637: I get: [ERROR] BUILD ERROR [INFO] [INFO] An Ant BuildException has occured: The following error occurred while executing this line: /Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/eclipse/build.xml:171: The following error occurred while executing this line: /Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/eclipse/build.xml:246: Warning: Could not find file /Users/tedkirby/svn/gdvtls/eclipse-plugin/trunk/testsuite/eclipse/metadata_abbot_swt/MANIFEST.MF to copy. I think Delos forgot to add this directory to svn before his checkin, as noted in GERONIMODEVTOOLS-675. Implement full testsuite automation on all supported Geronimo runtime platforms (i.e., Windows, Mac, Linux, etc.) and all major usage scenarios --- Key: GERONIMODEVTOOLS-637 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-637 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: java.lang.OutOfMemoryError: PermGen space
I recently updated https://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html for this to say: For 3.0, use at least: MAVEN_OPTS=-Xmx768m -XX:MaxPermSize=200m On Sun, Oct 10, 2010 at 8:50 AM, Ivan xhh...@gmail.com wrote: How about using more bigger memory size for those parameters, like use -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512m. ? 2010/10/10 mohamed.chebbi mhmdche...@gmail.com the revision is : Revision 1006251 - best reguards -- View this message in context: http://apache-geronimo.328035.n3.nabble.com/java-lang-OutOfMemoryError-PermGen-space-tp1673175p1673186.html Sent from the Development mailing list archive at Nabble.com. -- Ivan
[jira] Commented: (GERONIMODEVTOOLS-599) Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919318#action_12919318 ] Ted Kirby commented on GERONIMODEVTOOLS-599: I simplified further by reworking build.xml using conditional property settings. I simplified pom.xml by having ant os family determine environment, don't need maven to. Rev 1005892. Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes - Key: GERONIMODEVTOOLS-599 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: linux x86_64 Reporter: Johannes Weberhofer Assignee: Tim McConnell Attachments: gep-x86_64_and_simplifications.patch * Since revision 832984 build on x86_64 systems was broken again. I have fixed the pom.xml file again and replaced i386 architecture by x86; hope, this works on your build environments, too. * simplified the build.xml files by replacing the galileo parameters by a more general eclipse parameter, which makes changes between eclipse releases much easier (changes have to be done in the header sections only). At the same time I have upgraded to galileo version 3.5.1 (SR1) * a bug has been fixed in the testsuite, which made the x86_64 target not to depend on the common target. The testsuite runs much better now on x86_64 (but still produces an error) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-649) Can't build GEP trunk on 32-bit Mac
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12918934#action_12918934 ] Ted Kirby commented on GERONIMODEVTOOLS-649: I tried to build on Mac yesterday, and had issues, like you describe. I fixed it in trunk with GERONIMODEVTOOLS-674, before I found this JIRA. In 674, I upgraded to Helios SR1, and allowed for 32 and 64 bit mac versions, including a tweak to maven-eclipsepde-plugin. To build, extract and build geronimo/devtools/maven-plugins/trunk with mvn clean install. This will put version 1.2-SNAPSHOT of the maven-eclipsepde-plugin in your repo, which the subsequent build of the gep can use to build on mac with Helios SR1. Can't build GEP trunk on 32-bit Mac Key: GERONIMODEVTOOLS-649 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-649 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0_M1, 3.0 Attachments: maven-eclipsepde-plugin-2.0.jar Need to update eclipse/build.xml to make GEP build successfully on 32-bit Mac. Eclipse 3.6 has dropped support for Mac carbon. The script should change to Mac cocoa. From Donald, Could not build on MacOSX, as the referenced file no longer exists - file=/technology/epp/downloads/release/helios/R/eclipse-jee-helios-macosx-carbon.tar.gz Looks like we need to use the following 32bit Mac download instead in eclipse/build.xml - property name=helios_jee_macos value=eclipse-jee-helios-macosx-cocoa.tar/ property name=helios_jee_macos-x86_64 value=eclipse-jee-helios-macosx-cocoa-x86_64.tar/ Also, I had to specify specific mirrors to use (like AWS) as the local mirror didn't have the Helios files on it yet -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
GEP TestSuite not working in 3.0 trunk -- Key: GERONIMODEVTOOLS-675 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Ted Kirby Assignee: Delos Dai Fix For: 3.0 ~/svn/gdvtls/eclipse-plugin/trunk $ mvn clean install -Ptestsuite [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.geronimo.devtools:testsuite:pom:3.0.0 Reason: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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.project.ProjectBuildingException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391) ... 12 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.geronimo.devtools:geronimo-eclipse-plugin' not found in repository: Unable to download the artifact from any repository org.apache.geronimo.devtools:geronimo-eclipse-plugin:pom:3.0_M1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), geronimo-server-trunk (https://svn.apache.org/repos/asf/geronimo/server/trunk/repository/), geronimo-server-2.0.2 (https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/) for project org.apache.geronimo.devtools:geronimo-eclipse-plugin at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392) ... 19 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.geronimo.devtools:geronimo-eclipse-plugin:pom:3.0_M1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), geronimo-server-trunk (https://svn.apache.org/repos/asf/geronimo/server/trunk/repository/), geronimo-server-2.0.2 (https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve
[jira] Commented: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919025#action_12919025 ] Ted Kirby commented on GERONIMODEVTOOLS-675: In rev 1005580, I got a *lot* further. There, I tweaked a couple of pom versions to get things rolling. Now, I get missing artifacts. On the Mac, I get 7 missing artifacts: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.directwebremoting:dwr:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.directwebremoting -DartifactId=dwr -Dversion=2.0.5 -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.directwebremoting -DartifactId=dwr -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.4 3) org.apache.geronimo.plugins:console-tomcat:car:2.1.4 4) org.directwebremoting:dwr:jar:2.0.5 2) org.apache.axis2:axis2-jaxws:jar:1.3-G20090325 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-jaxws -Dversion=1.3-G20090325 -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.axis2 -DartifactId=axis2-jaxws -Dversion=1.3-G20090325 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.4 3) org.apache.geronimo.configs:axis2:car:2.1.4 4) org.apache.axis2:axis2-jaxws:jar:1.3-G20090325 3) org.apache.activemq:activemq-core:jar:4.1.2-G20090207 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.activemq -DartifactId=activemq-core -Dversion=4.1.2-G20090207 -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.activemq -DartifactId=activemq-core -Dversion=4.1.2-G20090207 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.4 3) org.apache.geronimo.configs:activemq-broker:car:2.1.4 4) org.apache.activemq:activemq-core:jar:4.1.2-G20090207 4) org.apache.axis2:axis2-kernel:jar:1.3-G20090325 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.axis2 -DartifactId=axis2-kernel -Dversion=1.3-G20090325 -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.axis2 -DartifactId=axis2-kernel -Dversion=1.3-G20090325 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.4 3) org.apache.geronimo.configs:axis2:car:2.1.4 4) org.apache.axis2:axis2-kernel:jar:1.3-G20090325 5) org.apache.tomcat:jasper-el:jar:6.0.18-G678601 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.tomcat -DartifactId=jasper-el -Dversion=6.0.18-G678601 -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.tomcat -DartifactId=jasper-el -Dversion=6.0.18-G678601 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.4 3) org.apache.geronimo.configs:jasper:car:2.1.4 4) org.apache.tomcat:jasper-el:jar:6.0.18-G678601 6) org.apache.axis2:axis2-metadata:jar:1.3-G20090325 Try downloading the file manually from the project website. Then, install it using
[jira] Commented: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919030#action_12919030 ] Ted Kirby commented on GERONIMODEVTOOLS-675: On windows, 18 required artifacts are missing: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Missing: -- 1) org.directwebremoting:dwr:jar:2.0.5 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.directwebremoting -DartifactId=dwr -Dversion=2.0.5 -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.directwebremoting -DartifactId=dwr -Dversion=2.0.5 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.1.4 3) org.apache.geronimo.plugins:console-tomcat:car:2.1.4 4) org.directwebremoting:dwr:jar:2.0.5 2) org.apache.aries.application:org.apache.aries.application.utils:jar:0.2-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries.application -DartifactId=org.apache.aries.application.utils -Dversion=0.2-incubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.aries.application -DartifactId=org.apache.aries.application.utils -Dversion=0.2-incubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT 3) org.apache.geronimo.plugingroups:javaee6-tomcat:car:3.0-SNAPSHOT 4) org.apache.geronimo.plugingroups:javaee6-web-tomcat:car:3.0-SNAPSHOT 5) org.apache.geronimo.plugingroups:eba-tomcat:car:3.0-SNAPSHOT 6) org.apache.geronimo.configs:aries-deployer:car:3.0-SNAPSHOT 7) org.apache.geronimo.modules:geronimo-aries-builder:jar:3.0-SNAPSHOT 8) org.apache.aries.application:org.apache.aries.application.utils:jar:0.2-incubating-SNAPSHOT 3) org.apache.aries:org.apache.aries.util:jar:0.2-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.2-incubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.aries -DartifactId=org.apache.aries.util -Dversion=0.2-incubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT 3) org.apache.geronimo.plugingroups:javaee6-tomcat:car:3.0-SNAPSHOT 4) org.apache.geronimo.plugingroups:javaee6-web-tomcat:car:3.0-SNAPSHOT 5) org.apache.geronimo.framework.plugingroups:framework:car:3.0-SNAPSHOT 6) org.apache.geronimo.framework:karaf-framework:car:3.0-SNAPSHOT 7) org.apache.aries:org.apache.aries.util:jar:0.2-incubating-SNAPSHOT 4) org.apache.aries.jpa:org.apache.aries.jpa.container:jar:0.2-incubating-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.aries.jpa -DartifactId=org.apache.aries.jpa.container -Dversion=0.2-incubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.aries.jpa -DartifactId=org.apache.aries.jpa.container -Dversion=0.2-incubating-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.devtools:testsuite:pom:3.0.0 2) org.apache.geronimo.assemblies:geronimo-tomcat7-javaee6:zip:bin:3.0-SNAPSHOT 3) org.apache.geronimo.plugingroups:javaee6-tomcat:car:3.0-SNAPSHOT 4) org.apache.geronimo.plugingroups:javaee6-web-tomcat:car:3.0-SNAPSHOT 5) org.apache.geronimo.plugingroups:eba-tomcat:car:3.0-SNAPSHOT 6) org.apache.geronimo.plugingroups:persistence:car:3.0-SNAPSHOT
[jira] Commented: (GERONIMODEVTOOLS-599) Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919137#action_12919137 ] Ted Kirby commented on GERONIMODEVTOOLS-599: I liked your build.xml simplifications, Johannes. I was inspired to extend your ideas and refactor the code so common code only appears once. I think we'll have to tweak it to account for some minor differences between initial major eclipse releases and the subsequent SRn releases, but I think we have an improved version that will make this much easier. See my changes in rev 1005697. I think Delos did your pom changes in GERONIMODEVTOOLS-600, with his excellent sun.arch.data.model work. I also want to apply this build.xml rework to testsuite/eclipse/build.xml, as you suggested, but I want to get the testsuite build to work for me first. I am missing some artifacts as noted in GERONIMODEVTOOLS-675. Thanks again for the patch Johannes. Compilation on x86_64 systems, simplifications of the build.xml files, Eclipse 3.5.1, testsuite fixes - Key: GERONIMODEVTOOLS-599 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-599 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.0 Environment: linux x86_64 Reporter: Johannes Weberhofer Assignee: Tim McConnell Attachments: gep-x86_64_and_simplifications.patch * Since revision 832984 build on x86_64 systems was broken again. I have fixed the pom.xml file again and replaced i386 architecture by x86; hope, this works on your build environments, too. * simplified the build.xml files by replacing the galileo parameters by a more general eclipse parameter, which makes changes between eclipse releases much easier (changes have to be done in the header sections only). At the same time I have upgraded to galileo version 3.5.1 (SR1) * a bug has been fixed in the testsuite, which made the x86_64 target not to depend on the common target. The testsuite runs much better now on x86_64 (but still produces an error) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-675) GEP TestSuite not working in 3.0 trunk
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12919145#action_12919145 ] Ted Kirby commented on GERONIMODEVTOOLS-675: my difference between windows and mac is that I have built g trunk on mac, not windows. GEP TestSuite not working in 3.0 trunk -- Key: GERONIMODEVTOOLS-675 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-675 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Ted Kirby Assignee: Delos Dai Fix For: 3.0 ~/svn/gdvtls/eclipse-plugin/trunk $ mvn clean install -Ptestsuite [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.geronimo.devtools:testsuite:pom:3.0.0 Reason: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:404) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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.project.ProjectBuildingException: Cannot find parent: org.apache.geronimo.devtools:geronimo-eclipse-plugin for project: org.apache.geronimo.devtools:testsuite:pom:3.0.0 for project org.apache.geronimo.devtools:testsuite:pom:3.0.0 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:508) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:604) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:487) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:560) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391) ... 12 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'org.apache.geronimo.devtools:geronimo-eclipse-plugin' not found in repository: Unable to download the artifact from any repository org.apache.geronimo.devtools:geronimo-eclipse-plugin:pom:3.0_M1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), geronimo-server-trunk (https://svn.apache.org/repos/asf/geronimo/server/trunk/repository/), geronimo-server-2.0.2 (https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/) for project org.apache.geronimo.devtools:geronimo-eclipse-plugin at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:605) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392) ... 19 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.geronimo.devtools:geronimo-eclipse-plugin:pom:3.0_M1-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), geronimo
duplicate project names importing g into eclipse
I have successfully built g trunk, and am following these instructions: https://cwiki.apache.org/confluence/display/GMOxDEV/Developing+Geronimo+in+Eclipse to import into eclipse. I did mvn eclipse:eclipse. I got errors when importing all the projects from g trunk into eclipse. These projects occur twice: client console-jetty console-tomcat They exist in plugingroups, and in the plugins directory. So, each is a group name that also contains a plugin with the same name. Should I open a JIRA for this? I could update the wiki page to say not to include those plugingroup projects. Thanks, Ted Kirby
[jira] Created: (GERONIMODEVTOOLS-674) Upgrade eclipse to Helios SR1
Upgrade eclipse to Helios SR1 - Key: GERONIMODEVTOOLS-674 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0_M1 Environment: all Reporter: Ted Kirby Assignee: Delos Dai Fix For: 3.0_M1 Helios has now released SR1, and the base releases are no longer available. I have upgraded build.xml to SR1. I also made macos 32 and 64 bit aware, like windows and linux -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-674) Upgrade eclipse to Helios SR1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby reassigned GERONIMODEVTOOLS-674: -- Assignee: Ted Kirby (was: Delos Dai) Upgrade eclipse to Helios SR1 - Key: GERONIMODEVTOOLS-674 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0_M1 Environment: all Reporter: Ted Kirby Assignee: Ted Kirby Fix For: 3.0_M1 Helios has now released SR1, and the base releases are no longer available. I have upgraded build.xml to SR1. I also made macos 32 and 64 bit aware, like windows and linux -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-674) Upgrade eclipse to Helios SR1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12918750#action_12918750 ] Ted Kirby commented on GERONIMODEVTOOLS-674: I needed to update maven-eclipsepde-plugin to make macos 64 bit aware, like win and linux. I thus upgraded the gep version of maven-eclipsepde-plugin to 1.2-SNAPSHOT to use it. Upgrade eclipse to Helios SR1 - Key: GERONIMODEVTOOLS-674 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0_M1 Environment: all Reporter: Ted Kirby Assignee: Ted Kirby Fix For: 3.0_M1 Helios has now released SR1, and the base releases are no longer available. I have upgraded build.xml to SR1. I also made macos 32 and 64 bit aware, like windows and linux -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [ANNOUNCE] Congrats Donald Woods! New ASF Member
Congrats!! On Sun, May 2, 2010 at 9:28 AM, Kevan Miller kevan.mil...@gmail.com wrote: Wanted to let the Geronimo community know that Donald Woods is a new member of the ASF. The ASF membership elected Donald in recognition of his many contributions to Geronimo, OpenJPA, and Incubator projects. Congrats to Donald on this well deserved achievement! --kevan
[jira] Updated: (GERONIMODEVTOOLS-601) Module config Id not found for undeployment
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-601: --- Attachment: eclipselog Thanks Delos. I attached my log. I will try on other OSes. Module config Id not found for undeployment --- Key: GERONIMODEVTOOLS-601 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-601 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: MacOS eclipse, Galileo SR1, Eclipse Java EE IDE for Web Developers, Build id: 20090902-1017 I am running in a Mac with this java: java -version java version 1.6.0_17 Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode) Reporter: Ted Kirby Assignee: Delos Dai Priority: Minor Attachments: eclipselog, GetnStarted3AG.tar.gz, GetnStarted3AG.zip I have created a dynamic web project and it seems to work fine. I can deploy and use the war file, and it gets republished if I change source. However, on every deploy/republish, I get this error in eclipse: Module config Id not found for undeployment java.lang.NullPointerException at org.apache.geronimo.st.core.jaxb.JAXBUtils.unmarshalFilterDeploymentPlan(JAXBUtils.java:126) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:236) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:199) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:179) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getConfigId(GeronimoV21Utils.java:119) at org.apache.geronimo.st.v21.core.GeronimoV21VersionHandler.getConfigID(GeronimoV21VersionHandler.java:36) at org.apache.geronimo.st.core.commands.UndeployCommand.execute(UndeployCommand.java:53) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.unDeploy(GeronimoServerBehaviourDelegate.java:740) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doRemoved(GeronimoServerBehaviourDelegate.java:666) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:451) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:273) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) If I export the project as a war file, and deploy it to geronimo, I don't get the error, so I suspect it's a GEP problem. Here is my geronimo-web.xml file: ?xml version=1.0 encoding=UTF-8? web:web-app xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; xmlns:client=http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0; xmlns:conn=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:ejb=http://openejb.apache.org/xml/ns/openejb-jar-2.2; xmlns:log=http://geronimo.apache.org/xml/ns/loginconfig-2.0; xmlns:name=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pers=http://java.sun.com/xml/ns/persistence; xmlns:pkgen=http://openejb.apache.org/xml/ns/pkgen-2.1; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1; dep:environment dep:moduleId dep:groupIdcom.ibm.websphere.xs.sample/dep:groupId dep:artifactIdGettnStarted3/dep:artifactId dep:version1.0/dep:version dep:typejar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdcom.ibm.websphere.xs/dep:groupId dep:artifactIdogclient/dep:artifactId
[jira] Updated: (GERONIMODEVTOOLS-601) Module config Id not found for undeployment
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-601: --- Attachment: GetnStarted3AG.tar.gz :-( Thanks for trying. Here is my latest project. Can you try it? I am changing jsp and java classes, not geronimo-web.xml or web.xml. If you don't see problem on this latest project version, then I guess it's just my environment. :-( I'll have to see if I can get further info. Thanks. Module config Id not found for undeployment --- Key: GERONIMODEVTOOLS-601 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-601 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: MacOS eclipse, Galileo SR1, Eclipse Java EE IDE for Web Developers, Build id: 20090902-1017 I am running in a Mac with this java: java -version java version 1.6.0_17 Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode) Reporter: Ted Kirby Assignee: Delos Dai Priority: Minor Attachments: GetnStarted3AG.tar.gz, GetnStarted3AG.zip I have created a dynamic web project and it seems to work fine. I can deploy and use the war file, and it gets republished if I change source. However, on every deploy/republish, I get this error in eclipse: Module config Id not found for undeployment java.lang.NullPointerException at org.apache.geronimo.st.core.jaxb.JAXBUtils.unmarshalFilterDeploymentPlan(JAXBUtils.java:126) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:236) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:199) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:179) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getConfigId(GeronimoV21Utils.java:119) at org.apache.geronimo.st.v21.core.GeronimoV21VersionHandler.getConfigID(GeronimoV21VersionHandler.java:36) at org.apache.geronimo.st.core.commands.UndeployCommand.execute(UndeployCommand.java:53) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.unDeploy(GeronimoServerBehaviourDelegate.java:740) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doRemoved(GeronimoServerBehaviourDelegate.java:666) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:451) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:273) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) If I export the project as a war file, and deploy it to geronimo, I don't get the error, so I suspect it's a GEP problem. Here is my geronimo-web.xml file: ?xml version=1.0 encoding=UTF-8? web:web-app xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; xmlns:client=http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0; xmlns:conn=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:ejb=http://openejb.apache.org/xml/ns/openejb-jar-2.2; xmlns:log=http://geronimo.apache.org/xml/ns/loginconfig-2.0; xmlns:name=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pers=http://java.sun.com/xml/ns/persistence; xmlns:pkgen=http://openejb.apache.org/xml/ns/pkgen-2.1; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1; dep:environment dep:moduleId dep:groupIdcom.ibm.websphere.xs.sample/dep:groupId dep:artifactIdGettnStarted3/dep:artifactId dep:version1.0/dep:version dep:typejar/dep:type
[jira] Created: (GERONIMODEVTOOLS-601) Module config Id not found for undeployment
Module config Id not found for undeployment --- Key: GERONIMODEVTOOLS-601 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-601 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: MacOS eclipse, Galileo SR1, Eclipse Java EE IDE for Web Developers, Build id: 20090902-1017 I am running in a Mac with this java: java -version java version 1.6.0_17 Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode) Reporter: Ted Kirby Assignee: Tim McConnell Priority: Minor I have created a dynamic web project and it seems to work fine. I can deploy and use the war file, and it gets republished if I change source. However, on every deploy/republish, I get this error in eclipse: Module config Id not found for undeployment java.lang.NullPointerException at org.apache.geronimo.st.core.jaxb.JAXBUtils.unmarshalFilterDeploymentPlan(JAXBUtils.java:126) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:236) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:199) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:179) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getConfigId(GeronimoV21Utils.java:119) at org.apache.geronimo.st.v21.core.GeronimoV21VersionHandler.getConfigID(GeronimoV21VersionHandler.java:36) at org.apache.geronimo.st.core.commands.UndeployCommand.execute(UndeployCommand.java:53) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.unDeploy(GeronimoServerBehaviourDelegate.java:740) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doRemoved(GeronimoServerBehaviourDelegate.java:666) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:451) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:273) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) If I export the project as a war file, and deploy it to geronimo, I don't get the error, so I suspect it's a GEP problem. Here is my geronimo-web.xml file: ?xml version=1.0 encoding=UTF-8? web:web-app xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; xmlns:client=http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0; xmlns:conn=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:ejb=http://openejb.apache.org/xml/ns/openejb-jar-2.2; xmlns:log=http://geronimo.apache.org/xml/ns/loginconfig-2.0; xmlns:name=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pers=http://java.sun.com/xml/ns/persistence; xmlns:pkgen=http://openejb.apache.org/xml/ns/pkgen-2.1; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1; dep:environment dep:moduleId dep:groupIdcom.ibm.websphere.xs.sample/dep:groupId dep:artifactIdGettnStarted3/dep:artifactId dep:version1.0/dep:version dep:typejar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdcom.ibm.websphere.xs/dep:groupId dep:artifactIdogclient/dep:artifactId dep:version7.0/dep:version dep:typejar/dep:type /dep:dependency dep:dependency dep:groupIdcom.ibm.websphere.xs/dep:groupId dep:artifactIdobjectgrid/dep:artifactId dep:version7.0/dep:version dep:typejar/dep:type
[jira] Updated: (GERONIMODEVTOOLS-601) Module config Id not found for undeployment
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-601: --- Attachment: GetnStarted3AG.zip This is the eclipse project in which I am seeing the error. Module config Id not found for undeployment --- Key: GERONIMODEVTOOLS-601 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-601 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: MacOS eclipse, Galileo SR1, Eclipse Java EE IDE for Web Developers, Build id: 20090902-1017 I am running in a Mac with this java: java -version java version 1.6.0_17 Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-9M3125) Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode) Reporter: Ted Kirby Assignee: Tim McConnell Priority: Minor Attachments: GetnStarted3AG.zip I have created a dynamic web project and it seems to work fine. I can deploy and use the war file, and it gets republished if I change source. However, on every deploy/republish, I get this error in eclipse: Module config Id not found for undeployment java.lang.NullPointerException at org.apache.geronimo.st.core.jaxb.JAXBUtils.unmarshalFilterDeploymentPlan(JAXBUtils.java:126) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:236) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:199) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getWebDeploymentPlan(GeronimoV21Utils.java:179) at org.apache.geronimo.st.v21.core.GeronimoV21Utils.getConfigId(GeronimoV21Utils.java:119) at org.apache.geronimo.st.v21.core.GeronimoV21VersionHandler.getConfigID(GeronimoV21VersionHandler.java:36) at org.apache.geronimo.st.core.commands.UndeployCommand.execute(UndeployCommand.java:53) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.run(SynchronizedDeploymentOp.java:84) at org.apache.geronimo.st.core.commands.SynchronizedDeploymentOp.execute(SynchronizedDeploymentOp.java:76) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.unDeploy(GeronimoServerBehaviourDelegate.java:740) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doRemoved(GeronimoServerBehaviourDelegate.java:666) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:451) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:318) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:948) at org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:273) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:872) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:708) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:2690) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:272) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) If I export the project as a war file, and deploy it to geronimo, I don't get the error, so I suspect it's a GEP problem. Here is my geronimo-web.xml file: ?xml version=1.0 encoding=UTF-8? web:web-app xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0; xmlns:client=http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0; xmlns:conn=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2; xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2; xmlns:ejb=http://openejb.apache.org/xml/ns/openejb-jar-2.2; xmlns:log=http://geronimo.apache.org/xml/ns/loginconfig-2.0; xmlns:name=http://geronimo.apache.org/xml/ns/naming-1.2; xmlns:pers=http://java.sun.com/xml/ns/persistence; xmlns:pkgen=http://openejb.apache.org/xml/ns/pkgen-2.1; xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0; xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1; dep:environment dep:moduleId dep:groupIdcom.ibm.websphere.xs.sample/dep:groupId dep:artifactIdGettnStarted3/dep:artifactId dep:version1.0/dep:version dep:typejar/dep:type /dep:moduleId dep:dependencies dep:dependency dep:groupIdcom.ibm.websphere.xs/dep:groupId dep:artifactIdogclient/dep:artifactId
[jira] Commented: (GERONIMODEVTOOLS-579) java specs are not included into G server runtime by default
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12721869#action_12721869
]
Ted Kirby commented on GERONIMODEVTOOLS-579:
Delos, I am not following the first part of the patch. Is this what you want:
public String getClasspathContainerLabel(IRuntime runtime) {
String version = runtime.getRuntimeType().getVersion();
if (version.equals(2.0)) {
return Messages.target20runtime;
}
if (version.equals(2.1)) {
return Messages.target21runtime;
}
return Messages.target22runtime;
}
java specs are not included into G server runtime by default
Key: GERONIMODEVTOOLS-579
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-579
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 2.2.0
Environment: os:win2003
Reporter: viola.lu
Assignee: Tim McConnell
Priority: Minor
Attachments: 579.patch
1.Create a web dynamic project ,and add %@ taglib
uri=http://java.sun.com/jsf/core; prefix='f' % to a jsp file
2.But can't recognize this taglib
In
$GEPsrc\plugins\org\apache\geronimo\st\core\GeronimoServerRuntimeTargetHandler.java
file, no support for 2.2 target runtime, so myface spec, javamail spec
are not included by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-492) GEP v2.1.1 installation error in eclipse Ganymede JEE package
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12718426#action_12718426 ] Ted Kirby commented on GERONIMODEVTOOLS-492: Thanks for the workaround, Carlos. This problem should have been fixed in GEP 2.1.2. Did you try the original scenario with GEP 2.1.4 and it failed? If that is the case, we should either re-open this JIRA, or open an new one. What version of eclipse did you use, and what were the error messages you got? Thanks. GEP v2.1.1 installation error in eclipse Ganymede JEE package - Key: GERONIMODEVTOOLS-492 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-492 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.1 Environment: OS: Windows XP SP2 and Ubuntu 8.04 Eclipse: Eclipse Ganymede JEE package, based on Version: 3.4.0 Build id: I20080617-2000 JDK: IBM SDK 5 sr6b Reporter: Forrest Xia Assignee: Ted Kirby Fix For: 2.1.2 Steps: 1. Download and lauch eclipse ganymede 2. click Software Updates...-Available Software to add a site point to http://www.apache.org/dist/geronimo/eclipse/updates 3. Choose Geronimo v2.1 Server Adapter to install Symptom: An install error shows up as follows: Cannot complete the request. See the details. Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0) Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0) Unsatisfied dependency: [org.apache.geronimo.feature.feature.group 2.1.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0) Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] requiredCapability: org.eclipse.equinox.p2.iu/org.eclipse.jst.feature.group/[2.0.0,3.0.0) Unsatisfied dependency: [org.apache.geronimo.v21.feature.feature.group 2.1.1] requiredCapability: org.eclipse.equinox.p2.iu/org.apache.geronimo.feature.feature.group/[2.1.1,2.1.1] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-570) GEP 2.0.2 branch build failed
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby closed GERONIMODEVTOOLS-570. -- Resolution: Fixed Assignee: Ted Kirby (was: Delos Dai) Fixed with rev 769789. Thanks for the patch Delos. It built successfully for me with the patch. GEP 2.0.2 branch build failed - Key: GERONIMODEVTOOLS-570 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-570 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.2 Reporter: Delos Dai Assignee: Ted Kirby Fix For: 2.0.2 Attachments: 570.patch Currently, when build GEP 2.0.2 branch, it failed. 1. It's due to the download URL of dtp,wtp,emf.etc. Fix with right URL 2. Several server dependencies can't be found. So change Geronimo server version from 2.0.1 to 2.0.2 and exclude some artifact which even doesn't exist in central maven repository -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-569) Deploy error when add share lib dependency
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703116#action_12703116 ] Ted Kirby commented on GERONIMODEVTOOLS-569: Thanks for the path, Viola. Could you re-attach the patch, this time checking the box to grant ASF license to the code in the patch? Thanks. Deploy error when add share lib dependency -- Key: GERONIMODEVTOOLS-569 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-569 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.2 Environment: OS:any platform Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: sharelib.patch 1.Create a dynamic web app, and add share lib dependency 2.deploy app, but erros exsit as below: Distribution of configuration failed. See log for details. Unable to create configuration for deployment org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:120) at org.apache.geronimo.deployment.DeploymentContext.init(DeploymentContext.java:100) at org.apache.geronimo.deployment.DeploymentContext.init(DeploymentContext.java:80) at org.apache.geronimo.j2ee.deployment.EARContext.init(EARContext.java:68) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:512) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$$EnhancerByCGLIB$$762a1907.buildConfiguration(generat ed) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:135) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1423) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:96) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1260) at java.security.AccessController.doPrivileged(AccessController.java:279) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1363) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:797
[jira] Closed: (GERONIMODEVTOOLS-569) Deploy error when add share lib dependency
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby closed GERONIMODEVTOOLS-569. -- Resolution: Fixed Fix Version/s: 2.0.2 Assignee: Ted Kirby (was: Tim McConnell) patch applied with rev 769230. Thanks Viola. Deploy error when add share lib dependency -- Key: GERONIMODEVTOOLS-569 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-569 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.2 Environment: OS:any platform Reporter: viola.lu Assignee: Ted Kirby Priority: Minor Fix For: 2.0.2 Attachments: sharelib.patch 1.Create a dynamic web app, and add share lib dependency 2.deploy app, but erros exsit as below: Distribution of configuration failed. See log for details. Unable to create configuration for deployment org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:120) at org.apache.geronimo.deployment.DeploymentContext.init(DeploymentContext.java:100) at org.apache.geronimo.deployment.DeploymentContext.init(DeploymentContext.java:80) at org.apache.geronimo.j2ee.deployment.EARContext.init(EARContext.java:68) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:512) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$$EnhancerByCGLIB$$762a1907.buildConfiguration(generat ed) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:135) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231) at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:238) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:833) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:802) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1423) at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:96) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1260) at java.security.AccessController.doPrivileged(AccessController.java:279) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1363) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:797) at sun.reflect.GeneratedMethodAccessor156
[jira] Commented: (GERONIMODEVTOOLS-569) Deploy error when add share lib dependency
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12703487#action_12703487 ] Ted Kirby commented on GERONIMODEVTOOLS-569: I get this error trying to build GEP 2.0.2: [get] Can't get http://www.eclipse.org/downloads/download.php?file=/datatools/downloads/1.5/dtp-sdk_1.5.zipr=1protocol=http to /m2/org/eclipse/eclipse/3.3/dtp-sdk_1.5.zip [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing ant tasks Embedded error: The following error occurred while executing this line: /Users/tedkirby/svn/gdvtls/branches/2.0.2/eclipse/build.xml:87: The following error occurred while executing this line: /Users/tedkirby/svn/gdvtls/branches/2.0.2/eclipse/build.xml:99: Can't get http://www.eclipse.org/downloads/download.php?file=/datatools/downloads/1.5/dtp-sdk_1.5.zipr=1protocol=http to /m2/org/eclipse/eclipse/3.3/dtp-sdk_1.5.zip Guess we need another JIRA for this issue. Delos, you seem to get further, maybe because you have that level of dtk already. Deploy error when add share lib dependency -- Key: GERONIMODEVTOOLS-569 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-569 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.2 Environment: OS:any platform Reporter: viola.lu Assignee: Ted Kirby Priority: Minor Fix For: 2.0.2 Attachments: sharelib.patch 1.Create a dynamic web app, and add share lib dependency 2.deploy app, but erros exsit as below: Distribution of configuration failed. See log for details. Unable to create configuration for deployment org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:120) at org.apache.geronimo.deployment.DeploymentContext.init(DeploymentContext.java:100) at org.apache.geronimo.deployment.DeploymentContext.init(DeploymentContext.java:80) at org.apache.geronimo.j2ee.deployment.EARContext.init(EARContext.java:68) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder.buildConfiguration(EARConfigBuilder.java:512) at org.apache.geronimo.j2ee.deployment.EARConfigBuilder$$FastClassByCGLIB$$38e56ec6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.j2ee.deployment.CorbaGBeanNameSource$$EnhancerByCGLIB$$762a1907.buildConfiguration(generat ed) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:319) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:135) at org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:342) at org.apache.geronimo.kernel.KernelGBean$$FastClassByCGLIB$$1cccefc9.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:865) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:239) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:168) at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:231
[jira] Closed: (GERONIMODEVTOOLS-568) Trunk build failed: should remove snapshot for 2.1 runtime dependency package
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby closed GERONIMODEVTOOLS-568. -- Resolution: Fixed Assignee: Ted Kirby (was: Delos Dai) patch applied with rev 767149. Thanks Delos! Trunk build failed: should remove snapshot for 2.1 runtime dependency package --- Key: GERONIMODEVTOOLS-568 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-568 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Delos Dai Assignee: Ted Kirby Fix For: 2.2.0 Attachments: trunk_build_failed.patch Devtools trunk build failed in org.apache.geronimo.runtime.v21 plugin. The reason is some 2.1.4-snapshot package still exist in the Manifest.MF. Since 2.1.4 has released, all the snapshot can be removed. Then, devtools trunk can be successfully. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-559) GEP signed feature jar(s) should not display nulls when asking the user if they trust the certificate(s)
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-559: --- Description: It seems that as a result of GERONIMODEVTOOLS-521 our jar(s) are signed. However as they are now they may likely cause more confusion with the end-user, rather then instill confidence. When the Eclipse installer discovers they are signed it asks the end-user if they trust the certificate(s). The one for the GEP feature displays too many nulls -- these values should be populated to mitigate possible confusion. I'll attach a screenshot to show what exactly I mean.(was: It seems that as a result of GERONIMODEVTOOLS-521 are feature jar(s) are signed. However as they are now they may likely cause more confusion with the end-user, rather then instill confidence. When the Eclipse installer discovers they are signed it asks the end-user if they trust the certificate(s). The one for the GEP feature displays too many nulls -- these values should be populated to mitigate possible confusion. I'll attach a screenshot to show what exactly I mean. ) GEP signed feature jar(s) should not display nulls when asking the user if they trust the certificate(s) -- Key: GERONIMODEVTOOLS-559 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-559 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0, 2.1.4 Reporter: Tim McConnell Assignee: Delos Dai Attachments: screenshot-1.jpg, screenshot-2.jpg It seems that as a result of GERONIMODEVTOOLS-521 our jar(s) are signed. However as they are now they may likely cause more confusion with the end-user, rather then instill confidence. When the Eclipse installer discovers they are signed it asks the end-user if they trust the certificate(s). The one for the GEP feature displays too many nulls -- these values should be populated to mitigate possible confusion. I'll attach a screenshot to show what exactly I mean. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-521) Sign features so the eclipse update manager recognizes them as signed
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12664146#action_12664146 ] Ted Kirby commented on GERONIMODEVTOOLS-521: That seems a bit much. Let me play with the current approach/patch. Thanks. Sign features so the eclipse update manager recognizes them as signed - Key: GERONIMODEVTOOLS-521 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.1.3 Reporter: Ted Kirby Assignee: Tim McConnell Fix For: 2.2.0 Attachments: 521.patch, 521_updated.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-521) Sign features so the eclipse update manager recognizes them as signed
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Kirby resolved GERONIMODEVTOOLS-521.
Resolution: Fixed
Fix Version/s: 2.1.4
Assignee: Ted Kirby (was: Tim McConnell)
Looks good!
The features are signed. The certificate I think should last longer, and I
don't see a signed date, but the jars show up as signed. This seems like a
good start. Thanks Delos.
I get this when building on the mac:
INFO] [jar:jar]
[INFO] Building jar:
/Users/tedkirby/svn/gdvtls/trunk/features/org.apache.geronimo.v22.feature/target/org.apache.geronimo.v22.feature-2.2.0.jar
[INFO] [jar:sign {execution: default}]
[debug] jarsigner
executable=[/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jarsigner]
[debug] Executing: /bin/sh -c cd
/Users/tedkirby/svn/gdvtls/trunk/features/org.apache.geronimo.v22.feature
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Home/bin/jarsigner
-verify
/Users/tedkirby/svn/gdvtls/trunk/features/org.apache.geronimo.v22.feature/target/org.apache.geronimo.v22.feature-2.2.0.jar
[info] jar is unsigned. (signatures missing or not parsable)
[INFO]
[INFO] Warning: The signer certificate will expire within six months.
In eclipse, the jars are signed, and they seem to have the signer artifacts in
them. The certificate seems to be for 3 months.
Also, I saw no differences between the two patches.
Applied in trunk with rev 734846, and in branches/2.1.4 with rev 734853.
Sign features so the eclipse update manager recognizes them as signed
-
Key: GERONIMODEVTOOLS-521
URL:
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521
Project: Geronimo-Devtools
Issue Type: Bug
Components: eclipse-plugin
Affects Versions: 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.1.3
Reporter: Ted Kirby
Assignee: Ted Kirby
Fix For: 2.2.0, 2.1.4
Attachments: 521.patch, 521_updated.patch
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-521) Sign features so the eclipse update manager recognizes them as signed
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663929#action_12663929 ] Ted Kirby commented on GERONIMODEVTOOLS-521: I think dynamic generation of passwords for a build sound good. Can you code that? Sign features so the eclipse update manager recognizes them as signed - Key: GERONIMODEVTOOLS-521 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.1.3 Reporter: Ted Kirby Assignee: Tim McConnell Fix For: 2.2.0 Attachments: 521.patch, 521_updated.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-554) warning message about supported JDK version is wrong
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby resolved GERONIMODEVTOOLS-554. Resolution: Fixed Fix Version/s: 2.1.4 2.2.0 fixed in trunk with rev 734561, and 2.1.4 branch with rev 734564. Thanks for the patch, Delos! warning message about supported JDK version is wrong Key: GERONIMODEVTOOLS-554 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-554 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.2.0, 2.1.4 Attachments: 554.patch, warning.JPG Hi, When I use JDK 6.0 with GEP 2.2, in the wizard New Server Runtime Environment, a warning message is shown Apache Geronimo v2.2 is currently certified only on a Sun JDK 5.0+ (J2SE 1.5.0+)..See attachment for more details. I think this message should only show when a JDK 1.4 is used. Otherwise, the statement is not accurate. Any comments? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-554) warning message about supported JDK version is wrong
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663344#action_12663344 ] Ted Kirby commented on GERONIMODEVTOOLS-554: I certainly believe the statement is accurate. The idea is it reflects the level of java used to run the TCK and certify that Geronimo is JEE compliant. I think 1.5.0+ covers the 1.6 case. But I agree that we may revisit this message, and should as java levels change. I have resisted using the term supported in this message, but perhaps that is a better term to use. We do want to reflect server requirements. So, perhaps we change the message to Apache Geronimo v2.2 requires a 5.0+ JDK (J2SE 1.5.0+)., and show the message only on JDK levels less than that. Comments? warning message about supported JDK version is wrong Key: GERONIMODEVTOOLS-554 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-554 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Delos Dai Assignee: Delos Dai Attachments: warning.JPG Hi, When I use JDK 6.0 with GEP 2.2, in the wizard New Server Runtime Environment, a warning message is shown Apache Geronimo v2.2 is currently certified only on a Sun JDK 5.0+ (J2SE 1.5.0+)..See attachment for more details. I think this message should only show when a JDK 1.4 is used. Otherwise, the statement is not accurate. Any comments? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-521) Sign features so the eclipse update manager recognizes them as signed
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12663479#action_12663479 ] Ted Kirby commented on GERONIMODEVTOOLS-521: Thanks Delos. I am not sure what to make of the keystore and password. No doubt something like this is required for signing. I'm not sure if and how we want to go forward with this in terms of incorporating it with our build. It does not appear to be an Apache requirement to sign the eclipse jars. I found this eclipse link on Jar Signing: http://wiki.eclipse.org/index.php/JAR_Signing. This discusses signing during an automated build, including procedure for using an eclipse machine and signature. ServiceMix seems to use maven-gpg-plugin, but I don't know if this is for eclipse plugins, or if that matters. I can't tell if this is automated, and, if so, where the passphrase is specified. It seems that Apache prefers GPG for this sort of thing, altho for signing eclipse plugins, this may not be required. Certainly if we put passwords in pom.xml files, this will not be secure. On the other hand, we just wanted to sign jars, so this may not matter. Still, a signature implies validation, and having the key in a publicly available pom.xml file would seem to undermine that claim. Delos, how does this patch work? Will it create a keystore if there is not one? Will this work for clean and non-clean mvn builds? I appreciate your efforts it getting this working. I have concerns and questions about keys and signing. I also seek input from others. Sign features so the eclipse update manager recognizes them as signed - Key: GERONIMODEVTOOLS-521 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0, 2.1.0, 2.1.1, 2.1.2, 2.1.3 Reporter: Ted Kirby Assignee: Tim McConnell Fix For: 2.2.0 Attachments: 521.patch, 521_updated.patch -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r733149 - in /geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins: org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/ org.apache.geronimo.st.ui/src/m
Wouldn't you rather use varargs for tracePoint, versus seperate
methods for 1-5 parameters?
Ted
On Fri, Jan 9, 2009 at 3:44 PM, mcco...@apache.org wrote:
Author: mcconne
Date: Fri Jan 9 12:44:26 2009
New Revision: 733149
URL: http://svn.apache.org/viewvc?rev=733149view=rev
Log:
Make trace logic more concise and trace output easier to read
Modified:
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/internal/Trace.java
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.v21.core/src/main/java/org/apache/geronimo/st/v21/core/internal/Trace.java
Modified:
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java?rev=733149r1=733148r2=733149view=diff
==
---
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
(original)
+++
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
Fri Jan 9 12:44:26 2009
@@ -25,60 +25,60 @@
*/
public class Trace {
- /**
-* Finest trace event.
-*/
- public static byte INFO = 0;
-
- /**
-* Warning trace event.
-*/
- public static byte WARNING = 1;
-
- /**
-* Severe trace event.
-*/
- public static byte SEVERE = 2;
-
- /**
-* Trace constructor comment.
-*/
- private Trace() {
- super();
- }
-
- /**
-* Trace the given text.
-*
-* @param level
-*the trace level
-* @param s
-*a message
-*/
- public static void trace(byte level, String s) {
- trace(level, s, null, false);
- }
-
- public static void trace(byte level, String s, boolean newLine) {
- trace(level, s, null, newLine);
- }
-
- public static void trace(byte level, String s, Throwable t) {
- trace(level, s, null, false);
- }
-
- public static void trace(byte level, String s, Throwable t, boolean
newLine) {
- if (Activator.getDefault() == null ||
!Activator.getDefault().isDebugging())
- return;
-
- if(newLine) {
- System.out.println();
- }
-
- System.out.println(Activator.PLUGIN_ID + : + s);
- if (t != null)
- t.printStackTrace();
- }
+/**
+ * Finest trace event.
+ */
+public static byte INFO = 0;
+
+/**
+ * Warning trace event.
+ */
+public static byte WARNING = 1;
+
+/**
+ * Severe trace event.
+ */
+public static byte SEVERE = 2;
+
+/**
+ * Trace constructor comment.
+ */
+private Trace() {
+super();
+}
+
+/**
+ * Trace the given text.
+ *
+ * @param level
+ *the trace level
+ * @param s
+ *a message
+ */
+public static void trace(byte level, String s) {
+trace(level, s, null, false);
+}
+
+public static void trace(byte level, String s, boolean newLine) {
+trace(level, s, null, newLine);
+}
+
+public static void trace(byte level, String s, Throwable t) {
+trace(level, s, null, false);
+}
+
+public static void trace(byte level, String s, Throwable t, boolean
newLine) {
+if (Activator.getDefault() == null ||
!Activator.getDefault().isDebugging())
+return;
+
+if(newLine) {
+System.out.println();
+}
+
+System.out.println(Activator.PLUGIN_ID + : + s);
+if (t != null)
+t.printStackTrace();
+}
/**
* Trace the given message
@@ -89,38 +89,25 @@
* @param classDotMethod
*The class name + method name (e.g., Class.method())
*
- * @param parm1,2,3,4,5
- *Method parameters if the trace point is an Entry
+ * @param parms
+ *Method parameter(s) if the trace point is an Entry
*or
*Return value if the trace point is an Exit
*/
public static void tracePoint(String tracePoint, String
Re: svn commit: r733149 - in /geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins: org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/ org.apache.geronimo.st.ui/src/m
oh yeah... good job! :-) Does each trace call produce one line of
output? If so, StringBuilder could be used to replicate the original
behaviour.
On Sun, Jan 11, 2009 at 5:11 PM, Tim McConnell tim.mcco...@gmail.com wrote:
Hi Ted, yes that's exactly what I changed. I removed the separate methods
and replaced with Object... parms
Ted Kirby wrote:
Wouldn't you rather use varargs for tracePoint, versus seperate
methods for 1-5 parameters?
Ted
On Fri, Jan 9, 2009 at 3:44 PM, mcco...@apache.org wrote:
Author: mcconne
Date: Fri Jan 9 12:44:26 2009
New Revision: 733149
URL: http://svn.apache.org/viewvc?rev=733149view=rev
Log:
Make trace logic more concise and trace output easier to read
Modified:
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.ui/src/main/java/org/apache/geronimo/st/ui/internal/Trace.java
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.v21.core/src/main/java/org/apache/geronimo/st/v21/core/internal/Trace.java
Modified:
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
URL:
http://svn.apache.org/viewvc/geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java?rev=733149r1=733148r2=733149view=diff
==
---
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
(original)
+++
geronimo/devtools/eclipse-plugin/branches/2.1.4/plugins/org.apache.geronimo.st.core/src/main/java/org/apache/geronimo/st/core/internal/Trace.java
Fri Jan 9 12:44:26 2009
@@ -25,60 +25,60 @@
*/
public class Trace {
- /**
-* Finest trace event.
-*/
- public static byte INFO = 0;
-
- /**
-* Warning trace event.
-*/
- public static byte WARNING = 1;
-
- /**
-* Severe trace event.
-*/
- public static byte SEVERE = 2;
-
- /**
-* Trace constructor comment.
-*/
- private Trace() {
- super();
- }
-
- /**
-* Trace the given text.
-*
-* @param level
-*the trace level
-* @param s
-*a message
-*/
- public static void trace(byte level, String s) {
- trace(level, s, null, false);
- }
-
- public static void trace(byte level, String s, boolean newLine) {
- trace(level, s, null, newLine);
- }
-
- public static void trace(byte level, String s, Throwable t) {
- trace(level, s, null, false);
- }
-
- public static void trace(byte level, String s, Throwable t,
boolean newLine) {
- if (Activator.getDefault() == null ||
!Activator.getDefault().isDebugging())
- return;
-
- if(newLine) {
- System.out.println();
- }
-
- System.out.println(Activator.PLUGIN_ID + : + s);
- if (t != null)
- t.printStackTrace();
- }
+/**
+ * Finest trace event.
+ */
+public static byte INFO = 0;
+
+/**
+ * Warning trace event.
+ */
+public static byte WARNING = 1;
+
+/**
+ * Severe trace event.
+ */
+public static byte SEVERE = 2;
+
+/**
+ * Trace constructor comment.
+ */
+private Trace() {
+super();
+}
+
+/**
+ * Trace the given text.
+ *
+ * @param level
+ *the trace level
+ * @param s
+ *a message
+ */
+public static void trace(byte level, String s) {
+trace(level, s, null, false);
+}
+
+public static void trace(byte level, String s, boolean newLine) {
+trace(level, s, null, newLine);
+}
+
+public static void trace(byte level, String s, Throwable t) {
+trace(level, s, null, false);
+}
+
+public static void trace(byte level, String s, Throwable t, boolean
newLine) {
+if (Activator.getDefault() == null ||
!Activator.getDefault().isDebugging())
+return;
+
+if(newLine) {
+System.out.println();
+}
+
+System.out.println(Activator.PLUGIN_ID + : + s);
+if (t != null)
+t.printStackTrace();
+}
/**
* Trace the given message
@@ -89,38 +89,25 @@
* @param classDotMethod
*The class name + method name (e.g., Class.method())
*
- * @param
[jira] Updated: (GERONIMODEVTOOLS-551) Update copyright years for 2009
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-551: --- Affects Version/s: 2.2.0 Fix Version/s: 2.2.0 affects 2.2/trunk also. Update copyright years for 2009 --- Key: GERONIMODEVTOOLS-551 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-551 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0, 2.1.4 Reporter: Ted Kirby Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0, 2.1.4 Update all copyright ranges in various files for 2009. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-551) Update copyright years for 2009
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12662083#action_12662083 ] Ted Kirby commented on GERONIMODEVTOOLS-551: 2.2/trunk fixed with rev 732802. Update copyright years for 2009 --- Key: GERONIMODEVTOOLS-551 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-551 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0, 2.1.4 Reporter: Ted Kirby Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0, 2.1.4 Update all copyright ranges in various files for 2009. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-551) Update copyright years for 2009
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby closed GERONIMODEVTOOLS-551. -- Resolution: Fixed fixed in 2.1.4 branch with rev 732807. Update copyright years for 2009 --- Key: GERONIMODEVTOOLS-551 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-551 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0, 2.1.4 Reporter: Ted Kirby Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0, 2.1.4 Update all copyright ranges in various files for 2009. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-518) Update GEP code with new Devtools URL
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby closed GERONIMODEVTOOLS-518. -- Resolution: Fixed Update GEP code with new Devtools URL - Key: GERONIMODEVTOOLS-518 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-518 Project: Geronimo-Devtools Issue Type: Bug Affects Versions: 2.1.3, 2.2.0 Reporter: Ted Kirby Assignee: Ted Kirby Fix For: 2.2.0 Recently, the devtools sub-project homepage was changed from http://geronimo.apache.org/development-tools.html to http://cwiki.apache.org/GMOxDOC21/apache-geronimo-development-tools-project.html. I have just found some references in the code to the old page that need to be updated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-551) Update copyright years for 2009
Update copyright years for 2009 --- Key: GERONIMODEVTOOLS-551 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-551 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.4 Reporter: Ted Kirby Assignee: Tim McConnell Priority: Minor Fix For: 2.1.4 Update all copyright ranges in various files for 2009. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (GERONIMODEVTOOLS-534) Fail to remove directory from repository after removing project from elicpse
Yes please. Thanks! If you could include some more of the G log, that would be great. Hopefully, it mentions which files are in the directory. Can you report that too, by looking on the file system? Also, was this run on one machine, or is remote deploy involved? Is the repository file system local or remote? Thanks. On Tue, Nov 18, 2008 at 5:31 AM, viola.lu (JIRA) [EMAIL PROTECTED] wrote: [ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648569#action_12648569 ] viola.lu commented on GERONIMODEVTOOLS-534: --- Thanks Ted.I tried to deploy jar to G via deploy command, which behaves same as in WEP.Seems it's not a GEP problem.Should report it in G server not in GEP? Fail to remove directory from repository after removing project from elicpse Key: GERONIMODEVTOOLS-534 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Environment: OS:windows 2003 Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: testejb.jar Steps: 1.Create an ejb project in elicpse, and deploy it to geronimo server via WEP, some errors output in console 2.So i remove it from current server runtime.Do some modifcation, and redeploy it 3.But it tells me that 11:39:19,546 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 11:42:13,765 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 4.I should go to repository to remove default directory first and go on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-534) Fail to remove directory from repository after removing project from elicpse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby closed GERONIMODEVTOOLS-534. -- Resolution: Fixed This is a server issue. See GERONIMO-4420, Fail to remove directory from repository after removing project from elicpse Key: GERONIMODEVTOOLS-534 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Environment: OS:windows 2003 Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: testejb.jar Steps: 1.Create an ejb project in elicpse, and deploy it to geronimo server via WEP, some errors output in console 2.So i remove it from current server runtime.Do some modifcation, and redeploy it 3.But it tells me that 11:39:19,546 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 11:42:13,765 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 4.I should go to repository to remove default directory first and go on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4420) Create Files under repository even if fail to deploy a jar having problems.
[ https://issues.apache.org/jira/browse/GERONIMO-4420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648907#action_12648907 ] Ted Kirby commented on GERONIMO-4420: - See link another instance of GERONIMO-3489. Viola, any special considerations, like remote deploy, or any kind of remote file system? Create Files under repository even if fail to deploy a jar having problems. --- Key: GERONIMO-4420 URL: https://issues.apache.org/jira/browse/GERONIMO-4420 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.1.3 Environment: OS:Any platform Reporter: viola.lu Priority: Minor Attachments: testejb.jar Defect transfers from GEP: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Steps: 1.Deploy attached testejb.jar, and this jar has some problems in it.So when deploy it via command or admin console, errors exist. 2.But in repository, files for this deployed jar are created already.If i redeploy this jar or deploy it second time, it will inform me : it exists in repository, i should remove it manually from repository. no log in server.log. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (GERONIMODEVTOOLS-534) Fail to remove directory from repository after removing project from elicpse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby reopened GERONIMODEVTOOLS-534: The issue was not fixed. I am reopening to to assign a more appropriate resolution. Fail to remove directory from repository after removing project from elicpse Key: GERONIMODEVTOOLS-534 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Environment: OS:windows 2003 Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: testejb.jar Steps: 1.Create an ejb project in elicpse, and deploy it to geronimo server via WEP, some errors output in console 2.So i remove it from current server runtime.Do some modifcation, and redeploy it 3.But it tells me that 11:39:19,546 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 11:42:13,765 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 4.I should go to repository to remove default directory first and go on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-534) Fail to remove directory from repository after removing project from elicpse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby closed GERONIMODEVTOOLS-534. -- Resolution: Invalid Assignee: Ted Kirby (was: Tim McConnell) This is a server issue, not a GEP issue. Fail to remove directory from repository after removing project from elicpse Key: GERONIMODEVTOOLS-534 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Environment: OS:windows 2003 Reporter: viola.lu Assignee: Ted Kirby Priority: Minor Attachments: testejb.jar Steps: 1.Create an ejb project in elicpse, and deploy it to geronimo server via WEP, some errors output in console 2.So i remove it from current server runtime.Do some modifcation, and redeploy it 3.But it tells me that 11:39:19,546 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 11:42:13,765 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 4.I should go to repository to remove default directory first and go on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-534) Fail to remove directory from repository after removing project from elicpse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648172#action_12648172 ] Ted Kirby commented on GERONIMODEVTOOLS-534: I have seen this occur on Windows outside of eclipse. That is a geronimo message, indicating it cannot remove a directory as part of undeploy. Have you tried your scenario outside of eclipse, say with the command-line deployer? Fail to remove directory from repository after removing project from elicpse Key: GERONIMODEVTOOLS-534 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Environment: OS:windows 2003 Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: testejb.jar Steps: 1.Create an ejb project in elicpse, and deploy it to geronimo server via WEP, some errors output in console 2.So i remove it from current server runtime.Do some modifcation, and redeploy it 3.But it tells me that 11:39:19,546 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 11:42:13,765 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 4.I should go to repository to remove default directory first and go on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-534) Fail to remove directory from repository after removing project from elicpse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12648478#action_12648478 ] Ted Kirby commented on GERONIMODEVTOOLS-534: When you remove the project from the server runtime, that should cause an undeploy command to be run on the server. It is that undeploy command that is generating the error message from Geronimo. G is having problems removing files. See GERONIMO-3489, for example. There should be other messages in the log indicating what file(s) are not being deleted. There is re-try logic in the code. It seems unlikely this is a GEP problem. Fail to remove directory from repository after removing project from elicpse Key: GERONIMODEVTOOLS-534 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-534 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Environment: OS:windows 2003 Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: testejb.jar Steps: 1.Create an ejb project in elicpse, and deploy it to geronimo server via WEP, some errors output in console 2.So i remove it from current server runtime.Do some modifcation, and redeploy it 3.But it tells me that 11:39:19,546 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 11:42:13,765 ERROR [RepositoryConfigurationStore] C:\geronimo-tomcat6-javaee5-2.1.3\repository\default\test\1.0\test-1.0.car is not an empty directory 4.I should go to repository to remove default directory first and go on. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Update on documentation progress of Geronimo v2.2
I fixed up some of the references to GEP pages. There is some duplication of GEP info between two sets of pages: Development environment and How to install Geronimo Eclipse Plugin. A couple of months ago I removed the installation instructions from the former, and replaced them with a link to the latter. The idea is to keep this information in one place. You can follow the gory details of this work in GERONIMODEVTOOLS-461. The plan is that there will be a How to install Geronimo Eclipse Plugin page for each release. Old and new releases are children of this page. The design of Development environment page seemed to be to put everything on one big page. I don't think this is a good approach. I think pages should be shorter and more focused. For example, breaking out the installation information. Hopefully, we can all by in sync moving forward. I think the GEP doc needs some work in terms of integrating it into the overall G doc, and eliminating duplication. Hopefully this can occur in G 2.2 and beyond. Thanks, Ted Kirby On Fri, Nov 14, 2008 at 1:13 AM, chi runhua [EMAIL PROTECTED] wrote: Hi all, We just created a page with one table of content to track progress of Geronimo 2.2 documentation. In this table, we highlighted some topics to be updated based on G 2.2 release roadmap. We believe that not every topic was included so far. Therefore, don't hesitate updating the table if you have new discoveries or topics. We also encourage everyone in this community to adopt topics and contribute more to the success of Geronimo. Here is the linkage for your reference. http://cwiki.apache.org/confluence/display/GMOxDOC22/Apache+Geronimo+v2.2+documentation+development+status What we are planning to do next are: 1. Moving pages to their appropriate parent so that the structure will be more like a tree; --- Ongoing 2. Keep the consistency between different topics including subject, wording and phrases; 3. Keep migrating topics from previous documentation and update them if capable; 4. Refine the granuality by dividing unique topics into pages, in this way, contibutors can include existing pages while writing a new topics instead of introducing basic concepts again and again. (might be difficult, but I hope it's the right direction); We are expecting to receive as much as feedback and opinions about documentation so that we can make it better and better. Thanks alot.
[jira] Commented: (GERONIMO-4349) jdbc driver is installed to wrong repository after installed server specific repo plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12646925#action_12646925 ] Ted Kirby commented on GERONIMO-4349: - That sounds right, Joe. We've seen this before: ordering differences with different JDKs causing problems. Forrest, I'd suggest DEBUG tracing of runs with both Sun and IBM JDKs, and compare the logs to see where things go bad with the IBM JDK. It looks like it's somewhere around the code where install directory is chosen. I'm not familiar with that part of the code. If you need more help, let me/us know. Ted Kirby jdbc driver is installed to wrong repository after installed server specific repo plugin Key: GERONIMO-4349 URL: https://issues.apache.org/jira/browse/GERONIMO-4349 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.1.3 Reporter: Forrest Xia Priority: Minor 1. start default server instance 2. install server specific repo plugin at http://geronimo.apache.org/plugins/geronimo-2.1.3/ 3. create a database pool with wizard, click download driver to install postgresql jdbc driver 4. after downloaded and installed, check where it is stored Issue: it is installed into GERONIMO_HOME/var/repository. But I think it should be installed into GERONIMO_HOME/repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: svn commit: r702479 - in /geronimo/devtools/eclipse-plugin/branches: 2.0.1/ 2.1.2/ 2.1.3/ 2.1/
Thanks Joe. I did just update the GEP release process to be more like the server. Before, we had copied trunk to branches for the release candidate. When approved, we had copied the branch to tags, and left the branch there. In future, we will move the branch to tags as you suggest. With this commit, I removed those old branches. The tags version should still have the change history. Ted Kirby On Tue, Oct 7, 2008 at 9:55 AM, Joe Bohn [EMAIL PROTECTED] wrote: Just FYI in the server we initially create the release branch via a copy but then move the branch to a tag when it is released. This preserves the history in svn and also removes the release branch as the tag is created. You might want to consider this approach for future GEP releases. Joe [EMAIL PROTECTED] wrote: Author: tkirby Date: Tue Oct 7 06:45:30 2008 New Revision: 702479 URL: http://svn.apache.org/viewvc?rev=702479view=rev Log: Be like the server. Get rid of old branches. These old releases are tagged Removed: geronimo/devtools/eclipse-plugin/branches/2.0.1/ geronimo/devtools/eclipse-plugin/branches/2.1/ geronimo/devtools/eclipse-plugin/branches/2.1.2/ geronimo/devtools/eclipse-plugin/branches/2.1.3/
GEP 2.1.4 branch created
I just copied GEP tags/2.1.3 to GEP braches/2.1.4 to create it. This will be the development tree for GEP 2.1.4, to support G 2.1.4. GEP trunk supports G 2.2, like the server does. I also updated the GEP release process to reflect this be like the server approach going forward. I removed the old 2.x GEP branches. Ted Kirby
[jira] Commented: (GERONIMODEVTOOLS-379) unable to set cmp-connection-factory
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637588#action_12637588 ] Ted Kirby commented on GERONIMODEVTOOLS-379: Applied to 214 branch with rev 702576 unable to set cmp-connection-factory Key: GERONIMODEVTOOLS-379 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-379 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: B.J. Reed Assignee: B.J. Reed Priority: Minor Fix For: 2.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-437) Determing success/failure of Abbot testcase from Maven
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12637590#action_12637590 ] Ted Kirby commented on GERONIMODEVTOOLS-437: applied to 214 branch with rev 702577 Determing success/failure of Abbot testcase from Maven -- Key: GERONIMODEVTOOLS-437 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-437 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Ashish Jain Fix For: 2.2.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-522) Feature.properties has a trailing backslash in it
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby resolved GERONIMODEVTOOLS-522. Resolution: Fixed Fix Version/s: 2.1.4 2.2.0 Assignee: Ted Kirby (was: Tim McConnell) It looks like we can't redo a released artifact. We will do a 214 release, and I added this fix to it in rev 702578. Feature.properties has a trailing backslash in it - Key: GERONIMODEVTOOLS-522 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-522 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Charles Overbeck Assignee: Ted Kirby Fix For: 2.2.0, 2.1.4 The feature.properties on the update site bundled with org.apache.geronimo.v21.feature_2.1.3.jar has a trailing backslash in it. The last two lines of the file are this: trial in any resulting litigation. \n\ \n\ Note the trailing slash at the end of the second line; no characters follow it. This may not sound like a terrible bug on its own, but because that content ends up getting expanded inside the feature.xml, I think it escapes the next character in the feature.xml, which in this case is the which closes a tag. This leads to an incorrectly generated content.xml file if you are generating an update site using Eclipse's P2 metadata generator, and you have the Geronimo feature present when you are doing the metadata generation. I don't know if it has any other side-effects. In any case, that's why I'm proposing a priority of Major for this seeming trivial bug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: GEP 2.1.4 branch created
Done with revs 702578, 702577 and 702576, respectively. I updated the version number to 2.1.4, with 2.1.4-SNAPSHOT for the appropriate server bits, in rev 702573. Be advised, GEP development community: we have two branches to put fixes in: branches/2.1.4 and trunk, which is targeted for 2.2. Fixes for GEP 2.1.4 should go in branches/2.1.4 and trunk, if appropriate for 2.2. Ted Kirby On Tue, Oct 7, 2008 at 12:31 PM, Donald Woods [EMAIL PROTECTED] wrote: Thanks. Can we get r701571, r701213 and 700249 (GD-379) from GEP trunk included in GEP 2.1.4? -Donald Ted Kirby wrote: I just copied GEP tags/2.1.3 to GEP braches/2.1.4 to create it. This will be the development tree for GEP 2.1.4, to support G 2.1.4. GEP trunk supports G 2.2, like the server does. I also updated the GEP release process to reflect this be like the server approach going forward. I removed the old 2.x GEP branches. Ted Kirby
[jira] Commented: (GERONIMODEVTOOLS-522) Feature.properties has a trailing backslash in it
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12636776#action_12636776 ] Ted Kirby commented on GERONIMODEVTOOLS-522: Thanks for bug report. I fixed it in trunk with rev 701571. We would like to work better in p2, and have had some issues with it. I don't know if we will do a 2.1.4. Currently trunk is targeted to 2.2. I wonder if we could or should fix this in 2.1.3 and put new artifacts on our eclipse plugin update site? Feature.properties has a trailing backslash in it - Key: GERONIMODEVTOOLS-522 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-522 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Charles Overbeck Assignee: Tim McConnell The feature.properties on the update site bundled with org.apache.geronimo.v21.feature_2.1.3.jar has a trailing backslash in it. The last two lines of the file are this: trial in any resulting litigation. \n\ \n\ Note the trailing slash at the end of the second line; no characters follow it. This may not sound like a terrible bug on its own, but because that content ends up getting expanded inside the feature.xml, I think it escapes the next character in the feature.xml, which in this case is the which closes a tag. This leads to an incorrectly generated content.xml file if you are generating an update site using Eclipse's P2 metadata generator, and you have the Geronimo feature present when you are doing the metadata generation. I don't know if it has any other side-effects. In any case, that's why I'm proposing a priority of Major for this seeming trivial bug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Can we stop continually moving Devtools JIRAs to the next release?
Yes, I think that is what I did. As part of the GEP release process, I Administered the GERONIMODEVTOOLS JIRA project to update the released and unreleased versions. I managed the 2.1.3 release, and clicked the Release link to release it. This, I think, resulted in all that email. Ted On Thu, Sep 25, 2008 at 1:48 PM, Jason Dillon [EMAIL PROTECTED] wrote: Hrm... odd, cause the default when marking a version as released in JIRA asks to move unresolved issues to the next version... --jason On Sep 26, 2008, at 12:39 AM, Donald Woods wrote: Can we stop the blanket moving of Devtools JIRAs from one release to the next? We should really only move unfixed JIRAs to 2.2.0 if we have intentions of fixing them for the 2.2.0 release. Continually moving any open JIRAs once GEP is released is generating way too many emails and is not the proper usage of the Fix Versions field in JIRA, which should be used to denote to the community that we're going to try our best to resolve the issue in the denoted release. -Donald
What's up with JEE6? Are we doing it in 2.2?
Who's doing what? I sort of assumed that 2.2 would have JEE 6 in it, but I can't find any information about it. Thanks, Ted Kirby
[jira] Created: (GERONIMODEVTOOLS-520) Add v22 runtimes, plugins and feature
Add v22 runtimes, plugins and feature - Key: GERONIMODEVTOOLS-520 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-520 Project: Geronimo-Devtools Issue Type: New Feature Affects Versions: 2.2.0 Reporter: Ted Kirby Assignee: Ted Kirby Fix For: 2.2.0 As GEP trunk is targeted to v22, time to create plugins and a feature for 2.2, in addition to the existing 20 and 21 features, runtimes and plugins. These will be minimal, so that they can be expanded as needed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-520) Add v22 runtimes, plugins and feature
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby resolved GERONIMODEVTOOLS-520. Resolution: Fixed fixed with rev 698259. Initially I was going to have v22 feature just do v22, but it requires all of 21, and 20 is only a little extra, so the v22 feature supports v20, v21 and v22, so we really don't need the v21 feature at the moment. As this may change over time, I will leave it for now. Add v22 runtimes, plugins and feature - Key: GERONIMODEVTOOLS-520 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-520 Project: Geronimo-Devtools Issue Type: New Feature Affects Versions: 2.2.0 Reporter: Ted Kirby Assignee: Ted Kirby Fix For: 2.2.0 As GEP trunk is targeted to v22, time to create plugins and a feature for 2.2, in addition to the existing 20 and 21 features, runtimes and plugins. These will be minimal, so that they can be expanded as needed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Need GMOxSITE refresh for stale page http://geronimo.apache.org/geronimo-eclipse-plugin-build-instructions.html ?
I removed some pages from GMOxSITE over the weekend, including http://geronimo.apache.org/geronimo-eclipse-plugin-build-instructions.html . But, it is still there in HTML. If you click the edit link, then cancel, is says the page has been removed. Can someone explain/help me fix? Thanks, Ted Kirby
[jira] Created: (GERONIMODEVTOOLS-521) Sign features so the eclipse update manager recognizes them as signed
Sign features so the eclipse update manager recognizes them as signed - Key: GERONIMODEVTOOLS-521 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-521 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3, 2.1.2, 2.1.1, 2.1.0, 2.0.0 Reporter: Ted Kirby Assignee: Tim McConnell Fix For: 2.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-519) Document the Deployment Plan editors
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12633469#action_12633469 ] Ted Kirby commented on GERONIMODEVTOOLS-519: We're in a bit of flux regarding GEP doc. I think the doc you propose should go in pages under http://cwiki.apache.org/confluence/display/GMOxDOC22/Apache+Geronimo+Development+Tools+Project. In a separate thread, Donald has proposed giving GEP its own wiki space. We need to get our GEP doc properly tied in with GMOxDOC22. I'd like one page for each set of info, and certainly one install page, with pre-reqs. I don't think this new doc belongs in GMOxSITE. Document the Deployment Plan editors Key: GERONIMODEVTOOLS-519 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-519 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: B.J. Reed Assignee: B.J. Reed Priority: Minor Fix For: 2.2.0 As the Deployment Plan Editors are completed, we need to add detailed documentation for the use of each editor and page. It should be hooked into the existing documentation on the http://geronimo.apache.org/development-tools.html page. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-512) When running the testsuite from maven, the Geronimo branding does not show up
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-512: --- Fix Version/s: (was: 2.1.3) 2.2.0 When running the testsuite from maven, the Geronimo branding does not show up - Key: GERONIMODEVTOOLS-512 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-512 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.3 Environment: Windows Ganymede, maven 2.0.9 Reporter: B.J. Reed Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0 When running the Abbot testsuite from maven, the Geronimo image button does not show up in the About window. Probably can be fixed by unzipping the features as well as the plugins. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-505) PLUGIN_RELEASE-NOTES-2.1.2.txt missing from distribution
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-505: --- Fix Version/s: (was: 2.1.3) 2.2.0 PLUGIN_RELEASE-NOTES-2.1.2.txt missing from distribution Key: GERONIMODEVTOOLS-505 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-505 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.2 Reporter: Ted Kirby Assignee: Tim McConnell Fix For: 2.2.0 PLUGIN_RELEASE-NOTES-2.1.2.txt is not on the eclipse update web site http://apache.org/dist/geronimo/eclipse/updates/. It is also missing from deployable.zip. It should also be in updatesite.zip, and we should put updatesite.zip on the website with deployable.zip. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-504) advanced security section does not allow setting of credential store
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-504: --- Fix Version/s: (was: 2.1.3) 2.2.0 advanced security section does not allow setting of credential store Key: GERONIMODEVTOOLS-504 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-504 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.1.3 Environment: Ganymede on Windows Reporter: B.J. Reed Assignee: Shiva Kumar H R Fix For: 2.2.0 When editing the Web deployment plan (and probably the application and EJB as well), clicking the Credential Store Edit button does nothing. Have traced through the code and when the button is selected, a call to getCredentialStoreRefWizard is made in SecurityAdvancedSection.java. This method simply returns null without bringing up a dialog and setting the field. With this function disabled, most of the rest of the advanced security options are also disabled. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-510) Deployment plan editor warning message when opening source tab for openejb-jar.xml file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-510: --- Fix Version/s: (was: 2.1.3) 2.2.0 Deployment plan editor warning message when opening source tab for openejb-jar.xml file --- Key: GERONIMODEVTOOLS-510 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-510 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Reporter: Tim McConnell Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0 Warning message as shown in Eclipse: No grammar constraints (DTD or XML schema) detected for the document. openejb-jar.xml testEJB/ejbModule/META-INF line 1 XML Problem -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-496) GEP 2.1.2 cannot be uninstalled through P2 in Ganymede
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-496: --- Fix Version/s: (was: 2.1.3) 2.2.0 GEP 2.1.2 cannot be uninstalled through P2 in Ganymede -- Key: GERONIMODEVTOOLS-496 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-496 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.2 Environment: Windows XP SP2 Eclipse Ganymede GEP 2.1.2 Reporter: Forrest Xia Assignee: Tim McConnell Priority: Minor Fix For: 2.2.0 Steps: 1. Install GEP 2.1.2 through Software Updates... 2. Restart Ganymede to confirm installation is ok, and try to define a server runtime to launch server from eclipse, it's ok as well 3. Remove server runtime and uninstall GEP 2.1.2, then restart Ganymede 4. Check available server adapters, no Geronimo server adapter found, check feature list in Software Update..., not found. At here, seems the GEP is uninstalled successfully 5. Check Ganymede directory, however found some GEP plugins jar files are still there So the uninstall function does not work for GEP 2.1.2 in Ganymede. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-472) Pb Deploying an EJB with MyEclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Kirby updated GERONIMODEVTOOLS-472: --- Fix Version/s: (was: 2.1.3) 2.2.0 Pb Deploying an EJB with MyEclipse -- Key: GERONIMODEVTOOLS-472 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-472 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Environment: Wndows XP Eclipse Platform 3.2.2 MyEclipse 5.5.1 GA Geronimo 2.0 Reporter: Jean-Jacques Parent Assignee: Tim McConnell Fix For: 2.2.0 Attachments: .log, sonoraEjb.jar I am trying to deploy an ear file containing web applications and an EJB. Here is the ejb-jar.xml: ?xml version=1.0 encoding=UTF-8? ejb-jar xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd; version=2.1 enterprise-beans session ejb-nameApplicationContextSession/ejb-name local-homebe.gial.wkf.ejb.ApplicationContextSessionHome/local-home localbe.gial.wkf.ejb.ApplicationContextSession/local ejb-classbe.gial.wkf.ejb.ApplicationContextSessionBean/ejb-class session-typeStateless/session-type transaction-typeBean/transaction-type resource-ref res-ref-namejdbc/SONORA/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeShareable/res-sharing-scope /resource-ref resource-ref res-ref-namejdbc/RAPCOL/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeShareable/res-sharing-scope /resource-ref resource-ref res-ref-namejdbc/MAILINGPER/res-ref-name res-typejavax.sql.DataSource/res-type res-authContainer/res-auth res-sharing-scopeShareable/res-sharing-scope /resource-ref /session /enterprise-beans /ejb-jar Witihn myEclipse, I can't perform an exploded deployment (development mode), I receive the following message: Eclipse msgbox : C:\Geronimo-2.0\deploy\SonoraEAR.ear\SonoraEjb.jar is not a directory Whatever, the ear file is partially exploded into C;\Geronimo-2.0\deploy. (I thought that it would be in C:\Geronimo-2.0\repository\...) MyEclipse indicates that it has been successfully deployed but it is not the case. The package archive deployment (production mode) works fine. My ear file is copied in C:\geronimo-2.0\deploy. When the server starts, the ear is exploded into the Geronimo repository. But for developpement purpose it is not convenient. If I want to test my code modification, I always have to redeploy and restart the server. We are losing a lot of time working this way especially when developping JSP. They are not synchronized at all. Have you got any idea about the problem ? Do you think that WTP is a better tool ? Thanks -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
