[jira] [Updated] (OFBIZ-6923) Improve the decorator for manufacturing component.
[ https://issues.apache.org/jira/browse/OFBIZ-6923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kongrath Suankaewmanee updated OFBIZ-6923: -- Attachment: manufacturing-decorator.diff > Improve the decorator for manufacturing component. > -- > > Key: OFBIZ-6923 > URL: https://issues.apache.org/jira/browse/OFBIZ-6923 > Project: OFBiz > Issue Type: Improvement > Components: manufacturing >Affects Versions: Trunk >Reporter: Kongrath Suankaewmanee > Attachments: manufacturing-decorator.diff > > > We have a problem on organize the existing decorator. In this case is > manufacturing decorator and also in another decorator too. We cannot use the > existing decorator with *main-decorator* that define on another component in > *hot-deploy*. > So, I thought we should make reorganization for decorator like in the > partymgr component > *applications/party/widget/partymgr/CommonScreens.xml* > All screen should call the common decorator and each common decorator call > *main-decorator* in each commonent, so if we have create the new component in > *hot-deploy* and it should use the *main-decorator* in their. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6923) Improve the decorator for manufacturing component.
Kongrath Suankaewmanee created OFBIZ-6923: - Summary: Improve the decorator for manufacturing component. Key: OFBIZ-6923 URL: https://issues.apache.org/jira/browse/OFBIZ-6923 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Kongrath Suankaewmanee We have a problem on organize the existing decorator. In this case is manufacturing decorator and also in another decorator too. We cannot use the existing decorator with *main-decorator* that define on another component in *hot-deploy*. So, I thought we should make reorganization for decorator like in the partymgr component *applications/party/widget/partymgr/CommonScreens.xml* All screen should call the common decorator and each common decorator call *main-decorator* in each commonent, so if we have create the new component in *hot-deploy* and it should use the *main-decorator* in their. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6916) Upgrade Axis2 to 1.7.1
[ https://issues.apache.org/jira/browse/OFBIZ-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-6916. -- Resolution: Fixed Fix Version/s: Upcoming Branch 13.07.03 14.12.01 > Upgrade Axis2 to 1.7.1 > -- > > Key: OFBIZ-6916 > URL: https://issues.apache.org/jira/browse/OFBIZ-6916 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > Fix For: 14.12.01, 13.07.03, Upcoming Branch > > > With OFBIZ-5801 I recently upgraded Axis2 to 1.6.3. But it still uses > commons-httpclient-3.1 which is not only deprecated but also faces a number > of vulnerabilties: > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5262 > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3577 > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-6153 > This will also help to resolve OFBIZ-6755 (passport component) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6922) Currently the testRemoteSoap test services does not work.
[ https://issues.apache.org/jira/browse/OFBIZ-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183791#comment-15183791 ] Jacques Le Roux commented on OFBIZ-6922: Finally I backported in R15.12 r1733993 R14.12 r1733994 R13.07 r1733995 R12.04 r1733996 I will complete when the demos will be ready > Currently the testRemoteSoap test services does not work. > - > > Key: OFBIZ-6922 > URL: https://issues.apache.org/jira/browse/OFBIZ-6922 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > > *At the moment* the testRemoteSoap which is based on > http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not > work. There are 2 points to consider here. > # Because we share/use the ASF SSL certificate we pass by an ASF proxy to > redirect requests. So we should rather call > http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService > because when when we call this request, the proxy underneath redirects to > http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService > So the current SOAP service location should be changed and the port removed. > # At the moment after recent infra changes none of the calls to > demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or > old.ofbiz.apache.org domains work. > So I will temporarily replace the domain by ofbiz-vm.apache.org but will not > close this issue because I will soon contact the infra team to fix the issue > with the domains. > Note this is the remote test SOAP services, so only the trunk is concerned. > We don't test againt the other domains. Also this test is not part of the > global test suite (all tests). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6916) Upgrade Axis2 to 1.7.1
[ https://issues.apache.org/jira/browse/OFBIZ-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6916: --- Summary: Upgrade Axis2 to 1.7.1 (was: Upgrade Axis2 to 1.7.0) > Upgrade Axis2 to 1.7.1 > -- > > Key: OFBIZ-6916 > URL: https://issues.apache.org/jira/browse/OFBIZ-6916 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > > With OFBIZ-5801 I recently upgraded Axis2 to 1.6.3. But it still uses > commons-httpclient-3.1 which is not only deprecated but also faces a number > of vulnerabilties: > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-5262 > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-3577 > https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-6153 > This will also help to resolve OFBIZ-6755 (passport component) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6916) Upgrade Axis2 to 1.7.0
[ https://issues.apache.org/jira/browse/OFBIZ-6916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183784#comment-15183784 ] Jacques Le Roux commented on OFBIZ-6916: Commited in trunk r1733956 R15.12 r1733957 R14.12 r1733958+r1733959 R13.07 r1733991 Note: there is a newer Axis2 1.7.1 version https://axis.apache.org/axis2/java/core/release-notes/1.7.1.html. OOTB we don't use ADB but better to get the last version anyway. I will change the issue title. Replacing Axis2 1.6.3 by 1.7.1 version is easy as long as you don't try to replace the commons-httpclient-3.1 lib. The only noticeable change is this warning shown in log |http-bio-8443-exec-1 |AxisConfigBuilder |W| Unable to instantiate deployer org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details| It has no effects on the SOAP test services, both works. But the main goal of this issue is a security update because commons-httpclient-3.1 lib is deprecated, no longer maintained and vulnerable and must be replaced. This commit also concerns OFBIZ-6755 but to not mix things OFBIZ-6755 will be completed later. So to not block this issue, the commons-httpclient-3.1 lib is moved from framework/service/lib to specialpurpose/passport/lib/ where it's still required. Normally, as explained at https://axis.apache.org/axis2/java/core/release-notes/1.7.0.html, Axis2 1.7.1 requires "HttpClient 4.2.x and should work with 4.3.x and 4.4.x, but is incompatible with 4.5.x". I did not replace commons-httpclient-3.1 by HttpClient 4.2.1, which is bundled with Axis2 1.7.1, because we have already HttpClient/Core 4.4.1 in base/lib and it works well as is (HttpClient/Core 4.4.1 is in the classpath). To use HttpClient/Core 4.4.1 you need to change the axis2.xml files as specified in the 1.7.0 release note. But where to place this file in OFBiz is not obvious! I decided the best way was to use Axis2 ConfigurationContextFactory.createConfigurationContextFromFileSystem() method to let know Axis2 we want the new httpclient instead of the default one (I really don't understand why the Axis2 team still prefers commons-httpclient-3.1 as default). I had to pass both locations to avoid hardcoding the repository location in the axis2.xml file. I have also decided the best place for the "Axis2 repository" (as they call it) was in framework/service/axis2. So following Axis2 convention http://wso2.com/library/tutorials/axis2-repository/ I put the axis2.xml file in framework/service/axis2/conf. Note: the Axis2 repository could be used to put [Apache Rampart|https://axis.apache.org/axis2/java/rampart/] as a module to secure web services... After this change, there are a number of warnings thrown by Axis2 but they are actually interesting as they provide guidance for future use of modules and such (notably Apache Rampart) |ttp-bio-8443-exec-10 |Utils |W| [JAXWS] - unable to load org.apache.axis2.jaxws.dispatchers.GenericProviderDispatcher |ttp-bio-8443-exec-10 |Utils |W| [JAXWS] - unable to load org.apache.axis2.jaxws.dispatchers.MustUnderstandValidationDispatcher |ttp-bio-8443-exec-10 |Utils |W| [JAXWS] - unable to load org.apache.axis2.jaxws.dispatchers.MustUnderstandChecker |ttp-bio-8443-exec-10 |Utils |W| [JAXWS] - unable to load org.apache.axis2.jaxws.dispatchers.GenericProviderDispatcher |ttp-bio-8443-exec-10 |Utils |W| [JAXWS] - unable to load org.apache.axis2.jaxws.dispatchers.MustUnderstandValidationDispatcher |ttp-bio-8443-exec-10 |AxisConfigBuilder |W| Unable to instantiate deployer org.apache.axis2.deployment.ServiceDeployer; see debug logs for more details |ttp-bio-8443-exec-10 |AxisConfigBuilder |W| Unable to instantiate deployer org.apache.axis2.jaxws.framework.JAXWSDeployer; see debug logs for more details While at it I replaced StAXOMBuilder (deprecated) by OMXMLBuilderFactory I will backport the changes in the supporterd releases branches but R12.04. Others all use HttpClient/Core version older than 4.2.1. I'm aware I will have to handle several conflicts by hand, some are easy others "harder". We have the passport component only in R15.12, it will be easy to neglect in older releases. I expect more work with the LICENSE file and even more with the .classpath file. Since R15.12 we use tabs in it (Adrian rightly told us to use Eclipse internal tools to edit this file, though I noted it does not respect the alphabetical order) but older releases still use spaces (and this is often a pain now, but a bright future ahead ;)) Crossing fingers with this commit, I have other changes pending in this instance (notably for OFBIZ-6849) and it got quite complicated. > Upgrade Axis2 to 1.7.0 > -- > >
[jira] [Assigned] (OFBIZ-6888) GroovyEngine.serviceInvoker masks Groovy script exceptions in some cases
[ https://issues.apache.org/jira/browse/OFBIZ-6888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-6888: -- Assignee: Jacques Le Roux > GroovyEngine.serviceInvoker masks Groovy script exceptions in some cases > > > Key: OFBIZ-6888 > URL: https://issues.apache.org/jira/browse/OFBIZ-6888 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Forrest Rae >Assignee: Jacques Le Roux > Labels: errorhandling > Attachments: OFBIZ-6888.patch > > > If GroovyEngine.serviceInvoker catches an exception in a Groovy script, it > would mask the exception in some cases. An exception's detailMessage can be > null. If it is null, the exception won't be properly returned and logged, > and that will make spotting problems very difficult. This was the case for > me while trying to track down a problem with a > java.util.ConcurrentModificationException error in a Groovy script. I > suspect that this choice to mask exceptions and only return the message has > cause bugs to not be spotted. > Disabling this for now in favor of returning a proper exception. > GroovyEngine.serviceInvoker() should throw GenericServiceException if error, > rather than returning ServiceUtil.returnError(e.getMessage()) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-6218: -- Assignee: Jacques Le Roux > Unit tests throw exception in DBCP > -- > > Key: OFBIZ-6218 > URL: https://issues.apache.org/jira/browse/OFBIZ-6218 > Project: OFBiz > Issue Type: Bug >Reporter: Adrian Crum >Assignee: Jacques Le Roux > Attachments: OFBIZ-6218.patch > > > Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183763#comment-15183763 ] Jacques Le Roux commented on OFBIZ-6218: Thanks Forrest, I'll have a look... soon... > Unit tests throw exception in DBCP > -- > > Key: OFBIZ-6218 > URL: https://issues.apache.org/jira/browse/OFBIZ-6218 > Project: OFBiz > Issue Type: Bug >Reporter: Adrian Crum > Attachments: OFBIZ-6218.patch > > > Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6922) Currently the testRemoteSoap test services does not work.
[ https://issues.apache.org/jira/browse/OFBIZ-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183385#comment-15183385 ] Jacques Le Roux commented on OFBIZ-6922: At revision: 1733951 I temporarily replaced the demo-trunk.ofbiz.apache.org domain by ofbiz-vm.apache.org:8080 > Currently the testRemoteSoap test services does not work. > - > > Key: OFBIZ-6922 > URL: https://issues.apache.org/jira/browse/OFBIZ-6922 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > > *At the moment* the testRemoteSoap which is based on > http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not > work. There are 2 points to consider here. > # Because we share/use the ASF SSL certificate we pass by an ASF proxy to > redirect requests. So we should rather call > http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService > because when when we call this request, the proxy underneath redirects to > http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService > So the current SOAP service location should be changed and the port removed. > # At the moment after recent infra changes none of the calls to > demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or > old.ofbiz.apache.org domains work. > So I will temporarily replace the domain by ofbiz-vm.apache.org but will not > close this issue because I will soon contact the infra team to fix the issue > with the domains. > Note this is the remote test SOAP services, so only the trunk is concerned. > We don't test againt the other domains. Also this test is not part of the > global test suite (all tests). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6922) Currently the testRemoteSoap test services does not work.
[ https://issues.apache.org/jira/browse/OFBIZ-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6922: --- Description: *At the moment* the testRemoteSoap which is based on http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not work. There are 2 points to consider here. # Because we share/use the ASF SSL certificate we pass by an ASF proxy to redirect requests. So we should rather call http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService because when when we call this request, the proxy underneath redirects to http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService So the current SOAP service location should be changed and the port removed. # At the moment after recent infra changes none of the calls to demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or old.ofbiz.apache.org domains work. So I will temporarily replace the domain by ofbiz-vm.apache.org but will not close this issue because I will soon contact the infra team to fix the issue with the domains. Note this is the remote test SOAP services, so only the trunk is concerned. We don't test againt the other domains. Also this test is not part of the global test suite (all tests). was: *At the moment* the testRemoteSoap which is based on http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not work. There are 2 points to consider here. # Because we share/use the ASF SSL certificate we pass by an ASF proxy to redirect requests. So we should rather call http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService because when when we call this request, the proxy underneath redirects to https://ofbiz-vm.apache.org:8080/webtools/control/SOAPService So the current SOAP service location should be changed and the port removed. # At the moment after recent infra changes none of the calls to demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or old.ofbiz.apache.org domains work. So I will temporarily replace the location by https://ofbiz-vm.apache.org:8080/webtools/control/SOAPService but will not close this issue because I will soon contact the infra team to fix the issue with the domains Note this is test SOAP services, so only the trunk is concerned. We don't test againt the other domains... *Note for myself (to remove), check if we can use this test on the demo* > Currently the testRemoteSoap test services does not work. > - > > Key: OFBIZ-6922 > URL: https://issues.apache.org/jira/browse/OFBIZ-6922 > Project: OFBiz > Issue Type: Bug > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux > > *At the moment* the testRemoteSoap which is based on > http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not > work. There are 2 points to consider here. > # Because we share/use the ASF SSL certificate we pass by an ASF proxy to > redirect requests. So we should rather call > http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService > because when when we call this request, the proxy underneath redirects to > http://ofbiz-vm.apache.org:8080/webtools/control/SOAPService > So the current SOAP service location should be changed and the port removed. > # At the moment after recent infra changes none of the calls to > demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or > old.ofbiz.apache.org domains work. > So I will temporarily replace the domain by ofbiz-vm.apache.org but will not > close this issue because I will soon contact the infra team to fix the issue > with the domains. > Note this is the remote test SOAP services, so only the trunk is concerned. > We don't test againt the other domains. Also this test is not part of the > global test suite (all tests). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6921) Four of the remote SOAP test services don't work
[ https://issues.apache.org/jira/browse/OFBIZ-6921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-6921: --- Assignee: Jacques Le Roux Priority: Minor (was: Major) Issue Type: Improvement (was: Bug) > Four of the remote SOAP test services don't work > > > Key: OFBIZ-6921 > URL: https://issues.apache.org/jira/browse/OFBIZ-6921 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Trunk >Reporter: Jacques Le Roux >Assignee: Jacques Le Roux >Priority: Minor > > For 5 years now the testRemoteSoap1 to testRemoteSoap4 test services don't > work. I added then when replacing testRemoteSoap at r1072378 but forgot then > to open a Jira issue, here it is! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6922) Currently the testRemoteSoap test services does not work.
Jacques Le Roux created OFBIZ-6922: -- Summary: Currently the testRemoteSoap test services does not work. Key: OFBIZ-6922 URL: https://issues.apache.org/jira/browse/OFBIZ-6922 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux Assignee: Jacques Le Roux *At the moment* the testRemoteSoap which is based on http://demo-trunk.ofbiz.apache.org:8080/webtools/control/SOAPService does not work. There are 2 points to consider here. # Because we share/use the ASF SSL certificate we pass by an ASF proxy to redirect requests. So we should rather call http://demo-trunk-ofbiz.apache.org/webtools/control/SOAPService because when when we call this request, the proxy underneath redirects to https://ofbiz-vm.apache.org:8080/webtools/control/SOAPService So the current SOAP service location should be changed and the port removed. # At the moment after recent infra changes none of the calls to demo-trunk.ofbiz.apache.org, demo-stable.ofbiz.apache.org or old.ofbiz.apache.org domains work. So I will temporarily replace the location by https://ofbiz-vm.apache.org:8080/webtools/control/SOAPService but will not close this issue because I will soon contact the infra team to fix the issue with the domains Note this is test SOAP services, so only the trunk is concerned. We don't test againt the other domains... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6921) Four of the remote SOAP test services don't work
Jacques Le Roux created OFBIZ-6921: -- Summary: Four of the remote SOAP test services don't work Key: OFBIZ-6921 URL: https://issues.apache.org/jira/browse/OFBIZ-6921 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Trunk Reporter: Jacques Le Roux For 5 years now the testRemoteSoap1 to testRemoteSoap4 test services don't work. I added then when replacing testRemoteSoap at r1072378 but forgot then to open a Jira issue, here it is! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6218) Unit tests throw exception in DBCP
[ https://issues.apache.org/jira/browse/OFBIZ-6218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183234#comment-15183234 ] Forrest Rae commented on OFBIZ-6218: It's very likely that these strange errors are related to groovy scripts throwing exceptions that don't have error messages. One strong possibility is java.util.ConcurrentModificationException. I ran into this issue and ended up tracking it down to the lack of exception reporting in the GroovyScriptEngine: OFBIZ-6888. > Unit tests throw exception in DBCP > -- > > Key: OFBIZ-6218 > URL: https://issues.apache.org/jira/browse/OFBIZ-6218 > Project: OFBiz > Issue Type: Bug >Reporter: Adrian Crum > Attachments: OFBIZ-6218.patch > > > Details in comments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Skype Group Call Next Week re-Framework Re-Factoring
Hi Ron You're good (I'm not sure I could manage a 7am call!). I think we can do better for you. Based on the feedback at the moment we have to cover 4 timezones so 8am, 9am and even 10am your time look like they could work too. Thanks Sharan Le 07/03/2016 14:33, Ron Wheeler a écrit : 7:00 AM is not a problem if that is the best time available. Ron On 07/03/2016 2:27 AM, Sharan-F wrote: Hi Taher I didnt realise Ron was interested. If that's the case then that makes it difficult for us to have our call today as it will only be 7am his time. I think then it's better to postpone the call until next week to make sure that we have the availability of everyone who is interested in a call. We do have a Community Day coming up on the 19th March so as long as we can have our call beforehand to co-ordinate the work then we should be able to get things moving in time for that. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/Skype-Group-Call-Next-Week-re-Framework-Re-Factoring-tp4677595p4677610.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: Skype Group Call Next Week re-Framework Re-Factoring
7:00 AM is not a problem if that is the best time available. Ron On 07/03/2016 2:27 AM, Sharan-F wrote: Hi Taher I didnt realise Ron was interested. If that's the case then that makes it difficult for us to have our call today as it will only be 7am his time. I think then it's better to postpone the call until next week to make sure that we have the availability of everyone who is interested in a call. We do have a Community Day coming up on the 19th March so as long as we can have our call beforehand to co-ordinate the work then we should be able to get things moving in time for that. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/Skype-Group-Call-Next-Week-re-Framework-Re-Factoring-tp4677595p4677610.html Sent from the OFBiz - Dev mailing list archive at Nabble.com. -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102
Re: Skype Group Call Next Week re-Framework Re-Factoring
Hi All Ok - I'll definitely move it to sometime next week. I'll also start setting up the skype group. Anyone that would like to be included, please send me your skype name via email to sha...@apache.org (Taher, Julien I already have yours so will add you both in). Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/Skype-Group-Call-Next-Week-re-Framework-Re-Factoring-tp4677595p4677612.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
