Re: buildup of files in var/cache
Just find the it is caused by store manager, it did not remove the old managed files while it switches to a new one. Although there is a property could be used to clean up the temp file, it is required to restart the framework and there is an issue while the cache folder does not exist. After googled, there is already a bug opened for this https://bugs.eclipse.org/bugs/show_bug.cgi?id=259981. And seems that this is a long known issue, luckily, it is fixed recently, but it is not included in the equonix version used in Geronimo now. Also, there might be an issue if the cleanOnOpen property is configured without cache folder, I have replied on the issue, and hope that someone could check it. 2011/7/23 Ivan > I just did a simple check, and it seems that the bundles are correctly > removed after the target application is undeployed, at least on the > successful scenarios. The extra 2M size is caused by a .lazy.* file in the > cache folder. and that file should be related to the store manager. Will > check it further later ... > > 2011/7/23 Kevan Miller > >> >> On Jul 22, 2011, at 10:45 PM, Ivan wrote: >> >> > Suppose you mean the OSGi cache directory ? On the server runtime, the >> size of this directory should be almost have the same size with the >> repository folder, as all the files would be copied. >> >> Right. I'm not worried about relatively static content. I am worried about >> consuming more and more disk space and never freeing it... >> >> > For the 12 GB var/cache directory size, there should be a leak issue >> somewhere, >> >> There's definitely a leak. As mentioned, I see two megabytes leaked for >> every deploy/undeploy of a very simple JSP web app. >> >> > a. In the deployment process, the deployer will deploy a temp bundle in >> the cache for builder analysis, maybe it is not uninstalled correctly due to >> some exceptions. >> > b. In the undeployment process, Geronimo did not invoke uninstall for >> the undeployed application due to unknown reason ? >> > c. Some exported classes of the undeployed application are wired with >> other bundles, so the OSGi runtime will keep it there until the framework is >> restarted. Considering the current package generation mechanism, should not >> happen. >> > Think that if we could reproduce the issue, it should be easy to fix. >> Also, I am also thinking that there is no need to package the temp bundle, >> just use the target directory. which mentioned in another thread in the mail >> list. >> >> It's extremely easy to recreate. Choose and application and >> deploy/undeploy it a few times... 'du -h var/cache' or similar to monitor >> disk space between iterations... >> >> --kevan > > > > > -- > Ivan > -- Ivan
[jira] [Commented] (GERONIMO-6076) Graphics cannot be displayed on monitoring porlet
[ https://issues.apache.org/jira/browse/GERONIMO-6076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071497#comment-13071497 ] Shenghao Fang commented on GERONIMO-6076: - The graphics are displayed correctly on Firefox after the change, but layout issues are still existed on Chrome. > Graphics cannot be displayed on monitoring porlet > - > > Key: GERONIMO-6076 > URL: https://issues.apache.org/jira/browse/GERONIMO-6076 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 3.0 >Reporter: Shenghao Fang >Assignee: Shawn Jiang > Attachments: ShowDojoCharting_6076.patch > > > Graphics cannot be displayed on monitoring porlet. > This is a regression by GERONIMO-5674. > Monitoring portlet requires chart related dojo library which was removed by > GERONIMO-5674. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: project branding requirements
Russel, I like your design.
Would you mind attaching the revised logo via a JIRA and I'll try to update
the project website.
Thanks a lot.
Jeff
On Tue, Jul 19, 2011 at 10:49 PM, Russell E Glaue wrote:
> I lost a little bit of the shadow transition to white, but otherwise are
> one of
> these G logos more acceptable? (I can redo the logo to make the shadow
> transition look exactly the same as the current).
>
> The first puts the TM at the inside top right.
> The second puts the TM at the outside bottom right.
>
> I included a small version to see how it scales down. The TM is barely
> legible,
> but otherwise scaled down okay for both.
>
> -RG
>
>
> On 07/19/2011 06:55 AM, Kevan Miller wrote:
> >
> > On Jul 18, 2011, at 11:20 PM, chi runhua wrote:
> >
> >> Kevan, I just did a quick review and please find my comments inline.
> >
> > Thanks!
> >
> >>
> >> Jeff
> >>
> >> On Tue, Jul 19, 2011 at 8:08 AM, Kevan Miller
> wrote:
> >> All,
> >> If anyone's willing to lend a hand on meeting our project branding
> requirements -- help would be much appreciated. It's the PMCs responsibility
> to insure the requirements are met. But anyone (contributor/committer/pmc
> member) can help us meet the requirements. As a reminder --
> http://www.apache.org/foundation/marks/pmcs provides a good overview of
> our requirements.
> >>
> >> I've made a few updates to help us to meet more of the requirements.
> More eyes to review would definitely be appreciated. Updates and
> contributions would be quite welcome... From the checklist:
> >>
> >> 1) Project Website Basics : homepage is project.apache.org (check)
> >>
> >> Reviewed and okay.
> >>
> >> 2) Project Naming And Descriptions : use proper Apache forms, describe
> product, etc. (I made some updates, today. Could use review)
> >>
> >> Reviewed and okay.
> >>
> >> 3) Website Navigation Links : navbar links included, link to
> www.apache.org included (Check. I've made a few updates today for better
> compliance).
> >>
> >> For sub-projects of Geronimo, shall we append Apache Geronimo prefix for
> all of them, If so, the name might be too long... And the link to GBuild is
> broken. Is it about the information of nightly build for both server and
> GEP?
> >
> > GBuild was/is a distributed build infrastructure. We'll need to
> investigate why that link is bad. We need to take similar efforts for our
> subprojects.
> >
> >>
> >> 4) Trademark Attributions : attribution for all ASF marks included in
> footers, etc. (I've updated a template and appears to be working. Could
> stand for some better formatting. We'll also need to review the whole site).
> >>
> >> Still ongoing... Shall we add the generic trademark attribution "All
> other marks mentioned may be trademarks or registered trademarks of their
> respective owners." to avoid any misunderstanding?
> >
> > I think we need to be explicit about our sub-projects. I am pretty sure
> that we need to add the mark information for other pages (some(?) of which
> are missing the footer. There must be multiple templates that need to be
> updated. Formatting suggestions are welcome...
> >
> >>
> >> 5) Logos and Graphics : include TM, use consistent product logo on your
> site (This will take some work)
> >>
> >> Attach the graphics with TM mark for reference. It's kinda difficult to
> edit a .gif file directly. You may notice that TM on topleft_logo is kinda
> ugly Any suggestions are appreciated.
> >
> > Better than I would have done... ;-) But would be nice if we could create
> something with a little nicer. Also, will need to confirm what is required.
> >
> >>
> >> 6) Project Metadata : DOAP file checkedin and up to date (I've made some
> updates and committed --
> https://svn.apache.org/repos/asf/geronimo/site/trunk/doap_Geronimo.rdf).
> >>
> >> I used RDF validator[1] for rdf validation and there are some error
> messages, not sure about the meaning of that, you comments are appreciated.
> >>
> >> [1]. http://www.w3.org/RDF/Validator/
> >>
> >> Error: {E201} Multiple children of property element[Line = 38, Column =
> 16]
> >> Error: {E201} Multiple children of property element[Line = 43, Column =
> 16]
> >> Error: {E201} Multiple children of property element[Line = 48, Column =
> 16]
> >> Error: {E201} Multiple children of property element[Line = 53, Column =
> 16]
> >
> > Cool. I didn't create the bad rdf, but i didn't see the problem, either.
> Should be fixed up, now...
> >
> > --kevan
>
Re: [jira] [Updated] (GERONIMO-5712) Geronimo should remember the monitoring server enablement status.
All right, it's just some of my suggestions[?] On Tue, Jul 26, 2011 at 1:43 PM, Shenghao Fang (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/GERONIMO-5712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] > > Shenghao Fang updated GERONIMO-5712: > > > Attachment: GERONIMO-5712-3.0.patch > > The patch for Geronimo 3.0. > > > Geronimo should remember the monitoring server enablement status. > > -- > > > > Key: GERONIMO-5712 > > URL: https://issues.apache.org/jira/browse/GERONIMO-5712 > > Project: Geronimo > > Issue Type: Bug > > Security Level: public(Regular issues) > >Affects Versions: 2.1.6, 2.2, 3.0 > >Reporter: Shawn Jiang > >Assignee: Shenghao Fang > > Attachments: G5712.patch, GERONIMO-5712-3.0.patch > > > > > > Currently , when a monitor user can use the monitoring function only > after a admin user add/enable the server and enable query on the servers. > > But after the server restart, the enable status become disable > automatically so the the admin user have to do the enablement again so that > Monitor user could continue use the monitoring console. > > To resolve this, we should make the server and query thread enablement > status persistent. so that we could start the query thread once the server > is restarted. > > -- > This message is automatically generated by JIRA. > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > -- Best regards! John Xiao <<330.gif>>
[jira] [Created] (GERONIMO-6097) Use temp directory directly with reference:// to avoid zip the deployed application in the deployment process
Use temp directory directly with reference:// to avoid zip the deployed application in the deployment process - Key: GERONIMO-6097 URL: https://issues.apache.org/jira/browse/GERONIMO-6097 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: deployment Affects Versions: 3.0 Reporter: Ivan Assignee: Ivan Fix For: 3.0 Seem that referece:file could point to a directory (I was thinking that it could only be pointed to a file) , with this function, it seems that we no need to package the temp bundle in the deployment process. Just tried with both felix and equonix, seems that both works fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[BUILD] branches/2.2: Failed for Revision: 1150953
Geronimo Revision: 1150953 built with tests included See the full build-2000.log file at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110726/build-2000.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.2/20110726 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 430 minutes 35 seconds [INFO] Finished at: Tue Jul 26 03:19:10 EDT 2011 [INFO] Final Memory: 315M/753M [INFO] TESTSUITE RESULTS (Failures only) = Assembly: tomcat = See full test results and logs at http://people.apache.org/builds/geronimo/server/binaries/2.2/20110726/logs-2000-tomcat/ Booting Geronimo Kernel (in Java 1.5.0_22)... Module 1/75 org.apache.geronimo.framework/j2ee-system/2.2.2-SNAPSHOT/car started in .001s Module 2/75 org.apache.geronimo.framework/jee-specs/2.2.2-SNAPSHOT/car started in .001s Module 3/75 org.apache.geronimo.plugins.classloaders/xbean-finder/2.2.2-SNAPSHOT/car started in .000s Module 4/75 org.apache.geronimo.framework/xmlbeans/2.2.2-SNAPSHOT/car started in .000s Module 5/75 org.apache.geronimo.framework/rmi-naming/2.2.2-SNAPSHOT/car 2011-07-26 03:24:41,228 WARN [RMIRegistryService] RMI Registry failed 2011-07-26 03:24:41,230 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName="org.apache.geronimo.framework/rmi-naming/2.2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.framework/rmi-naming/2.2.2-SNAPSHOT/car,j2eeType=GBean,name=RMIRegistry" java.rmi.server.ExportException: Port already in use: 1099; nested exception is: java.net.BindException: Address already in use at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:249) at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:184) at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382) at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116) at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:180) at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) at sun.rmi.registry.RegistryImpl.(RegistryImpl.java:68) at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:222) at org.apache.geronimo.kernel.rmi.RMIRegistryService.doStart(RMIRegistryService.java:72) at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:953) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:269) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:103) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:125) at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:539) at org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:377) at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:465) at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:190) at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:546) at sun.reflect.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:592) at org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:816) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) at org.apache.geronimo.kernel.config.EditableConfigurationManager$$EnhancerByCGLIB$$d2f3f41e.startConfiguration() at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:204) at org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:87)
[jira] [Created] (GERONIMO-6096) OpenJPA related error pops up when add two servers which just protocol different in Monitoring porlet on admin console
OpenJPA related error pops up when add two servers which just protocol different in Monitoring porlet on admin console -- Key: GERONIMO-6096 URL: https://issues.apache.org/jira/browse/GERONIMO-6096 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Assignee: Shenghao Fang Priority: Minor 1. Use the July 26's build of geronimo-3.0 snapshot 2. Go to the "Monitoring" porlet on admin console 3. Click the "Add a new server" link under the servers category to add a new server successfully: name:localhost IP/hostname: 127.0.0.1 Protocol:EJB Port:4201 username and password are system and manager 4.Add another server follows step3, but the only difference is : protocol: JMX Port: 1099 5.Click "Add" button ,then error displayed on admin console: An error encountered while adding server. Unable to commit: transaction marked for rollback 6.And warning message displayed on server console: 2011-07-26 16:18:48,031 WARN [Transaction] Unexpected exception from beforeCompletion; transaction will roll back org.apache.openjpa.persistence.EntityExistsException: The transaction has been rolled back. See the nested exceptions for details on the errors that occurred. FailedObject: org.apache.geronimo.monitoring.console.data.Node@125f125f at org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2321) at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2158) at org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2056) at org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:1974) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:520) at org.apache.geronimo.transaction.manager.TransactionImpl.beforeCompletion(TransactionImpl.java:505) at org.apache.geronimo.transaction.manager.TransactionImpl.beforePrepare(TransactionImpl.java:407) at org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:255) at org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:252) at org.apache.geronimo.transaction.GeronimoUserTransaction.commit(GeronimoUserTransaction.java:70) at org.apache.geronimo.monitoring.console.MonitoringPortlet.addServer(MonitoringPortlet.java:707) at org.apache.geronimo.monitoring.console.MonitoringPortlet.processAction(MonitoringPortlet.java:179) at org.apache.pluto.driver.services.container.FilterChainImpl.doFilter(FilterChainImpl.java:117) at org.apache.pluto.driver.services.container.FilterChainImpl.processFilter(FilterChainImpl.java:84) at org.apache.pluto.driver.services.container.FilterManagerImpl.processFilter(FilterManagerImpl.java:112) at org.apache.pluto.container.driver.PortletServlet.dispatch(PortletServlet.java:359) at org.apache.pluto.container.driver.PortletServlet.doPost(PortletServlet.java:267) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:684) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:593) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:530) at org.apache.pluto.driver.container.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:233) at org.apache.pluto.driver.container.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:101) at org.apache.pluto.container.impl.PortletContainerImpl.doAction(PortletContainerImpl.java:251) at org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:135) at org.apache.pluto.driver.PortalDriverServlet.doPost(PortalDriverServlet.java:205) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:668) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.geronimo.console.filter.R
[jira] [Assigned] (GERONIMO-6095) Info displayed incomplete of Default Server in Monitoring on admin console
[ https://issues.apache.org/jira/browse/GERONIMO-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shenghao Fang reassigned GERONIMO-6095: --- Assignee: Shenghao Fang > Info displayed incomplete of Default Server in Monitoring on admin console > -- > > Key: GERONIMO-6095 > URL: https://issues.apache.org/jira/browse/GERONIMO-6095 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 3.0 > Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 > jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) >Reporter: Tina Li >Assignee: Shenghao Fang >Priority: Minor > > 1. Use the July 26's build of geronimo-3.0 snapshot > 2. Go to the "Monitoring" porlet on admin console > 3. Click the 'Enable Query' link associated with this default server, server > works well > 4. Click the 'Edit' link associated with the default server but found no > default protocol was choosed and the values of "Username" and "Password" are > null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (GERONIMO-6095) Info displayed incomplete of Default Server in Monitoring on admin console
Info displayed incomplete of Default Server in Monitoring on admin console -- Key: GERONIMO-6095 URL: https://issues.apache.org/jira/browse/GERONIMO-6095 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 3.0 Environment: JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT enabled, AOT enabled) Reporter: Tina Li Priority: Minor 1. Use the July 26's build of geronimo-3.0 snapshot 2. Go to the "Monitoring" porlet on admin console 3. Click the 'Enable Query' link associated with this default server, server works well 4. Click the 'Edit' link associated with the default server but found no default protocol was choosed and the values of "Username" and "Password" are null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[RESULT] [VOTE] Release javamail 1.8.3 provider and mail components (1st try)
Thanks for voting. The vote passed with 6 +1's. Rex Wang Forrest Xia Kevan Miller Shawn Jiang Ivan Xu Viola Lu there's no +0 or -1 Will the staging artifacts to central soon. regards, -Rex 2011/7/26 viola lu > +1 > > > On Mon, Jul 25, 2011 at 10:46 AM, Ivan wrote: > >> +1 >> >> >> 2011/7/25 Shawn Jiang >> >>> +1 >>> >>> >>> On Thu, Jul 21, 2011 at 12:45 PM, Rex Wang wrote: >>> This is a bug fix release. The sources up for vote are: https://repository.apache.org/content/repositories/orgapachegeronimo-021/org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.3/geronimo-javamail_1.4-1.8.3-source-release.tar.gz https://repository.apache.org/content/repositories/orgapachegeronimo-021/org/apache/geronimo/javamail/geronimo-javamail_1.4/1.8.3/geronimo-javamail_1.4-1.8.3-source-release.zip The staging repository is at: https://repository.apache.org/content/repositories/orgapachegeronimo-021/ The tag has been created at: http://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.8.3/ Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Lei Wang (Rex) rwonly AT apache.org >>> >>> >>> >>> -- >>> Shawn >>> >> >> >> >> -- >> Ivan >> > > > > -- > viola > > Apache Geronimo > > -- Lei Wang (Rex) rwonly AT apache.org
[Result] [VOTE] Release new geronimo-el_2.2_spec 1.0.2, geronimo-jaxws_2.2_spec 1.1, and geronimo-osgi-support 1.1 versions
The vote passed with 6 +1 Shawn Jiang Ivan Xu Kevan Miller Rex Wang Viola Lu Forrest Xia there's no +0/-1.I'll promote the artifacts to central repo soon. On Thu, Jul 21, 2011 at 10:07 AM, Shawn Jiang wrote: > These are bug fix releases to fix problems in the el spec ,jaxws spec, and > osgi-support. > >geronimo-el_2.2_spec-1.0.2 >geronimo-jaxws_2.2_spec-1.1 >geronimo-osgi-support-1.1 > > This is a single vote for 3 spec updates. The components up for vote > are: > > > https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.2/geronimo-el_2.2_spec-1.0.2-source-release.tar.gz > > https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.2/geronimo-el_2.2_spec-1.0.2-source-release.zip > > > https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/1.1/geronimo-jaxws_2.2_spec-1.1-source-release.tar.gz > > https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/1.1/geronimo-jaxws_2.2_spec-1.1-source-release.zip > > > https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-osgi-support/1.1/geronimo-osgi-support-1.1-source-release.tar.gz > > https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-osgi-support/1.1/geronimo-osgi-support-1.1-source-release.zip > > > >The staging repository is: > > > https://repository.apache.org/content/repositories/orgapachegeronimo-006/ > > >The source repos are: > > > https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0.2/ > > https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jaxws_2.2_spec-1.1/ > > https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-osgi-support-1.1/ > > > Vote will be open for 72 hours. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > -- > Shawn > -- Shawn
Re: [VOTE][RESULTS] Release Geronimo Transaction Manager version 2.2.2
Cool! Thanks Jacek. 2011/7/25 Jacek Laskowski > Thanks for voting. The vote passed with 7 +1's. > > Kevan Miller > Ivan Xu > David Blevins > Jean-Louis MONTEIRO > Shawn Jiang > Viola Lu > Jacek Laskowski > > there's no +0 or -1 > > I'm pushing (releasing) the staging artifacts to central (and will the > other steps as described in Geronimo 2.1.7 Release Process [1]). > Thanks for the smooth voting process. > > [1] https://cwiki.apache.org/GMOxPMGT/geronimo-217-release-process.html > > Jacek > > -- > Jacek Laskowski > Java EE, functional languages and IBM WebSphere - http://blog.japila.pl > Warszawa JUG conference = Confitura (formerly Javarsovia) :: > http://confitura.pl >
Re: [VOTE] Release new geronimo-el_2.2_spec 1.0.2, geronimo-jaxws_2.2_spec 1.1, and geronimo-osgi-support 1.1 versions
+1 Forrest On Thu, Jul 21, 2011 at 10:59 AM, Ivan wrote: > +1 > > > 2011/7/21 Shawn Jiang > >> build, unit test, rat:check are all good. >> >> my own +1. >> >> On Thu, Jul 21, 2011 at 10:07 AM, Shawn Jiang wrote: >> >>> These are bug fix releases to fix problems in the el spec ,jaxws spec, >>> and osgi-support. >>> >>>geronimo-el_2.2_spec-1.0.2 >>>geronimo-jaxws_2.2_spec-1.1 >>>geronimo-osgi-support-1.1 >>> >>> This is a single vote for 3 spec updates. The components up for vote >>> are: >>> >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.2/geronimo-el_2.2_spec-1.0.2-source-release.tar.gz >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-el_2.2_spec/1.0.2/geronimo-el_2.2_spec-1.0.2-source-release.zip >>> >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/1.1/geronimo-jaxws_2.2_spec-1.1-source-release.tar.gz >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-jaxws_2.2_spec/1.1/geronimo-jaxws_2.2_spec-1.1-source-release.zip >>> >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-osgi-support/1.1/geronimo-osgi-support-1.1-source-release.tar.gz >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-006/org/apache/geronimo/specs/geronimo-osgi-support/1.1/geronimo-osgi-support-1.1-source-release.zip >>> >>> >>> >>>The staging repository is: >>> >>> >>> https://repository.apache.org/content/repositories/orgapachegeronimo-006/ >>> >>> >>>The source repos are: >>> >>> >>> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-el_2.2_spec-1.0.2/ >>> >>> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jaxws_2.2_spec-1.1/ >>> >>> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-osgi-support-1.1/ >>> >>> >>> Vote will be open for 72 hours. >>> >>> [ ] +1 approve >>> [ ] +0 no opinion >>> [ ] -1 disapprove (and reason why) >>> >>> -- >>> Shawn >>> >> >> >> >> -- >> Shawn >> > > > > -- > Ivan >
