Re: Welcome viola.lu as a new committer
Congratulation, Viola! On Sun, Jan 2, 2011 at 7:45 PM, Jacek Laskowski ja...@laskowski.net.plwrote: On Thu, Dec 30, 2010 at 6:57 AM, Ivan xhh...@gmail.com wrote: I would like to welcome viola.lu aboard, as she recently accepted the Geronimo PMC invitation to become a committer. Her account was just created this morning (viola.lu), so you should start seeing some commits from her soon. Gratulacje! Jacek -- Jacek Laskowski Notatnik Projektanta Java EE - http://jaceklaskowski.pl -- Best Regards, Delos
Re: Access Request for GEP release
You just need the permission for builds/geronimo/eclipse. Try again, I've granted the permission. On Mon, Dec 6, 2010 at 4:06 PM, han hongfang hanhongf...@gmail.com wrote: Hi, I need the access of directory www/people.apache.org/builds/geronimo on server people.apache.org to release GEP. Can somebody help me on this? Thanks a lot in advance! -- Best regards, Han Hong Fang (Janet) hanhongfang AT apache.org -- Best Regards, Delos
Re: Strange GEP branch versions.
I don't know the reason either, seems it's a convention for GEP from version 1.2.1. You may make it the same as server, I think. On Fri, Nov 5, 2010 at 11:21 PM, Ted Kirby ted.ki...@gmail.com wrote: 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 -- Best Regards, Delos
Re: Suggestions for improving new G and GEP user experiences
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
Re: Welcome Janet Hong Fang Han as a new committer
Congrats Janet! On Wed, Oct 27, 2010 at 7:58 AM, Jay D. McHugh jaydmch...@gmail.com wrote: Congratulations Janet! Jay On 10/20/2010 08:11 PM, Ivan 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 -- Best Regards, Delos
[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=12924296#action_12924296
]
Delos Dai commented on GERONIMODEVTOOLS-677:
If the GUI is not the same in various OS, I suggest to extract OS specific test
cases to a single test plugin. Then, every time only run the test cases per OS.
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
[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=12922424#action_12922424 ] Delos Dai commented on GERONIMODEVTOOLS-637: Ted, I commit all missing files for aries test cases in revision #1024101 and #1024098. EclipseUITest should not be removed in test.xml file.It's likely for me to comment EclipseUITest to skip some test cases. I found you have recovered the file. Thanks! 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.
[jira] Resolved: (GERONIMODEVTOOLS-676) branch 2.1.7 build error
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-676. Resolution: Fixed Build successfully with your patch. commit it in revision 1022868. Thanks Hong Fang Han for the patch! branch 2.1.7 build error Key: GERONIMODEVTOOLS-676 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-676 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.7 Reporter: Han Hong Fang Assignee: Han Hong Fang Attachments: GERONIMODEVTOOLS-676.patch Branch 2.1.7 build error due to incorrect version number etc. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-674) Upgrade eclipse to Helios SR1
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-674: --- Fix Version/s: (was: 3.0_M1) 3.0 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 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-608) Publish with GEP takes minutes, while deploy takes seconds
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12920861#action_12920861 ] Delos Dai commented on GERONIMODEVTOOLS-608: commit the patch in revision 1022386 for trunk. Thanks Boes and Chris for the patch! Publish with GEP takes minutes, while deploy takes seconds -- Key: GERONIMODEVTOOLS-608 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: GEP 2.2 installed in Eclipse (galileo-SR1). Reporter: Boes Assignee: Delos Dai Attachments: 608_20100909.patch, getEnvironment.txt, HiThere.ear, HiThereSlow.ear, reorderModules.txt Publishing an Enterprise Application (EAR) with GEP to Geronimo takes much more time then deploying the same EAR to Geronimo using the console. See http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-td684484.html After doing some research I found that EAR's that have dependencies in geronimo-application.xml take a lot of time to publish. This is caused by the very inefficient implementation of the reorderModules method in the org.apache.geronimo.st.core.internal.DependencyHelper class. I installed a GEP development environment and put on tracing. It tested an EAR with 3 WAR's in it. In the EAR's geronimo-application.xml I added dependency tags for 4 libraries. Tracing shows that this results in parsing the geronimo-application.xml 1092 (!) times. In code this means that a call to DependencyHelper.getEnvironment is made 1092 times. Another inefficient part in the reorderModules method is that the call to DeploymentUtils.isInstalledModule is repeatedly made for the same module. In the test I found it was called at least 3 times for each dependent library. These calls result in a request to Geronimo and take almost a second each. The best way to solve this bug is to redesign the reordering process and make it work in a way that both DependencyHelper.getEnvironment and DeploymentUtils.isInstalledModule are not called more often then needed. I wonder why DeploymentUtils.isInstalledModule is called at all. Dependencies are defined in the xml. I can't imagine why it would matter if a module is installed in Geronimo or not. What I did to fix this problem and make GEP workable again for me is: - made sure the DeploymentUtils.isInstalledModule is never called twice for the same module. Once the DeploymentUtils.isInstalledModule is called for a certain module, I add this module to a list. Before a next call to DeploymentUtils.isInstalledModule I verify if the call has been made before. If so, it doesn't need to be called again. - reduced the number of times the xml is parsed. I put the results of the DependencyHelper.getEnvironment for a certain module in a hashmap. Next time the DependencyHelper.getEnvironment is called for the same module, I returns the result stored in the hashmap. After these two modifications GEP is up to speed again. Removal of the call to DeploymentUtils.isInstalledModule makes GEP even faster. Just as fast as deployment using the Geronimo console. For me this works, but I don't know what the impact is for other users. In the attached code I left it the way it was. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-608) Publish with GEP takes minutes, while deploy takes seconds
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-608. Resolution: Fixed Fix Version/s: 3.0 2.1.7 2.2.1 commit the patch in revision 1022388 for 2.1.6 branch and 1022395 for 2.2.1 branch Publish with GEP takes minutes, while deploy takes seconds -- Key: GERONIMODEVTOOLS-608 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: GEP 2.2 installed in Eclipse (galileo-SR1). Reporter: Boes Assignee: Delos Dai Fix For: 2.2.1, 2.1.7, 3.0 Attachments: 608_20100909.patch, getEnvironment.txt, HiThere.ear, HiThereSlow.ear, reorderModules.txt Publishing an Enterprise Application (EAR) with GEP to Geronimo takes much more time then deploying the same EAR to Geronimo using the console. See http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-td684484.html After doing some research I found that EAR's that have dependencies in geronimo-application.xml take a lot of time to publish. This is caused by the very inefficient implementation of the reorderModules method in the org.apache.geronimo.st.core.internal.DependencyHelper class. I installed a GEP development environment and put on tracing. It tested an EAR with 3 WAR's in it. In the EAR's geronimo-application.xml I added dependency tags for 4 libraries. Tracing shows that this results in parsing the geronimo-application.xml 1092 (!) times. In code this means that a call to DependencyHelper.getEnvironment is made 1092 times. Another inefficient part in the reorderModules method is that the call to DeploymentUtils.isInstalledModule is repeatedly made for the same module. In the test I found it was called at least 3 times for each dependent library. These calls result in a request to Geronimo and take almost a second each. The best way to solve this bug is to redesign the reordering process and make it work in a way that both DependencyHelper.getEnvironment and DeploymentUtils.isInstalledModule are not called more often then needed. I wonder why DeploymentUtils.isInstalledModule is called at all. Dependencies are defined in the xml. I can't imagine why it would matter if a module is installed in Geronimo or not. What I did to fix this problem and make GEP workable again for me is: - made sure the DeploymentUtils.isInstalledModule is never called twice for the same module. Once the DeploymentUtils.isInstalledModule is called for a certain module, I add this module to a list. Before a next call to DeploymentUtils.isInstalledModule I verify if the call has been made before. If so, it doesn't need to be called again. - reduced the number of times the xml is parsed. I put the results of the DependencyHelper.getEnvironment for a certain module in a hashmap. Next time the DependencyHelper.getEnvironment is called for the same module, I returns the result stored in the hashmap. After these two modifications GEP is up to speed again. Removal of the call to DeploymentUtils.isInstalledModule makes GEP even faster. Just as fast as deployment using the Geronimo console. For me this works, but I don't know what the impact is for other users. In the attached code I left it the way it was. -- 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=12920485#action_12920485 ] Delos Dai commented on GERONIMODEVTOOLS-675: I did a couple of changes for testsuite 1) I updated the message for downloading free aries tools 2) 3.0 server can't be installed in testsuite, so I update the code to make the case runnable Now, I think the remaining work is to update texts on widgets according to new UI of eclipse helios SR1. Eg. change Show View into Show View. 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
[jira] Updated: (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:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-673: --- Description: From 2.1.6, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. was: From 2.2.x, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now Key: GERONIMODEVTOOLS-673 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 From 2.1.6, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-673. Resolution: Fixed Commit the patch in revision 1002477 for 2.2.1 branch, 1002478 for 2.1.6 branch, 1001147 for trunk. Thanks Janet for the patch! Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now Key: GERONIMODEVTOOLS-673 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 Attachments: GERONIMODEVTOOLS-673 .patch From 2.1.6, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMODEVTOOLS-673) Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now
Don't download TPTP runtime since maven-eclipsepde-plugin 1.1 can handle optional bundle now Key: GERONIMODEVTOOLS-673 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-673 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 From 2.2.x, building GEP will download TPTP runtime from eclipse site. In fact, it's not necessary now, since maven-eclipsepde-plugin 1.1 has been updated and we don't have to download optional bundle such as plugins in TPTP runtime. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5568) fail to asembly custom server via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMO-5568. - Resolution: Fixed it's problem of exporting plugin. Now, all deployed artifact has been in format of car package, so update original code to read from a package instead of a directory. Commit the fix in revision #997666. fail to asembly custom server via admin console Key: GERONIMO-5568 URL: https://issues.apache.org/jira/browse/GERONIMO-5568 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Assignee: Delos Dai Priority: Minor Fix For: 3.0 Attachments: hello-2.1.1.2.war setps to recur: 1、start geronimo server 2、Install hello sample (click deploy new) (attachment) 3、Open Applications -- Plugins portlet(first choosecreate Geronimo plug-in portlet,choose hello/(version)/car,then export the plug-in) 4、use the default configuration. 5、Click save plugin data button. 6、Click export plugin in next page. then you will find following infomation: ERROR [[car-export]] Servlet.service() for servlet car-export threw exception java.lang.NullPointerException at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.writeToZip(RepositoryConfigurationStore.java:280) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.exportConfiguration(RepositoryConfigurationStore.java:268) at org.apache.geronimo.console.car.CARExportServlet.doGet(CARExportServlet.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:655) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:443) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) at org.apache.geronimo.console.servlet.GenericForwardServlet.doPost(GenericForwardServlet.java:154) at org.apache.geronimo.console.servlet.GenericForwardServlet.doGet(GenericForwardServlet.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:242) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201) at org.apache.geronimo.tomcat.security.SecurityValve.invoke(SecurityValve.java:89) at org.apache.geronimo.tomcat.security.jacc.JACCSecurityValve.invoke(JACCSecurityValve.java:54) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:146) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:254) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:267) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:245) at org.apache.tomcat.util.net.JIoEndpoint
[jira] Resolved: (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 ] Delos Dai resolved GERONIMODEVTOOLS-637. Assignee: Delos Dai (was: Tim McConnell) Resolution: Fixed update testsuite 1) upgrade selenium 2) update text change in eclipse menu. commit the fix in revision #997576. 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.
[jira] Resolved: (GERONIMO-5608) Update connector attribute list for Tomcat 7
[ https://issues.apache.org/jira/browse/GERONIMO-5608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMO-5608. - Resolution: Fixed update connector attributes in TomcatManagerImpl in revision #997591. Update connector attribute list for Tomcat 7 Key: GERONIMO-5608 URL: https://issues.apache.org/jira/browse/GERONIMO-5608 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 Need to update connector attribute list in TomcatManagerImpl.java per list here http://tomcat.apache.org/tomcat-7.0-doc/config/http.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-5544) Geronimo 3.0 console-testsuite/advanced WebServerTest testEditConnector fail. The Network Listeners can not edit.
[ https://issues.apache.org/jira/browse/GERONIMO-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMO-5544. - Resolution: Fixed Connector gbean can't be found when user hopes to update port number. Just query the gbean with abstract name, then it works. Commit the fix in revision #996786 Geronimo 3.0 console-testsuite/advanced WebServerTest testEditConnector fail. The Network Listeners can not edit. - Key: GERONIMO-5544 URL: https://issues.apache.org/jira/browse/GERONIMO-5544 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: testsuite Affects Versions: 3.0 Environment: OS:ubuntu 8.04 JVM:sun 1.6.0_20 Server:geronimo-tomcat7-javaee6-3.0-SNAPSHOT build at 2010.08.20-09:46:01.318+0800 Reporter: janel Zhang Assignee: Delos Dai Fix For: 3.0 1.Create a new Tomcat BIO HTTP Connector through geronimo-tomcat7-javaee6-3.0-SNAPSHOT console:ServerWeb ServerAdd New Tomcat BIO HTTP Connector(name:uniquename2,port 8082) 2.Edit the uniquename2's port to 8083,but it can not take effect and the port can not edit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5608) Update connector attribute list for Tomcat 7
Update connector attribute list for Tomcat 7 Key: GERONIMO-5608 URL: https://issues.apache.org/jira/browse/GERONIMO-5608 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: Tomcat Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 Need to update connector attribute list in TomcatManagerImpl.java per list here http://tomcat.apache.org/tomcat-7.0-doc/config/http.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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 ] Delos Dai resolved GERONIMODEVTOOLS-658. Fix Version/s: 3.0 Resolution: Fixed 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: 3.0, 2.0.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 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] Resolved: (GERONIMODEVTOOLS-619) Implement Blueprint XML form editor
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-619. Resolution: Fixed commit the initial UI for blueprint editor, #996559 Implement Blueprint XML form editor --- Key: GERONIMODEVTOOLS-619 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-619 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 Attachments: GERONIMODEVTOOLS-619.patch Should be modeled on the web.xml and geronimo-web.xml form editor support -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-626) Implement reordering of artifacts during deployment and run-on-server functions to adhere to specified dependencies in deployment plans and/or bundle manifests to
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-626. -- Assignee: Delos Dai Resolution: Not A Problem The original code in DependencyHelper works fine in 3.0. I don't think we need other change to the reordering work. Implement reordering of artifacts during deployment and run-on-server functions to adhere to specified dependencies in deployment plans and/or bundle manifests to ensure proper start order when started on the Geronimo server Key: GERONIMODEVTOOLS-626 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-626 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 See org.apache.geronimo.st.core.DependencyHelper GEP class. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-631) Implement for any changed Geronimo-specific deployment plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-631. Fix Version/s: 3.0 Resolution: Fixed commit patch with #996601. Thanks Hong Fang Han for the patch! Implement for any changed Geronimo-specific deployment plan descriptors (via JAXB) for Web Profile server - Key: GERONIMODEVTOOLS-631 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-631 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Han Hong Fang Fix For: 3.0 Attachments: GERONIMODEVTOOLS-631(1).patch, GERONIMODEVTOOLS-631(2).patch, schema.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-661) Create JAXB model for geronimo-jaspi.xsd
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-661. Resolution: Fixed Create JAXB model for geronimo-jaspi.xsd Key: GERONIMODEVTOOLS-661 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-661 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.2.1, 3.0 Create JAXB model for geronimo-jaspi.xsd. We have generated the model in trunk. First, create plugin v22.jaxbmodel; then, for 2.2 branch, copy the model from trunk into v22.jaxbmodel;for trunk, copy the model from v30.jaxbmodel into v22.jaxbmodel -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-660) Add new schema geronimo-jaspi.xsd into GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-660. Resolution: Fixed Add new schema geronimo-jaspi.xsd into GEP -- Key: GERONIMODEVTOOLS-660 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-660 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.2.1, 3.0 From Geronimo 2.2, geronimo-jaspi.xsd is added into deployment plan. We need to add it into GEP, including 1) generate JAXB model for it 2) update old schema files in st.schema, which imports geronimo-jaspi.xsd 3) update JAXB model for changed schema files -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-662) update old schema files in st.schema and JAXB model for changed schema files
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-662. Resolution: Fixed complete in patch for GERONIMODEVTOOLS-631 update old schema files in st.schema and JAXB model for changed schema files Key: GERONIMODEVTOOLS-662 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-662 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.2.1, 3.0 1) update old schema files in st.schema, which imports geronimo-jaspi.xsd 2) update JAXB model for changed schema files -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-672) Error occurs in geronimo deployment plan when refactoring projects
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-672. Fix Version/s: 3.0 Resolution: Fixed It's caused by duplicated refactoring extension in v30.core, so remove it. Fix in revision #996604. Error occurs in geronimo deployment plan when refactoring projects -- Key: GERONIMODEVTOOLS-672 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-672 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: Eclipse 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai Fix For: 3.0 Attachments: end.png, middle.png, modify.png, new.png, upper.png Different Errors occurs in geronimo deployment plan when refactoring projects in different ways which will be showed in pictures below. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-5568) fail to asembly custom server via admin console
[ https://issues.apache.org/jira/browse/GERONIMO-5568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMO-5568: --- Assignee: Delos Dai fail to asembly custom server via admin console Key: GERONIMO-5568 URL: https://issues.apache.org/jira/browse/GERONIMO-5568 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Tomcat Affects Versions: 3.0 Environment: OS:Windows XP SP3 Java Version: 1.6.0_20 Server:Geronimo 3.0-SNAPSHOT Reporter: Zhen Zhang Assignee: Delos Dai Priority: Minor Fix For: 3.0 Attachments: hello-2.1.1.2.war setps to recur: 1、start geronimo server 2、Install hello sample (click deploy new) (attachment) 3、Open Applications -- Plugins portlet(first clickcreate Geronimo plug-in,choose hello,then export the plug-in) 4、Click Assemble a Server button then you will find following infomation: ERROR [[car-export]] Servlet.service() for servlet car-export threw exception java.lang.NullPointerException at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.writeToZip(RepositoryConfigurationStore.java:280) at org.apache.geronimo.system.configuration.RepositoryConfigurationStore.exportConfiguration(RepositoryConfigurationStore.java:268) at org.apache.geronimo.console.car.CARExportServlet.doGet(CARExportServlet.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:655) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:443) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310) at org.apache.geronimo.console.servlet.GenericForwardServlet.doPost(GenericForwardServlet.java:154) at org.apache.geronimo.console.servlet.GenericForwardServlet.doGet(GenericForwardServlet.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:575) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.geronimo.console.filter.XSSXSRFFilter.doFilter(XSSXSRFFilter.java:130) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:242) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201) at org.apache.geronimo.tomcat.security.SecurityValve.invoke(SecurityValve.java:89) at org.apache.geronimo.tomcat.security.jacc.JACCSecurityValve.invoke(JACCSecurityValve.java:54) at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:700) at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47) at org.apache.geronimo.tomcat.valve.ProtectedTargetValve.invoke(ProtectedTargetValve.java:53) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:146) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:108) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:402) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:254) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:267) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:245) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:260) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:241) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(ThreadPool.java:371) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
[jira] Assigned: (GERONIMO-5544) Geronimo 3.0 console-testsuite/advanced WebServerTest testEditConnector fail. The Network Listeners can not edit.
[ https://issues.apache.org/jira/browse/GERONIMO-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMO-5544: --- Assignee: Delos Dai Geronimo 3.0 console-testsuite/advanced WebServerTest testEditConnector fail. The Network Listeners can not edit. - Key: GERONIMO-5544 URL: https://issues.apache.org/jira/browse/GERONIMO-5544 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: testsuite Affects Versions: 3.0 Environment: OS:ubuntu 8.04 JVM:sun 1.6.0_20 Server:geronimo-tomcat7-javaee6-3.0-SNAPSHOT build at 2010.08.20-09:46:01.318+0800 Reporter: janel Zhang Assignee: Delos Dai Fix For: 3.0 1.Create a new Tomcat BIO HTTP Connector through geronimo-tomcat7-javaee6-3.0-SNAPSHOT console:ServerWeb ServerAdd New Tomcat BIO HTTP Connector(name:uniquename2,port 8082) 2.Edit the uniquename2's port to 8083,but it can not take effect and the port can not edit. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-533) Configuration in geronimo-web.xml is removed after Importing an external war to eclipse
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-533. -- Resolution: Invalid Configuration in geronimo-web.xml is removed after Importing an external war to eclipse --- Key: GERONIMODEVTOOLS-533 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-533 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.3 Environment: Suse Reporter: viola.lu Assignee: Tim McConnell Priority: Minor Attachments: example_extension.war Steps: 1.Import example-extension.war to elicpse , target runtime is geronimo 2.1 2.Open geronimo-web.xml, configuration information is remove from it but just context-root/HelloWorldPortlet/context-root left. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-597) Wrong geronimo version detect message if create more thant one server instance
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-597. -- Resolution: Cannot Reproduce Wrong geronimo version detect message if create more thant one server instance --- Key: GERONIMODEVTOOLS-597 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-597 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: os:win2003 eclipse 3.5 jdk:sun 1.5 Reporter: viola.lu Assignee: Delos Dai Priority: Minor 1.Create one geronimo 1.1 server instance, geronimo 2.2 server instance 2.Create a geornimo 2.1 server instance, install geronimo 2.1 server runtime, choose geronimo 2.1 as installation directory, but a warnig about geronimo version detection is wrong: An incorrect version of Apache Geronimo v2.1 was detected. Version 2.1 was expected, but version 2.2-SNAPSHOT was found -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-663) Remove duplicated License and Notice files in each jar when we issue mvn release:prepare
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-663. Fix Version/s: (was: 2.2.1) (was: 2.1.6) Resolution: Fixed commit for trunk in revision #993190. Thanks Han Hong Fang for the patch! Remove duplicated License and Notice files in each jar when we issue mvn release:prepare -- Key: GERONIMODEVTOOLS-663 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-663 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.6, 2.2.1, 3.0 Reporter: Delos Dai Assignee: Han Hong Fang Fix For: 3.0 Attachments: GERONIMODEVTOOLS-663.patch Remove duplicated License and Notice files in each jar when we issue mvn release:prepare -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-671) cannot start geronimo after adding javaagent arguements
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-671. -- Resolution: Fixed Thanks, Han Hong Fang! Since it's an issue of server, let's close it cannot start geronimo after adding javaagent arguements --- Key: GERONIMODEVTOOLS-671 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-671 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS:windows xp Eclipse :3.6 Geronimo :3.0 Reporter: Lu Jiang Assignee: Delos Dai Priority: Minor Attachments: jpa.jar Add something like -javaagent:D:/jpa.jar to Server VM arguements in eclipse. Then geronimo will fail to start for the following error: java.lang.reflect.InvocationTargetException 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 sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323) at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338) Caused by: java.lang.NoClassDefFoundError: org/apache/commons/lang/exception/NestableRuntimeException at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:616) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at org.apache.openjpa.enhance.PCEnhancerAgent.premain(PCEnhancerAgent.java:127) ... 6 more Caused by: java.lang.ClassNotFoundException: org.apache.commons.lang.exception.NestableRuntimeException at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) ... 19 more Exception in thread main FATAL ERROR in native method: processing of -javaagent failed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-608) Publish with GEP takes minutes, while deploy takes seconds
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12905787#action_12905787 ] Delos Dai commented on GERONIMODEVTOOLS-608: Hi Kory, I didn't see your attachment, could you attach your patch? Thanks in advance! Publish with GEP takes minutes, while deploy takes seconds -- Key: GERONIMODEVTOOLS-608 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-608 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.2.0 Environment: GEP 2.2 installed in Eclipse (galileo-SR1). Reporter: Boes Assignee: Delos Dai Attachments: getEnvironment.txt, HiThere.ear, HiThereSlow.ear, reorderModules.txt Publishing an Enterprise Application (EAR) with GEP to Geronimo takes much more time then deploying the same EAR to Geronimo using the console. See http://n3.nabble.com/Publish-with-GEP-takes-minutes-while-deploy-takes-10-seconds-td684484.html After doing some research I found that EAR's that have dependencies in geronimo-application.xml take a lot of time to publish. This is caused by the very inefficient implementation of the reorderModules method in the org.apache.geronimo.st.core.internal.DependencyHelper class. I installed a GEP development environment and put on tracing. It tested an EAR with 3 WAR's in it. In the EAR's geronimo-application.xml I added dependency tags for 4 libraries. Tracing shows that this results in parsing the geronimo-application.xml 1092 (!) times. In code this means that a call to DependencyHelper.getEnvironment is made 1092 times. Another inefficient part in the reorderModules method is that the call to DeploymentUtils.isInstalledModule is repeatedly made for the same module. In the test I found it was called at least 3 times for each dependent library. These calls result in a request to Geronimo and take almost a second each. The best way to solve this bug is to redesign the reordering process and make it work in a way that both DependencyHelper.getEnvironment and DeploymentUtils.isInstalledModule are not called more often then needed. I wonder why DeploymentUtils.isInstalledModule is called at all. Dependencies are defined in the xml. I can't imagine why it would matter if a module is installed in Geronimo or not. What I did to fix this problem and make GEP workable again for me is: - made sure the DeploymentUtils.isInstalledModule is never called twice for the same module. Once the DeploymentUtils.isInstalledModule is called for a certain module, I add this module to a list. Before a next call to DeploymentUtils.isInstalledModule I verify if the call has been made before. If so, it doesn't need to be called again. - reduced the number of times the xml is parsed. I put the results of the DependencyHelper.getEnvironment for a certain module in a hashmap. Next time the DependencyHelper.getEnvironment is called for the same module, I returns the result stored in the hashmap. After these two modifications GEP is up to speed again. Removal of the call to DeploymentUtils.isInstalledModule makes GEP even faster. Just as fast as deployment using the Geronimo console. For me this works, but I don't know what the impact is for other users. In the attached code I left it the way it was. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-636) Implement JEE5 backward capability for Geronimo 2.x servers
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-636. Fix Version/s: 3.0 Resolution: Fixed refactor code for 2.x adapters to fix issues in 2.x adapters. commit the fix in revision #990612 Implement JEE5 backward capability for Geronimo 2.x servers --- Key: GERONIMODEVTOOLS-636 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636 Project: Geronimo-Devtools Issue Type: Sub-task 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.
[jira] Resolved: (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-670. Fix Version/s: 3.0 Resolution: Fixed fix the issues you found in GERONIMODEVTOOLS-636. So mark it as resolved Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime --- Key: GERONIMODEVTOOLS-670 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: IBM JDK 6 Eclipse: 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai Fix For: 3.0 I created an web, an ejb and an ear projects using the Geronimo 2.2 as the target runtime, the geronimo deployment plans which should be in these projects don't exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-667) Configuration elements duplicated in Geronimo deployment plan editor for geronimo-application.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-667. -- Fix Version/s: 3.0 Resolution: Invalid Han Hong Fang, thanks for your clarify! So they're not duplicated elements. Let's close it! Configuration elements duplicated in Geronimo deployment plan editor for geronimo-application.xml - Key: GERONIMODEVTOOLS-667 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-667 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: Sun JDK 1.6.0_20 Eclipse 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai Fix For: 3.0 When I test the geronimo deployment plan editor for geronimo-application.xml, I found in the deployment configuration part, there are modules and external modules elements, which are duplicated in the configuration content. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-669) Modification to VM arguements is lost
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-669. Fix Version/s: 3.0 Resolution: Fixed Server VM arguments section was added because no solution found to save the VM arguments in configuration dialog. Now, I find a solution to save VM arugments in configuration dialog. I override the performApply() method in GeronimoLaunchConfigurationTabGroup. So it's time to remove VM arguments section. Submit the fix in revision #989524 Modification to VM arguements is lost -- Key: GERONIMODEVTOOLS-669 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-669 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS:win xp JDK:1.6_U18 Reporter: Lu Jiang Assignee: Delos Dai Priority: Minor Fix For: 3.0 Steps to reproduce: 1. new a Geronimo server in Eclipse 2.Double click the server,then you can see the server overview. 3.Under Gereral Information,click the link open lauch configuration. 4.Click Arguements tag,and and do some modifications to VM arguements. 5.Click Apply and OK. 6.Reopen the lauch configuration. The modifications to VM arguements are lost. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-636) Implement JEE5 backward capability for Geronimo 2.1.x servers
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-636: -- Assignee: Delos Dai Implement JEE5 backward capability for Geronimo 2.1.x servers - Key: GERONIMODEVTOOLS-636 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Delos Dai -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-636) Implement JEE5 backward capability for Geronimo 2.x servers
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-636: --- Summary: Implement JEE5 backward capability for Geronimo 2.x servers (was: Implement JEE5 backward capability for Geronimo 2.1.x servers) Implement JEE5 backward capability for Geronimo 2.x servers --- Key: GERONIMODEVTOOLS-636 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-636 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Delos Dai -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-670) Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12902304#action_12902304 ] Delos Dai commented on GERONIMODEVTOOLS-670: Now,I'm working on GERONIMODEVTOOLS-636 with some code refactoring work. This problem should be resolved, once GERONIMODEVTOOLS-636 is completed. Geronimo deployment plan doesn't be created when creating projects using the Geronimo 2.2 as the target runtime --- Key: GERONIMODEVTOOLS-670 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-670 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: IBM JDK 6 Eclipse: 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai I created an web, an ejb and an ear projects using the Geronimo 2.2 as the target runtime, the geronimo deployment plans which should be in these projects don't exist. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: How to detect status of server instance?
Thanks David Kevan! See my reply in blue. 2010/8/23 Kevan Miller kevan.mil...@gmail.com On Aug 19, 2010, at 11:17 PM, David Jencks wrote: This isn't enough information for me. What do you want to do with the information that, for instance, a karaf instance started but no geronimo bundles were started? You have no idea how to contact this karaf instance with this information, nor any information about what it can do. I think we should target our common/intended use cases, which IMO is running geronimo *servers*, not karaf instances... I agree running karaf instance doesn't means a geronimo server is running. My solution only tells status of karaf instance, but it's enough for me, I think. I don't think we should support this. I can understand trying to communicate with a server that can do something, but not detecting that a jvm started with some stuff running that has no way to communicate with the outside world. Maybe if you explain your goals I'll start thinking this might be useful IIUC, Rex wants to be able to detect running instances of Geronimo servers. This could be used by install/uninstall programs or other management tools for administering Geronimo servers. Personally, I'd like to understand what this code would look like. Is a patch available? You may find a initial patch of my solution. http://svn.apache.org/repos/asf/geronimo/sandbox/delos/status.patch I think our handling of multiple server instances could be improved. Aids to help with the creation, configuration, and control of server instances. Capturing information about running server instances might help us with some of these issues... Agree. --kevan -- Best Regards, Delos
[jira] Resolved: (GERONIMODEVTOOLS-668) Error occurs when converting apps to plugins
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-668. Fix Version/s: 3.0 Resolution: Fixed Deployed artifact has been in format of car package.It's directory before. Fix it in revision 988386 Error occurs when converting apps to plugins Key: GERONIMODEVTOOLS-668 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-668 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Wang Guang Zhe Assignee: Delos Dai Fix For: 3.0 Attachments: error.jpg I used GEP to convert an application A to an plugin but failed with the only information: Failed to save A. I will attach an image which shows the situation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-666) Error occurs when reading geronimo-web.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-666. -- Resolution: Won't Fix After mvn eclipse:eclipse, the project you importing is considered as a normal java project. None of the elements in geronimo-web.xml is replaced with real values.So it cause error when you open the file. GEP only support valid deployment plan containing real values. That's the reason why it works well for imported WAR. GEP works as design for this JIRA, so won't fix it. Error occurs when reading geronimo-web.xml -- Key: GERONIMODEVTOOLS-666 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-666 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: Sun JDK 1.6.0_20 Eclipse: 3.6 Reporter: Wang Guang Zhe Assignee: Delos Dai Attachments: jsp2.2-test-3.0-SNAPSHOT.war, jsp2.2-test.zip When I open an geronimo-web.xml which belongs to an project imported after mvn -Dwtpversion=2.0 eclipse:eclipse command, error occurs. But when reading the same file from war file imported, it runs well. The error stack is as follows: org.eclipse.ui.PartInitException: Error in loading deployment plan at org.apache.geronimo.st.ui.editors.AbstractGeronimoDeploymentPlanEditor.init(AbstractGeronimoDeploymentPlanEditor.java:219) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:647) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:289) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2863) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2768) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2760) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2711) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2707) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2691) at org.eclipse.ui.actions.OpenWithMenu.openEditor(OpenWithMenu.java:331) at org.eclipse.ui.actions.OpenWithMenu$2.handleEvent(OpenWithMenu.java:179) 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:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) 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) 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.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment
Re: How to detect status of server instance?
Let me try again to clarify my requirements and implementation. - What I want to do? I just hope to detect all running instances of a specific Geronimo installation (For multi instances configuration, see https://cwiki.apache.org/GMOxDOC22/running-multiple-geronimo-instances.html). In one word, I just need a mechanism to tell if any running instance exists or not. So far, I don't care which instance is running but only want to know if there is a running instance. - How I want to do? My solution leverages a flag file to indicate if an instance is running. When an instance is running, it will lock its flag file first; any other process or thread CAN'T lock this file any more until the instance is stopped. In this way, by checking if any of these flag files is lockable, we can know if there is a running instance. Flag file A flag file can be created and locked at the beginning when a server instance is starting. The file can also be unlocked and deleted at the ending when the serve instance is stopping. File creating and locking can be done before we start OSGi framework at the beginning of Bootstrapper.execute(); while file deleting and unlocking can be done in the thread added as shutdown hook in FrameworkLauncher.launch() (line 140). NOTE, even if server instance is stopped abnormally, its flag file will still be unlocked by JVM. API It's not difficult to create and delete flag file by File.createNewFile() and File.delete(). For locking and unlocking file, we may use FileChannel.lock() to lock a file, FileChannel.tryLock() to check if the file has been locked and FileLock.release() to unlock the file. 2010/8/18 Rex Wang rwo...@gmail.com 2010/8/18 Kevan Miller kevan.mil...@gmail.com On Aug 17, 2010, at 4:45 AM, Delos wrote: For some reasons, we often need to know if there is a running server instance. By establishing a connection to a specific port such as 1099, we may get the status of server. However, the method doesn't work if default port number is changed, especially in multi-instances scenario. In multi-instances scenario, we hope to know if any instance is running. I think we'd better do a better job of defining some requirements. I'm not sure I understand precisely what you're trying to accomplish. Some off-hand thoughts: 1) Users want to know when a server is up and running and ready to process user requests (at least that's what users have asked me for, in the past). So, the fact that a process has been started is probably not sufficient 2) I think most users will want information on a specific server, not *any* server 3) If determining the proper port to be used is a problem (and I think we should make this simpler), then the problem applies to any command stop-server, wait-for-server, deploy, list-modules, etc. wait-for-server might be a good way to address the problem, however it is a gsh command in 2.1.x Shall we resume the command in deploytool for 3.0? -Rex Below is my thoughts about the solution. Any comments or suggestions, please feel free to tell me. It will be appreciated if any better solution could be provided. Possible solution: We may create flag file for each instance and lock the file with FileChannel.lock() when a server instance is starting up. It will be unlocked and deleted when the server is stopped. Unlocking will be automatically done when JVM exits; deleting the file can be done in shutdown hook in FrameworkLauncher.launch(). In this way, if any flag file has been locked, we may deduce that there is at least one running server instance; if no locked files found, we may think all server instances are stopped. We can put all the flag files in a same directory for us to track. It's been a while since I looked at similar issues, but I'm not very trusting about how much work a Java process can be guaranteed to perform on shutdown. Normal shutdown situations work fine. But what happens when the JVM catches an abnormal signal and just exits? I'd want to see thorough testing of any file locking/file deleting technique (especially if appropriate file manipulation was required to start/restart the server). --kevan -- Lei Wang (Rex) rwonly AT apache.org -- Best Regards, Delos
[jira] Resolved: (GERONIMODEVTOOLS-648) Source release assembly contains temporary files generated in build process
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-648. Resolution: Fixed verified it with mvn -DdryRun=true release:prepare. So mark it as resolved Source release assembly contains temporary files generated in build process --- Key: GERONIMODEVTOOLS-648 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-648 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.6, 2.2.1, 3.0_M1, 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.1.6, 2.2.1, 3.0_M1, 3.0 Currently, apache 5 is the parent of geronimo-eclipse-plugin.Besides, I added configuration to its pom.xml introduced here http://maven.apache.org/developers/release/apache-release.html. But the result is, after we complete release prepare and perform, the source assembly contains all the temporary files generated by maven, such as target directory and pom.releaseBackup. Seems the configuration doesn't work for GEP. I found source assembly for Geronimo Server works fine because it uses a different source assembly dependency from apache 5 or 6, that is apache-source-release-assembly-descriptor in group org.apache.geronimo.genesis. So I did these changes to root pom.xml. 1) Update apache 5 to apache 6, which is also used by Geronimo server 3.0 2) copy apache-release profile snippet from genesis-2.0.pom -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-634) Implement identification of valid/invalid packaging for Web Profile prior to deployment
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-634: --- Affects Version/s: (was: 3.0) Implement identification of valid/invalid packaging for Web Profile prior to deployment --- Key: GERONIMODEVTOOLS-634 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-634 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Reporter: Tim McConnell Assignee: Delos Dai i.e., do not rely solely on the Geronimo deployment process to identify these types of errors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-634) Implement identification of valid/invalid packaging for Web Profile prior to deployment
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-634. Assignee: Delos Dai Fix Version/s: (was: 3.0) Resolution: Later We may leverage facet definition in WST to check if a package depends on features beyond Web Profile. But I'm afraid it's not accurate. Eg, we can't distinguish EJB 3.1 full from EJB 3.1 lite, there is only jst.ejb 3.1 defined in WST. That is a potential issue. Besides, it's not a must-to-have feature. So defer it until we have better solution. Implement identification of valid/invalid packaging for Web Profile prior to deployment --- Key: GERONIMODEVTOOLS-634 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-634 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Reporter: Tim McConnell Assignee: Delos Dai i.e., do not rely solely on the Geronimo deployment process to identify these types of errors -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
How to detect status of server instance?
For some reasons, we often need to know if there is a running server instance. By establishing a connection to a specific port such as 1099, we may get the status of server. However, the method doesn't work if default port number is changed, especially in multi-instances scenario. In multi-instances scenario, we hope to know if any instance is running. Below is my thoughts about the solution. Any comments or suggestions, please feel free to tell me. It will be appreciated if any better solution could be provided. Possible solution: We may create flag file for each instance and lock the file with FileChannel.lock() when a server instance is starting up. It will be unlocked and deleted when the server is stopped. Unlocking will be automatically done when JVM exits; deleting the file can be done in shutdown hook in FrameworkLauncher.launch(). In this way, if any flag file has been locked, we may deduce that there is at least one running server instance; if no locked files found, we may think all server instances are stopped. We can put all the flag files in a same directory for us to track. -- Best Regards, Delos
[DISCUSSION] How to detect status of server instance?
2010/8/17 Delos dait...@gmail.com For some reasons, we often need to know if there is a running server instance. By establishing a connection to a specific port such as 1099, we may get the status of server. However, the method doesn't work if default port number is changed, especially in multi-instances scenario. In multi-instances scenario, we hope to know if any instance is running. Below is my thoughts about the solution. Any comments or suggestions, please feel free to tell me. It will be appreciated if any better solution could be provided. Possible solution: We may create flag file for each instance and lock the file with FileChannel.lock() when a server instance is starting up. It will be unlocked and deleted when the server is stopped. Unlocking will be automatically done when JVM exits; deleting the file can be done in shutdown hook in FrameworkLauncher.launch(). In this way, if any flag file has been locked, we may deduce that there is at least one running server instance; if no locked files found, we may think all server instances are stopped. We can put all the flag files in a same directory for us to track. -- Best Regards, Delos -- Best Regards, Delos
[jira] Resolved: (GERONIMODEVTOOLS-665) Error occurs when deploying EBA package
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-665. Fix Version/s: 3.0 Resolution: Fixed It should have been resolved, since GERONIMODEVTOOLS-656 is fixed. Error occurs when deploying EBA package --- Key: GERONIMODEVTOOLS-665 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-665 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP SP3 JDK: Sun JDK 1.6.0_20 Reporter: Wang Guang Zhe Assignee: Delos Dai Fix For: 3.0 Attachments: com.example.helloworld.eba-0.1-incubating.eba When deploying an EBA package to the Geronimo trunk server through GEP, error occurs. This package has been successfully deployed directly to the trunk server and run correctly. The error stack is as follows: NLS missing message: DISTRIBUTE_FAIL in: org.apache.geronimo.st.v30.core.internal.Messages No plan or module specified org.apache.geronimo.common.DeploymentException: No plan or module specified at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:217) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) 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.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:872) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:836) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:761) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427) at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367) at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugin
maven-plugin 1.1 has passed the voting with following result: +1: Delos, Donald, Kevan, Ivan -1: no 0: no I will promote the artifacts in repository. Thank you all! 2010/8/16 Ivan xhh...@gmail.com +1 2010/8/13 Donald Woods dwo...@apache.org +1 source-release passed rat:check and was able to build it on Mac with Maven 2.2.1 and 1.6.0_20. -Donald On 8/10/10 10:42 PM, Delos wrote: Hi all, This is the second try for releasing maven-plugins 1.1 used by GEP. I have created the buildable source distribution for it. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. Source distribution: https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.zip Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-093 svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1 [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Ivan -- Best Regards, Delos
[jira] Resolved: (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:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-649. Resolution: Fixed update maven-eclipsepde-plugin to 1.1, in revision #985848 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] Resolved: (GERONIMODEVTOOLS-656) Failed to deploy aries samples
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-656. Fix Version/s: 3.0 Resolution: Fixed GERONIMODEVTOOLS-658 has been fixed, so commit fix for this JIRA in revision 986167 Failed to deploy aries samples -- Key: GERONIMODEVTOOLS-656 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-656 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Chris Zhang Assignee: Delos Dai Fix For: 3.0 Attachments: com.example.helloworld.eba-1.0.0.eba I write an simple aries sample named hello world and I failed to deploy it. The exception stack is: Deployer operation failed: No plan or module specified org.apache.geronimo.common.DeploymentException: No plan or module specified at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:217) at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:856) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.kernel.KernelGBean.invoke(KernelGBean.java:344) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:131) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:856) at org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:245) at org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(Unknown Source) at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$200(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) And the attachment is the hello world aries sample. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-5525) Geronimo launch failed for Multiple Geronimo Instances
Geronimo launch failed for Multiple Geronimo Instances --- Key: GERONIMO-5525 URL: https://issues.apache.org/jira/browse/GERONIMO-5525 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: startup/shutdown Affects Versions: 3.0 Reporter: Delos Dai According to the configuration https://cwiki.apache.org/GMOxDOC22/running-multiple-geronimo-instances.html, I configure Geronimo 3.0 trunk build, but it can't start in case of multi instances. Here is the error message after geronimo run, Error launching framework: java.lang.NullPointerException -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugin (2nd try)
Thanks, Kevan! Hope other PMC members can take a look at this. 2010/8/12 Kevan Miller kevan.mil...@gmail.com +1 Source, signature/checksums, build, all look good. Note that the NOTICE file is out-of-date: = == NOTICE file corresponding to section 4(d) of the Apache License, == == Version 2.0, in this case for the Apache Geronimo distribution.== = should not be in the NOTICE file. IMO, this is not a blocking issue. But please delete from development trunk/branches, so it won't be included in future releases. --kevan On Aug 10, 2010, at 10:42 PM, Delos wrote: Hi all, This is the second try for releasing maven-plugins 1.1 used by GEP. I have created the buildable source distribution for it. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. Source distribution: https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.zip Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-093 svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1 [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugin (2nd try)
my own +1 for it 2010/8/11 Delos dait...@gmail.com Hi all, This is the second try for releasing maven-plugins 1.1 used by GEP. I have created the buildable source distribution for it. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. Source distribution: https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.zip Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-093 svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1 [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos
[jira] Closed: (GERONIMODEVTOOLS-657) When importing the aries blog and trader samples, the content of manifest file changed.
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-657. -- Resolution: Won't Fix It's a problem of free Aries tools. With latest version, the problem has been fixed. When importing the aries blog and trader samples, the content of manifest file changed. --- Key: GERONIMODEVTOOLS-657 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-657 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Environment: OS: Windows XP JDK: 1.6_20 Eclipse: 3.6 Reporter: Chris Zhang Assignee: Delos Dai Attachments: org.apache.aries.samples.ariestrader.jdbc-0.1-incubating.eba, org.apache.aries.samples.blog.jdbc.eba-0.1-incubating.eba When I import the aries blog sample and the aries trader sample into eclipse, the content of MANIFEST.MF file of their web bundle change. But the MANIFEST.MF file of other bundles don't change. Take the blog sample for instance, the content of original MANIFEST.MF is : Manifest-Version: 1.0 Implementation-Title: Apache Aries Implementation-Version: 0.1-incubating Built-By: admin Tool: Bnd-0.0.357 Bundle-Name: Apache Aries blog sample web component Created-By: Apache Maven Bundle Plugin Web-ContextPath: /blog Bundle-Vendor: The Apache Software Foundation Build-Jdk: 1.6.0_20 Bundle-Version: 0.1.0.incubating Bnd-LastModified: 1277349176296 Bundle-ManifestVersion: 2 Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt Bundle-Description: Aries top-level parent pom Bundle-DocURL: http://www.apache.org Bundle-SymbolicName: org.apache.aries.samples.blog.web Import-Package: javax.naming,javax.servlet;version=2.5,javax.servlet .http;version=2.5,org.apache.aries.samples.blog.api;version=[0.1,1 ) And in eclipse, its content is: Manifest-Version: 1.0 Bundle-ManifestVersion: 2 Bundle-Name: org.apache.aries.samples.blog.web Bundle-SymbolicName: org.apache.aries.samples.blog.web Bundle-Version: 1.0.0.qualifier Bundle-RequiredExecutionEnvironment: JavaSE-1.6 Import-Package: javax.servlet;version=2.5, javax.el;version=2.0;resolution:=optional, javax.servlet.jsp.el;version=2.0, javax.servlet.jsp.tagext;version=2.0, javax.servlet.jsp;version=2.0, javax.servlet.http;version=2.5 Web-ContextPath: /blog Please review it. Thanks. P.S The attachments are the eba files of the two samples. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMODEVTOOLS-630) Implement any new Geronimo-specific plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai closed GERONIMODEVTOOLS-630. -- Resolution: Duplicate Duplicate with GERONIMODEVTOOLS-631, we will handle all new plan and changed plan there. Implement any new Geronimo-specific plan descriptors (via JAXB) for Web Profile server -- Key: GERONIMODEVTOOLS-630 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-630 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Delos Dai -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-630) Implement any new Geronimo-specific plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-630: -- Assignee: Delos Dai Implement any new Geronimo-specific plan descriptors (via JAXB) for Web Profile server -- Key: GERONIMODEVTOOLS-630 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-630 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Delos Dai -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-631) Implement for any changed Geronimo-specific deployment plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-631: -- Assignee: Han Hong Fang Implement for any changed Geronimo-specific deployment plan descriptors (via JAXB) for Web Profile server - Key: GERONIMODEVTOOLS-631 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-631 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Han Hong Fang Attachments: GERONIMODEVTOOLS-631(1).patch, GERONIMODEVTOOLS-631(2).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-644) Refactor code for Geronimo 2.2.x branch
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-644. Resolution: Fixed complete the refactoring work. Refactor code for Geronimo 2.2.x branch --- Key: GERONIMODEVTOOLS-644 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-644 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.1 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.2.1 Similar to what we did for GEP trunk, we make st.core and st.ui version independent. We did this to avoid potential problems such as ClassCastException. Before, changes in GEP server dependency may cause issues during class cast. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-660) Add new schema geronimo-jaspi.xsd into GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896823#action_12896823 ] Delos Dai commented on GERONIMODEVTOOLS-660: Part of the job has been included in patch for GERONIMODEVTOOLS-631. I will go back to this JIRA after review the patch for 631 Add new schema geronimo-jaspi.xsd into GEP -- Key: GERONIMODEVTOOLS-660 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-660 Project: Geronimo-Devtools Issue Type: Task Components: eclipse-plugin Affects Versions: 2.2.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.2.1, 3.0 From Geronimo 2.2, geronimo-jaspi.xsd is added into deployment plan. We need to add it into GEP, including 1) generate JAXB model for it 2) update old schema files in st.schema, which imports geronimo-jaspi.xsd 3) update JAXB model for changed schema files -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-631) Implement for any changed Geronimo-specific deployment plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12896824#action_12896824 ] Delos Dai commented on GERONIMODEVTOOLS-631: Thanks, Janet! I will review the patch later. Implement for any changed Geronimo-specific deployment plan descriptors (via JAXB) for Web Profile server - Key: GERONIMODEVTOOLS-631 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-631 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Han Hong Fang Attachments: GERONIMODEVTOOLS-631(1).patch, GERONIMODEVTOOLS-631(2).patch, schema.zip -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
OK, I got your meaning. I was confused by source jar and source-release zip. It's the first time maven-plugin is released with release plugin, the source-release zip file is missing. There must be some mis-configure in its pom. I will investigate it. 2010/8/10 Kevan Miller kevan.mil...@gmail.com On Aug 9, 2010, at 10:26 PM, Delos wrote: Hi Kevan, Thanks for your reply! maven-plugin 1.1 is parent of maven-eclipsepde-plugin 1.1. We only have source code for maven-eclipsepde-plugin. You may find it under https://repository.apache.org/content/repositories/orgapachegeronimo-030/org/apache/geronimo/devtools/maven-eclipsepde-plugin/1.1/ Right. That's the sources jar file, I mentioned. The jar file is not a replacement for a source distribution file. As you note, it does not contain the necessary files (to build). Do you mean maven-eclipsepde-plugin-1.1-sources.jar is not buildable? It's generated by release plugin. All the source jar generated by the plugin doesn't contain a pom, so we can't build it. Is there anything wrong in my understanding? See http://repo2.maven.org/maven2/org/apache/geronimo/components/geronimo-txmanager-parent/3.0/for examples of source distributions, n If you hope to build the source, I'm afraid you need to check out the tag first. http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ No. As a release manager, you are preparing a source distribution file. That is the artifact(s) that the community is releasing. Our community expects that the contents of this source distribution will match the contents of the svn tag. However, the vote should be performed on the source distribution file (not svn). In case there's any question, I'm -1 until this issue is resolved. --kevan -- Best Regards, Delos
Cancel - Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
Cancel this voting. As Kevan mentioned, we have no source-release file generated. So I have to regenerate the staging repository. I will re-launch the voting once a new staging repository is set up. 2010/8/10 Delos dait...@gmail.com OK, I got your meaning. I was confused by source jar and source-release zip. It's the first time maven-plugin is released with release plugin, the source-release zip file is missing. There must be some mis-configure in its pom. I will investigate it. 2010/8/10 Kevan Miller kevan.mil...@gmail.com On Aug 9, 2010, at 10:26 PM, Delos wrote: Hi Kevan, Thanks for your reply! maven-plugin 1.1 is parent of maven-eclipsepde-plugin 1.1. We only have source code for maven-eclipsepde-plugin. You may find it under https://repository.apache.org/content/repositories/orgapachegeronimo-030/org/apache/geronimo/devtools/maven-eclipsepde-plugin/1.1/ Right. That's the sources jar file, I mentioned. The jar file is not a replacement for a source distribution file. As you note, it does not contain the necessary files (to build). Do you mean maven-eclipsepde-plugin-1.1-sources.jar is not buildable? It's generated by release plugin. All the source jar generated by the plugin doesn't contain a pom, so we can't build it. Is there anything wrong in my understanding? See http://repo2.maven.org/maven2/org/apache/geronimo/components/geronimo-txmanager-parent/3.0/for examples of source distributions, n If you hope to build the source, I'm afraid you need to check out the tag first. http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ No. As a release manager, you are preparing a source distribution file. That is the artifact(s) that the community is releasing. Our community expects that the contents of this source distribution will match the contents of the svn tag. However, the vote should be performed on the source distribution file (not svn). In case there's any question, I'm -1 until this issue is resolved. --kevan -- Best Regards, Delos -- Best Regards, Delos
[VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugin (2nd try)
Hi all, This is the second try for releasing maven-plugins 1.1 used by GEP. I have created the buildable source distribution for it. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. Source distribution: https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-093/org/apache/geronimo/devtools/maven-plugins/1.1/maven-plugins-1.1-source-release.zip Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-093 svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1 [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
Hi Kevan, Thanks for your reply! maven-plugin 1.1 is parent of maven-eclipsepde-plugin 1.1. We only have source code for maven-eclipsepde-plugin. You may find it under https://repository.apache.org/content/repositories/orgapachegeronimo-030/org/apache/geronimo/devtools/maven-eclipsepde-plugin/1.1/ https://repository.apache.org/content/repositories/orgapachegeronimo-030/org/apache/geronimo/devtools/maven-eclipsepde-plugin/1.1/Do you mean maven-eclipsepde-plugin-1.1-sources.jar is not buildable? It's generated by release plugin. All the source jar generated by the plugin doesn't contain a pom, so we can't build it. Is there anything wrong in my understanding? If you hope to build the source, I'm afraid you need to check out the tag first. http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ 2010/8/9 Kevan Miller kevan.mil...@gmail.com Can you point to me to the source distribution for this release? I just found a sources jar, which is not buildable. All of our releases should have a source distribution and that's what we should be voting on. --kevan On Jul 27, 2010, at 10:15 AM, Delos wrote: Hi all, Hope you're not surprised at this voting. Actually, I have discussed it with Kevan and Donald. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
Now, we have Ivan and Donald +1 for maven-plugin 1.1. Hope other PMC members can take a look at this.Thanks! 2010/8/6 Delos dait...@gmail.com Thanks, Donald! By now, we need another one voting for this! 2010/8/5 Donald Woods dwo...@apache.org +1 Passed rat:check, built tag with 1.6.0_20, jar contains required License/Notice files. -Donald On 7/27/10 10:15 AM, Delos wrote: Hi all, Hope you're not surprised at this voting. Actually, I have discussed it with Kevan and Donald. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
Thanks, Donald! By now, we need another one voting for this! 2010/8/5 Donald Woods dwo...@apache.org +1 Passed rat:check, built tag with 1.6.0_20, jar contains required License/Notice files. -Donald On 7/27/10 10:15 AM, Delos wrote: Hi all, Hope you're not surprised at this voting. Actually, I have discussed it with Kevan and Donald. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos
[jira] Resolved: (GERONIMODEVTOOLS-664) Update required WTP version number in feature.xml
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-664. Resolution: Fixed commit the fix in revision #982876. Thanks Janet for the patch! Janet, it would be better if you update configuration of subversion client according to https://cwiki.apache.org/GMOxDEV/subversion-client-configuration.html. Update required WTP version number in feature.xml - Key: GERONIMODEVTOOLS-664 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-664 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Han Hong Fang Fix For: 3.0 Attachments: GERONIMODEVTOOLS-664.patch Since GEP 3.0 can only run on WTP 3.2, we need to update WTP version constraints in feature.xml. Then, GEP 3.0 will only be installed on Eclipse 3.6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-615) Implement deploy, redeploy, and un-deploy of OSGi spec-compliant artifacts to Geronimo server:
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-615. Resolution: Fixed free Aries tools has provided a fix for CBA.So close it. Implement deploy, redeploy, and un-deploy of OSGi spec-compliant artifacts to Geronimo server: Key: GERONIMODEVTOOLS-615 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-615 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Tim McConnell Fix For: 3.0 Must include the following artifacts: o EBA o WAB o OSGi bundle o OSGi Blueprint bundle -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-616) Implement run-on-server function from Eclipse workspace for OSGi spec-compliant workspace artifacts
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-616. Resolution: Fixed free Aries tools has provided a fix for CBA.So close it. Implement run-on-server function from Eclipse workspace for OSGi spec-compliant workspace artifacts --- Key: GERONIMODEVTOOLS-616 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-616 Project: Geronimo-Devtools Issue Type: Sub-task Reporter: Tim McConnell Assignee: Tim McConnell -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-629) Implement any changed JEE6 deployment plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-629: --- Assignee: Delos Dai Priority: Minor (was: Major) Implement any changed JEE6 deployment plan descriptors (via JAXB) for Web Profile server Key: GERONIMODEVTOOLS-629 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-629 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Priority: Minor Fix For: 3.0 o Servlet 3.0 o JavaServer Pages (JSP) 2.2 o Expression Language (EL) 2.2 o Standard Tag Library for JavaServer Pages (JSTL) 1.2 o JavaServer Faces (JSF) 2.0 o Common Annotations for Java Platform (JSR-250) 1.1 o Enterprise JavaBeans (EJB) 3.1 Lite o Java Transaction API (JTA) 1.1 o Java Persistence API (JPA) 2.0 o Interceptors 1.1 o Debugging Support for Other Languages (JSR-45) 1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-629) Implement any changed JEE6 deployment plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-629. Resolution: Later Deployment descriptor is provided by WTP itself. Unless GEP decided to provide its own editor for these files, there is no need to generate JAXB classes for these descriptors. So defer it until other JIRAs with higher priority have been fixed Implement any changed JEE6 deployment plan descriptors (via JAXB) for Web Profile server Key: GERONIMODEVTOOLS-629 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-629 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Priority: Minor Fix For: 3.0 o Servlet 3.0 o JavaServer Pages (JSP) 2.2 o Expression Language (EL) 2.2 o Standard Tag Library for JavaServer Pages (JSTL) 1.2 o JavaServer Faces (JSF) 2.0 o Common Annotations for Java Platform (JSR-250) 1.1 o Enterprise JavaBeans (EJB) 3.1 Lite o Java Transaction API (JTA) 1.1 o Java Persistence API (JPA) 2.0 o Interceptors 1.1 o Debugging Support for Other Languages (JSR-45) 1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-628) Implement any new JEE6 deployment plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-628: --- Assignee: Delos Dai Priority: Minor (was: Major) Implement any new JEE6 deployment plan descriptors (via JAXB) for Web Profile server Key: GERONIMODEVTOOLS-628 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-628 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Priority: Minor Fix For: 3.0 o New descriptors related to JAX-RS o Managed Beans 1.0 o Web Beans (JSR-299) 1.0 o Dependency Injection (JSR-330) 1.0 o Bean Validation 1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMODEVTOOLS-628) Implement any new JEE6 deployment plan descriptors (via JAXB) for Web Profile server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-628. Resolution: Later Deployment descriptor is provided by WTP itself. Unless GEP decided to provide its own editor for these files, there is no need to generate JAXB classes for these descriptors. So defer it until other JIRAs with higher priority have been fixed Implement any new JEE6 deployment plan descriptors (via JAXB) for Web Profile server Key: GERONIMODEVTOOLS-628 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-628 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Priority: Minor Fix For: 3.0 o New descriptors related to JAX-RS o Managed Beans 1.0 o Web Beans (JSR-299) 1.0 o Dependency Injection (JSR-330) 1.0 o Bean Validation 1.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
It needs another two voting from PMC. It's key for fixing GERONIMODEVTOOLS-658https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 2010/8/3 Ivan xhh...@gmail.com +1 mvn rat:check pass 2010/7/30 Delos dait...@gmail.com We need to release the maven plugin to fix JIRA GERONIMODEVTOOLS-658https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658. Could PMC members take a look at this? 2010/7/29 Delos dait...@gmail.com my own +1. Is there anyone can take a look at this? 2010/7/27 Delos dait...@gmail.com Hi all, Hope you're not surprised at this voting. Actually, I have discussed it with Kevan and Donald. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos -- Best Regards, Delos -- Ivan -- Best Regards, Delos
[jira] Created: (GERONIMODEVTOOLS-664) Update required WTP version number in feature.xml
Update required WTP version number in feature.xml - Key: GERONIMODEVTOOLS-664 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-664 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 3.0 Since GEP 3.0 can only run on WTP 3.2, we need to update WTP version constraints in feature.xml. Then, GEP 3.0 will only be installed on Eclipse 3.6. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] External tomcat-parent-6.0.29.0
Thanks, Vamsavardhana! 2010/8/2 Vamsavardhana Reddy c1vams...@gmail.com +1 Delos, you now have the required PMC votes. On Fri, Jul 23, 2010 at 4:58 PM, Delos dait...@gmail.com wrote: This voting is for mavenized tomcat 6.0.29. Following what we did to tomcat 6.0.20, we are using a forked copy of tomcat derived from the tomcat 6.0.29 release, built with maven, with maven dependencies, etc etc. Besides, we also applied some patches which haven't been included in tomcat 6.0.29. Based on tomcat 6.0.29 tag, I also applied another couple of patches: GERONIMO-3451 'Restricted listeners property file not found' error logged during Tomcat server startup GERONIMO-4685 Include patches for revision #790742 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-028/ svn tag at: http://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.29.0/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks a lot! -- Best Regards, Delos -- Vamsi -- Best Regards, Delos
[RESULT] [VOTE] External tomcat-parent-6.0.29.0
tomcat-parent-6.0.29.0 passed the voting with following result: +1: Donald(PMC), Ivan(PMC), Vamsavardhana(PMC), Rex, Shawn,Delos 0: no -1: no I will promote the artifact in repository and update tomcat version in 2.1 and 2.2 branches. Thanks! 2010/8/3 Delos dait...@gmail.com Thanks, Vamsavardhana! 2010/8/2 Vamsavardhana Reddy c1vams...@gmail.com +1 Delos, you now have the required PMC votes. On Fri, Jul 23, 2010 at 4:58 PM, Delos dait...@gmail.com wrote: This voting is for mavenized tomcat 6.0.29. Following what we did to tomcat 6.0.20, we are using a forked copy of tomcat derived from the tomcat 6.0.29 release, built with maven, with maven dependencies, etc etc. Besides, we also applied some patches which haven't been included in tomcat 6.0.29. Based on tomcat 6.0.29 tag, I also applied another couple of patches: GERONIMO-3451 'Restricted listeners property file not found' error logged during Tomcat server startup GERONIMO-4685 Include patches for revision #790742 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-028/ svn tag at: http://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.29.0/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks a lot! -- Best Regards, Delos -- Vamsi -- Best Regards, Delos -- Best Regards, Delos
[jira] Assigned: (GERONIMODEVTOOLS-627) Implement introspection on Geronimo server to determine its capabilities
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-627: -- Assignee: Delos Dai Implement introspection on Geronimo server to determine its capabilities Key: GERONIMODEVTOOLS-627 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-627 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 May already be supported by WTP. For example: o Full JEE6 spec-compliant server o Full Web Profile spec-compliant server o Derivation of either -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-627) Implement introspection on Geronimo server to determine its capabilities
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1289#action_1289 ] Delos Dai commented on GERONIMODEVTOOLS-627: AFAIK, WTP doesn't care if the server is full JEE6 compliant or Web Profile compliant. It support all types of JEE6 modules. If we need to distinguish Geronimo JEE6 server and Geronimo Web Profile Server, we need a flag in server installation to indicate this. Then, GEP will check project to be deployed per server type. This task affect several tasks: GERONIMODEVTOOLS-632,GERONIMODEVTOOLS-633,GERONIMODEVTOOLS-634. Implement introspection on Geronimo server to determine its capabilities Key: GERONIMODEVTOOLS-627 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-627 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 May already be supported by WTP. For example: o Full JEE6 spec-compliant server o Full Web Profile spec-compliant server o Derivation of either -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-632) Implement usage scenarios where target runtime is or isn't a Web Profile type server configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-632: -- Assignee: Delos Dai Implement usage scenarios where target runtime is or isn't a Web Profile type server configuration Key: GERONIMODEVTOOLS-632 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-632 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 i.e., only WAR-type artifacts should be deployed on a Web Profile server -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMODEVTOOLS-611) JEE6 Enhancements
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-611: -- Assignee: Delos Dai JEE6 Enhancements - Key: GERONIMODEVTOOLS-611 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-611 Project: Geronimo-Devtools Issue Type: Improvement 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.
[jira] Assigned: (GERONIMODEVTOOLS-625) Implement run-on-server function from Eclipse workspace for JEE6/Web Profile spec-compliant workspace artifacts to the Geronimo server with/without Geronimo-spe
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-625: -- Assignee: Delos Dai Implement run-on-server function from Eclipse workspace for JEE6/Web Profile spec-compliant workspace artifacts to the Geronimo server with/without Geronimo-specific deployment descriptors Key: GERONIMODEVTOOLS-625 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-625 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: [VOTE] External tomcat-parent-6.0.29.0
Thanks for all your review! 2010/7/30 Rex Wang rwo...@gmail.com build successfully and signature/checksum looks good. +1 -Rex 2010/7/23 Delos dait...@gmail.com This voting is for mavenized tomcat 6.0.29. Following what we did to tomcat 6.0.20, we are using a forked copy of tomcat derived from the tomcat 6.0.29 release, built with maven, with maven dependencies, etc etc. Besides, we also applied some patches which haven't been included in tomcat 6.0.29. Based on tomcat 6.0.29 tag, I also applied another couple of patches: GERONIMO-3451 'Restricted listeners property file not found' error logged during Tomcat server startup GERONIMO-4685 Include patches for revision #790742 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-028/ svn tag at: http://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.29.0/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks a lot! -- Best Regards, Delos -- Lei Wang (Rex) rwonly AT apache.org -- Best Regards, Delos
[jira] Resolved: (GERONIMODEVTOOLS-625) Implement run-on-server function from Eclipse workspace for JEE6/Web Profile spec-compliant workspace artifacts to the Geronimo server with/without Geronimo-spe
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-625. Resolution: Fixed This JIRA already implemented when we update to WTP 3.2. So close it. If any other problems on run-on-server, please open a new JIRA Implement run-on-server function from Eclipse workspace for JEE6/Web Profile spec-compliant workspace artifacts to the Geronimo server with/without Geronimo-specific deployment descriptors Key: GERONIMODEVTOOLS-625 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-625 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.
[jira] Resolved: (GERONIMODEVTOOLS-624) Implement deploy, redeploy, and un-deploy of JEE6/Web Profile spec-compliant artifacts to the Geronimo server (with/without Geronimo-specific deployment descrip
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-624. Resolution: Fixed This JIRA already implemented when we update to WTP 3.2. So close it. If any other issues, please open a new JIRA. Implement deploy, redeploy, and un-deploy of JEE6/Web Profile spec-compliant artifacts to the Geronimo server (with/without Geronimo-specific deployment descriptor) Key: GERONIMODEVTOOLS-624 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-624 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 Must include the following artifacts: o EAR o EJB o WAR o JAR -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] External tomcat-parent-6.0.29.0
We still need one more voting from PMC members!-:) 2010/8/2 Delos dait...@gmail.com Thanks for all your review! 2010/7/30 Rex Wang rwo...@gmail.com build successfully and signature/checksum looks good. +1 -Rex 2010/7/23 Delos dait...@gmail.com This voting is for mavenized tomcat 6.0.29. Following what we did to tomcat 6.0.20, we are using a forked copy of tomcat derived from the tomcat 6.0.29 release, built with maven, with maven dependencies, etc etc. Besides, we also applied some patches which haven't been included in tomcat 6.0.29. Based on tomcat 6.0.29 tag, I also applied another couple of patches: GERONIMO-3451 'Restricted listeners property file not found' error logged during Tomcat server startup GERONIMO-4685 Include patches for revision #790742 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-028/ svn tag at: http://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.29.0/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks a lot! -- Best Regards, Delos -- Lei Wang (Rex) rwonly AT apache.org -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] External tomcat-parent-6.0.29.0
Thanks, Donald! 2010/7/29 Donald Woods dwo...@apache.org +1 Was able to build the tag and the jars looked like they have the required License/Notice files. -Donald On 7/23/10 7:28 AM, Delos wrote: This voting is for mavenized tomcat 6.0.29. Following what we did to tomcat 6.0.20, we are using a forked copy of tomcat derived from the tomcat 6.0.29 release, built with maven, with maven dependencies, etc etc. Besides, we also applied some patches which haven't been included in tomcat 6.0.29. Based on tomcat 6.0.29 tag, I also applied another couple of patches: GERONIMO-3451 'Restricted listeners property file not found' error logged during Tomcat server startup GERONIMO-4685 Include patches for revision #790742 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-028/ svn tag at: http://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.29.0/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks a lot! -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
We need to release the maven plugin to fix JIRA GERONIMODEVTOOLS-658https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658. Could PMC members take a look at this? 2010/7/29 Delos dait...@gmail.com my own +1. Is there anyone can take a look at this? 2010/7/27 Delos dait...@gmail.com Hi all, Hope you're not surprised at this voting. Actually, I have discussed it with Kevan and Donald. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos -- Best Regards, Delos
Re: [VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
my own +1. Is there anyone can take a look at this? 2010/7/27 Delos dait...@gmail.com Hi all, Hope you're not surprised at this voting. Actually, I have discussed it with Kevan and Donald. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos -- Best Regards, Delos
[jira] Assigned: (GERONIMODEVTOOLS-623) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai reassigned GERONIMODEVTOOLS-623: -- Assignee: Delos Dai Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime --- Key: GERONIMODEVTOOLS-623 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 Must include the following artifacts: o EBA o WAB o OSGi bundle o OSGi Blueprint bundle -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMODEVTOOLS-623) Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai updated GERONIMODEVTOOLS-623: --- Priority: Minor (was: Major) I think Admin Console will finally provide portlet for user to start/stop/restart OSGi artifacts. So it may be duplicated. Update the task with lower priority. Implement finer granularity of start/stop/restart operations on OSGi artifacts deployed on the Geronimo runtime --- Key: GERONIMODEVTOOLS-623 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-623 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Priority: Minor Fix For: 3.0 Must include the following artifacts: o EBA o WAB o OSGi bundle o OSGi Blueprint bundle -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-663) Remove duplicated License and Notice files in each jar when we issue mvn release:prepare
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893498#action_12893498 ] Delos Dai commented on GERONIMODEVTOOLS-663: During release process, LICENSE and NOTICE file will automatically pulled in MANIFEST directory of final jar file. So we don't need to keep LICENSE.txt and NOTICE.txt in source code of each plugins. Remove duplicated License and Notice files in each jar when we issue mvn release:prepare -- Key: GERONIMODEVTOOLS-663 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-663 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.6, 2.2.1, 3.0 Reporter: Delos Dai Assignee: Delos Dai Fix For: 2.1.6, 2.2.1, 3.0 Remove duplicated License and Notice files in each jar when we issue mvn release:prepare -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMODEVTOOLS-619) Implement Blueprint XML form editor
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12893500#action_12893500 ] Delos Dai commented on GERONIMODEVTOOLS-619: Kan, Thanks! I've corrected it. Implement Blueprint XML form editor --- Key: GERONIMODEVTOOLS-619 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-619 Project: Geronimo-Devtools Issue Type: Sub-task Components: eclipse-plugin Affects Versions: 3.0 Reporter: Tim McConnell Assignee: Delos Dai Fix For: 3.0 Attachments: GERONIMODEVTOOLS-619.patch Should be modeled on the web.xml and geronimo-web.xml form editor support -- 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=12892782#action_12892782 ] Delos Dai commented on GERONIMODEVTOOLS-649: This issue may be resolved once GERONIMODEVTOOLS-658 is fixed. 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.
[VOTE] maven-plugins 1.1 for Geronimo Eclipse Plugins
Hi all, Hope you're not surprised at this voting. Actually, I have discussed it with Kevan and Donald. As part of GEP, maven-eclipsepde-plugin helps to convert eclipse plugins to maven dependencies and add them into artifact dependency list.But now, we have to update the plugin to accommodate new requirements. See more details here https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 I will prompt the new plugins once it passes the voting. https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-658 Staging repo: https://repository.apache.org/content/repositories/orgapachegeronimo-030/ svn tag at: http://svn.apache.org/repos/asf/geronimo/devtools/maven-plugins/tags/1.1/ [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute -- Best Regards, Delos
