Re: [VOTE] [RELEASE] Apache OFBiz 17.12.05 - Second attempt
+1 - Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Jan 4, 2021 at 4:02 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > This is the vote thread (second attempt) to release a new bug fix release > for the release17.12 branch. This new release, "Apache OFBiz 17.12.05" will > supersede all the previous releases from the same branch. > > Please consider that this may be the last release in the 17.12 series and > in the future releases will be published from the newer series, which is > 18.12. > > The release files can be downloaded from here: > > https://dist.apache.org/repos/dist/dev/ofbiz/ > > and are: > > * apache-ofbiz-17.12.05.zip > * KEYS: text file with keys > * apache-ofbiz-17.12.05.zip.asc: the detached signature file > * apache-ofbiz-17.12.05.zip.sha512: checksum file > > Please download and test the zip file and its signatures (for instructions > on testing the signatures see http://www.apache.org/info/verification.html > ). > > Please cast your vote: > > [ +1] release Apache OFBiz 17.12.05 > [ -1] do not release > > This vote will be open for 5 days. >
Re: Welcome Mridul Pathak as new PMC member!!
Many many congratulations Mridul! - Best regards, Swapnil M Mane, ofbiz.apache.org On Fri, Sep 18, 2020 at 12:55 PM Ashish Vijaywargiya wrote: > The OFBiz PMC has invited Mridul Pathak to become a member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Mridul! >
Re: Welcome Swapnil Shah as new PMC member!!
Many many congratulations Swapnil! - Best regards, Swapnil M Mane, ofbiz.apache.org On Fri, Sep 18, 2020 at 12:56 PM Ashish Vijaywargiya wrote: > The OFBiz PMC has invited Swapnil Shah to become a member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Swapnil! >
Re: Welcome to Devanshu Vyas as new committer!
Many congratulations Devanshu! Best regards, Swapnil M Mane On Wed, Aug 19, 2020 at 2:32 PM Pawan Verma wrote: > The OFBiz PMC has invited Devanshu Vyas to become a new committer and we > are happy to announce that he has accepted this role. > > Some of the reasons for inviting Devanshu Vyas include: > > - He is invested in the OFBiz project and has been a member for many years > - He is taking an initiative towards improving the system > - He has functional experience in various areas of the framework > - He enjoys working with the community and collaborating with others > > Please join me in welcoming and congratulating Devanshu! > > Cheers > Pawan Verma > ofbiz.apache.org >
Re: Welcome Pawan Verma as new PMC member
Many congratulations Pawan, welcome aboard! - Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Jul 28, 2020 at 1:22 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Pawan Verma to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Pawan! > >
Re: Welcome Arun Patidar as new PMC member
Many congratulations Arun, welcome aboard! - Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Jul 6, 2020 at 12:30 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Arun Patidar to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Arun! > >
Re: Welcome Aditya Sharma as new PMC member
Many congratulations Aditya, welcome aboard! - Best regards, Swapnil M Mane, ofbiz.apache.org On Sun, Jul 5, 2020 at 10:24 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Aditya Sharma to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Aditya! > >
Re: Welcome Suraj Khurana as new PMC member
Many congratulations Suraj, welcome aboard! - Best regards, Swapnil M Mane, ofbiz.apache.org On Sat, Jul 4, 2020 at 5:22 PM Jacques Le Roux wrote: > The OFBiz PMC has invited Suraj Khurana to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board Suraj! > >
Re: Add CHANGELOG.md file
+1 - Best regards, Swapnil M Mane, ofbiz.apache.org On Wed, Jun 17, 2020 at 11:23 AM Deepak Dixit wrote: > Hi Dev, > > As we have already moved to git for the version control system, I propose > to add a changelog file to maintain the changelogs[1]. > What is a changelog? > > A changelog is a file which contains a curated, chronologically ordered > list of notable changes for each version of a project. > Why keep a changelog? > > To make it easier for users and contributors to see precisely what notable > changes have been made between each release (or version) of the project. > Who needs a changelog? > > People do. Whether consumers or developers, the end users of software are > human beings who care about what's in the software. When the software > changes, people want to know why and how. > > We can have our own process to generate changelog, It may be either manual > entries, or some tool or using git log. We can discuss this independently. > > https://keepachangelog.com/en/1.0.0/ > > Thanks & Regards > -- > Deepak Dixit > ofbiz.apache.org >
Re: Welcome Swapnil M Mane as new PMC member
Dear all, Thank you so much for your kind wishes! It's a privilege and honor to be part of the vibrant OFBiz community. Looking forward to having more amazing experience with you all, thanks again. Thank you Jacques for your mail. - Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Apr 28, 2020 at 8:46 PM Deepak Nigam wrote: > Congratulations, Swapnil. > > Regards > -- > Deepak Nigam > > On Mon, Apr 27, 2020, 11:02 AM Aditya Sharma > wrote: > > > Congratulations Swapnil! > > > > Thanks and Regards, > > Aditya Sharma > > > > On Sat, Apr 25, 2020 at 9:58 PM Mohammad Kathawala < > > mohammad.kathaw...@hotwaxsystems.com> wrote: > > > > > Many Congratulations Swapnil! > > > Kind Regards, > > > Mohammad Kathawala > > > Senior Technical Consultant > > > *HotWax Systems* > > > *Enterprise open source experts* > > > cell: +91-7772858789 > > > office: 0731-409-3684 > > > http://www.hotwaxsystems.com > > > > > > > > > On Sat, Apr 25, 2020 at 7:19 PM Pranay Pandey < > > > pranay.pan...@hotwaxsystems.com> wrote: > > > > > > > Swapnil M, > > > > > > > > Congratulations and welcome. > > > > Looking forward to a wonderful journey together. > > > > > > > > Best regards, > > > > Pranay Pandey > > > > > > > > > > > > On Thu, Apr 23, 2020 at 5:02 PM Jacques Le Roux < > > > > jacques.le.r...@les7arts.com> wrote: > > > > > > > > > The OFBiz PMC has invited Swapnil M Mane to become member of the > > > > committee > > > > > and we are glad to announce that he has accepted the nomination. > > > > > > > > > > On behalf of the OFBiz PMC, welcome on board! > > > > > > > > > > > > > > > > > > > >
Re: Welcome Rishi Solanki as new PMC member
Many congratulations Rishi, welcome on board! - Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Apr 28, 2020 at 7:53 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > The OFBiz PMC has invited Rishi Solanki to become member of the committee > and we are glad to announce that he has accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board! >
Re: Welcome James Young as new PMC member
Congratulations James! - Best regards, Swapnil M Mane, ofbiz.apache.org On Wed, Apr 22, 2020 at 3:58 PM James Yong wrote: > Hi all, > > Thank you for your words of congratulations. > Hope everyone is well and safe. > Also thanks PMC for the kind invitation. > Looking forward to deeper collaboration. > > Regards, > James > > On 2020/04/22 10:16:36, Deepak Nigam wrote: > > Congratulations James!!! > > > > Regards > > -- > > Deepak Nigam > > > > > > > > On Wed, Apr 22, 2020, 3:25 PM Pawan Verma wrote: > > > > > Congratulations James! > > > -- > > > Thanks & Regards > > > Pawan Verma > > > ofbiz.apache.org > > > > > > > > > On Wed, Apr 22, 2020 at 3:16 PM Suraj Khurana > > > > wrote: > > > > > > > Congratulations James !! > > > > > > > > -- > > > > Best Regards, > > > > Suraj Khurana > > > > Senior Technical Consultant > > > > > > > > > > > > On Wed, Apr 22, 2020 at 3:15 PM Ashish Vijaywargiya < > > > > ashish.vijaywarg...@hotwaxsystems.com> wrote: > > > > > > > > > Congrats James! > > > > > > > > > > -- > > > > > Kind Regards, > > > > > Ashish Vijaywargiya > > > > > Vice President of Operations > > > > > *HotWax Systems* > > > > > *Enterprise open source experts* > > > > > cell: +91-9893479711 > > > > > http://www.hotwaxsystems.com > > > > > > > > > > > > > > > > > > > > On Wed, Apr 22, 2020 at 2:08 PM Jacques Le Roux < > > > > > jacques.le.r...@les7arts.com> wrote: > > > > > > > > > > > The OFBiz PMC has invited James Young to become member of the > > > committee > > > > > > and we are glad to announce that he has accepted the nomination. > > > > > > > > > > > > On behalf of the OFBiz PMC, welcome on board! > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: Welcome to Girish Vasmatkar as new committer!
Congratulations Girish! - Best regards, Swapnil M Mane, ofbiz.apache.org On Wed, Apr 22, 2020 at 5:55 PM Girish Vasmatkar < girish.vasmat...@hotwaxsystems.com> wrote: > Hi All > > Thanks for your continuous support in this journey. I am honoured and > privileged to be part of this community. Sure, the committership comes with > great responsibilities and I hope to back it up with even more commitment > from my side. > > Thanks once again! > > Best, > Girish > > > On Wed, Apr 22, 2020 at 5:36 PM Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > Sorry I missed Girish 1st name in subject :/ > > > > Le 22/04/2020 à 11:37, Jacques Le Roux a écrit : > > > The OFBiz PMC has invited Girish to become a new committer and we are > > pleased to announce that he has accepted. > > > > > > Girish is part of the community for near 2 years and has proposed > > several smart propositions notably related to security and GraphQL, but > not > > only. > > > > > > Please join me in welcoming and congratulating Girish. > > > > > > Jacques > > > > > > > > >
Re: [VOTE] [RELEASE] Apache OFBiz 17.12.03
+1 - Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Apr 20, 2020 at 2:34 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > This is the vote thread to release a new bug fix release for the > release17.12 branch. This new release, "Apache OFBiz 17.12.03" will > supersede the previous release from the same branch. > > The release files can be downloaded from here: > https://dist.apache.org/repos/dist/dev/ofbiz/ > and are: > * apache-ofbiz-17.12.03.zip > * KEYS: text file with keys > * apache-ofbiz-17.12.03.zip.asc: the detached signature file > * apache-ofbiz-17.12.03.zip.sha512: checksum file > > Please download and test the zip file and its signatures (for instructions > on testing the signatures see http://www.apache.org/info/verification.html > ). > > Vote: > [ +1] release as Apache OFBiz 17.12.03 > [ -1] do not release > > This vote will be open for 5 days. > > For more details about this process please refer to > http://www.apache.org/foundation/voting.html > > Best Regards, > > Jacopo >
Re: [GitHub] [ofbiz-tools] swapnilmmane merged pull request #3: Documented: Updated instance details in README file
Thank you Jacques for notifying, will re-request Infra team for the same. :) - Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Apr 14, 2020 at 5:59 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Hi Swapnil, > > It seems Infra missed tools in INFRA-20007? > > Thanks > > Jacques > > Le 14/04/2020 à 14:21, GitBox a écrit : > > swapnilmmane merged pull request #3: Documented: Updated instance > details in README file > > URL: https://github.com/apache/ofbiz-tools/pull/3 > > > > > > > > > > > > This is an automated message from the Apache Git Service. > > To respond to the message, please log on to GitHub and use the > > URL above to go to the specific comment. > > > > For queries about this service, please contact Infrastructure at: > > us...@infra.apache.org > > > > > > With regards, > > Apache Git Services > >
Re: [VOTE] [RELEASE] Apache OFBiz 17.12.02
+1 - Best regards, Swapnil M Mane, ofbiz.apache.org On Fri, Apr 10, 2020 at 3:36 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > This is the vote thread to release a new bug fix release for the > release17.12 branch. This new release, "Apache OFBiz 17.12.02" will > supersede the previous release from the same branch. > > The release files can be downloaded from here: > https://dist.apache.org/repos/dist/dev/ofbiz/ > and are: > * apache-ofbiz-17.12.02.zip > * KEYS: text file with keys > * apache-ofbiz-17.12.02.zip.asc: the detached signature file > * apache-ofbiz-17.12.02.zip.sha512: checksum file > > Please download and test the zip file and its signatures (for instructions > on testing the signatures see http://www.apache.org/info/verification.html > ). > > Vote: > [ +1] release as Apache OFBiz 17.12.02 > [ -1] do not release > > This vote will be open for 5 days. > > For more details about this process please refer to > http://www.apache.org/foundation/voting.html > > Best Regards, > > Jacopo >
Re: Demo instance for OFBiz 17.12 release and remove 13.07 demo
Hello team, I am planning to upgrade the demo instances next week. If you have any feedback or thoughts, please feel free to comment at https://issues.apache.org/jira/browse/OFBIZ-11472 - Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Mar 23, 2020 at 3:48 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Thank you very much Swapnil! > > Jacques > > Le 23/03/2020 à 03:56, Swapnil M Mane a écrit : > > Hello team, > > The progress of upgrading demo instances can be tracked at > > https://issues.apache.org/jira/browse/OFBIZ-11472 > > > > The Pull Request and notes on steps to be executed on OFBiz VM > > for setting demo instance are mentioned in Jira comment at > > https://s.apache.org/o95vx > > > > Please have a look and let me know your kind feedback. > > Thank you so much Jacques Le Roux for your inputs and guidance in this. > > > > - Best regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > On Sun, Mar 15, 2020 at 9:29 PM Swapnil M Mane > wrote: > >> Thank you everyone for your response. > >> > >> Hi Jacques, > >> I will take care of this and will sync with you and the team in case > any help needed. > >> > >> Best regards, > >> Swapnil M Mane, > >> ofbiz.apache.org > >> > >> > >> > >> On Sat, Mar 14, 2020 at 4:32 PM Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > >>> Hi, > >>> > >>> Someone will handle it? > >>> > >>> Jacques > >>> > >>> Le 06/03/2020 à 10:34, Swapnil M Mane a écrit : > >>>> Hello team, > >>>> Current we have three demo instances [1] for OFBiz. > >>>> > >>>> -- Current Stable Release 16.11 - Demo > >>>> https://demo-stable.ofbiz.apache.org/ordermgr/control/main > >>>> > >>>> -- Developer Trunk - Demo > >>>> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main > >>>> > >>>> -- Previous Stable Release 13.07 - Demo > >>>> https://demo-old.ofbiz.apache.org/ordermgr/control/main > >>>> > >>>> As we have our new OFBiz release 17.12, should we think of taking the > >>>> following actions: > >>>> > >>>> 1. The 'Current Stable Release' instance should have release 17.12 > >>>> i.e. demo-stable.ofbiz.apache.org should deploy on release 17.12 > >>>> > >>>> 2. The 'Previous Stable Release' instance should have release 16.11 > >>>> i.e. demo-old.ofbiz.apache.org should deploy on 16.11 > >>>> > >>>> After this migration, we will *no longer have 13.07 - Demo* instance. > >>>> > >>>> Here are some more details about the 13.07 demo instance. > >>>> The 13.07 instance gets down abruptly very frequently. > >>>> After this, it requires manual interaction to restart, in recent times > >>>> Jacques and I manually restarted it many times. > >>>> Looking at the current scenarios, it seems our users are also not > >>>> using 13.07 demo instance on a frequent basis, because no one from our > >>>> users reports us when it is down ;-) > >>>> > >>>> [1] https://ofbiz.apache.org/ofbiz-demos.html > >>>> > >>>> Best regards, > >>>> Swapnil M Mane, > >>>> ofbiz.apache.org > >
Re: [GitHub] [ofbiz-site] PierreSmits commented on issue #1: Improved: widget-theme.xsd typos (OFBIZ-11421)
Hello team, This is done, thanks to our Infra team! For the following repositories, GitHub PR notifications will be sent to notificati...@ofbiz.apache.org https://github.com/apache/ofbiz https://github.com/apache/ofbiz-framework https://github.com/apache/ofbiz-plugins https://github.com/apache/ofbiz-tools https://github.com/apache/ofbiz-site - Best regards, Swapnil M Mane, ofbiz.apache.org On Sun, Mar 22, 2020 at 2:51 PM Swapnil M Mane wrote: > > Hello team, > I mistakenly created the ticket in OFBiz Jira space, > I thought I was selecting the 'Project' field as OFBiz on Infra Jira ticket. > Apologies for this, closed the ticket. > Here is a reference to Infra ticket: > > https://issues.apache.org/jira/browse/INFRA-20007 > > > - Best regards, > Swapnil M Mane, > ofbiz.apache.org > > On Sun, Mar 22, 2020 at 2:21 PM Swapnil M Mane > wrote: > > > > Hi team, > > Here is the Infra Jira ticket to track the progress on this. > > https://issues.apache.org/jira/browse/OFBIZ-11471 > > > > - Best regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > On Tue, Mar 17, 2020 at 10:18 AM Swapnil M Mane > > wrote: > > > > > > Hello team, > > > > > > For the following repositories, the Git PR notifications are sent to the > > > dev@ofbiz.apache.org list. > > > > > > https://github.com/apache/ofbiz > > > https://github.com/apache/ofbiz-framework > > > https://github.com/apache/ofbiz-plugins > > > https://github.com/apache/ofbiz-tools > > > > > > Similar to the ofbiz-site repository, > > > I will request the Infra team to move these notifications to > > > notificati...@ofbiz.apache.org list. > > > > > > Best regards, > > > Swapnil M Mane, > > > ofbiz.apache.org > > > > > > > > > > > > On Mon, Mar 9, 2020 at 5:50 PM Swapnil M Mane > > > wrote: > > >> > > >> Hello team, > > >> Here is the Jira ticket to track the progress for this activity > > >> https://issues.apache.org/jira/browse/INFRA-19945 > > >> > > >> Best regards, > > >> Swapnil M Mane, > > >> ofbiz.apache.org > > >> > > >> > > >> > > >> On Sat, Feb 29, 2020 at 10:24 AM Swapnil M Mane > > >> wrote: > > >>> > > >>> Thank you team for inputs, will sync up with the Infra team to proceed > > >>> with this. > > >>> > > >>> Best regards, > > >>> Swapnil M Mane, > > >>> ofbiz.apache.org > > >>> > > >>> > > >>> > > >>> On Thu, Feb 27, 2020 at 3:14 PM Pierre Smits > > >>> wrote: > > >>>> > > >>>> Good advice, Michael. But that don't always happen. > > >>>> > > >>>> Met vriendelijke groet, > > >>>> > > >>>> Pierre Smits > > >>>> *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> > > >>>> since > > >>>> 2008 (without privileges) > > >>>> > > >>>> *Apache Trafodion <https://trafodion.apache.org>, Vice President* > > >>>> *Apache Directory <https://directory.apache.org>, PMC Member* > > >>>> Apache Incubator <https://incubator.apache.org>, committer > > >>>> Apache Steve <https://steve.apache.org>, committer > > >>>> > > >>>> > > >>>> On Thu, Feb 27, 2020 at 10:35 AM Michael Brohl > > >>>> > > >>>> wrote: > > >>>> > > >>>> > Every Git PR also needs a Jira, for which the notifications go to the > > >>>> > notifications mailing list. > > >>>> > > > >>>> > If people want to contribute and follow, they should subscribe to > > >>>> > notifications. > > >>>> > > > >>>> > Maybe we should send a reminder and encourage them to do so instead > > >>>> > of > > >>>> > mixing notifications and dev again. > > >>>> > > > >>>> > Michael Brohl > > >>>> > > > >>>> > ecomify GmbH - www.ecomify.de > > >>>> > > > >>>> > > > >>>> > Am 27.02.20 um 09:54 schrieb Pierre Smits: > >
Re: Demo instance for OFBiz 17.12 release and remove 13.07 demo
Hello team, The progress of upgrading demo instances can be tracked at https://issues.apache.org/jira/browse/OFBIZ-11472 The Pull Request and notes on steps to be executed on OFBiz VM for setting demo instance are mentioned in Jira comment at https://s.apache.org/o95vx Please have a look and let me know your kind feedback. Thank you so much Jacques Le Roux for your inputs and guidance in this. - Best regards, Swapnil M Mane, ofbiz.apache.org On Sun, Mar 15, 2020 at 9:29 PM Swapnil M Mane wrote: > > Thank you everyone for your response. > > Hi Jacques, > I will take care of this and will sync with you and the team in case any help > needed. > > Best regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Sat, Mar 14, 2020 at 4:32 PM Jacques Le Roux > wrote: >> >> Hi, >> >> Someone will handle it? >> >> Jacques >> >> Le 06/03/2020 à 10:34, Swapnil M Mane a écrit : >> > Hello team, >> > Current we have three demo instances [1] for OFBiz. >> > >> > -- Current Stable Release 16.11 - Demo >> > https://demo-stable.ofbiz.apache.org/ordermgr/control/main >> > >> > -- Developer Trunk - Demo >> > https://demo-trunk.ofbiz.apache.org/ordermgr/control/main >> > >> > -- Previous Stable Release 13.07 - Demo >> > https://demo-old.ofbiz.apache.org/ordermgr/control/main >> > >> > As we have our new OFBiz release 17.12, should we think of taking the >> > following actions: >> > >> > 1. The 'Current Stable Release' instance should have release 17.12 >> > i.e. demo-stable.ofbiz.apache.org should deploy on release 17.12 >> > >> > 2. The 'Previous Stable Release' instance should have release 16.11 >> > i.e. demo-old.ofbiz.apache.org should deploy on 16.11 >> > >> > After this migration, we will *no longer have 13.07 - Demo* instance. >> > >> > Here are some more details about the 13.07 demo instance. >> > The 13.07 instance gets down abruptly very frequently. >> > After this, it requires manual interaction to restart, in recent times >> > Jacques and I manually restarted it many times. >> > Looking at the current scenarios, it seems our users are also not >> > using 13.07 demo instance on a frequent basis, because no one from our >> > users reports us when it is down ;-) >> > >> > [1] https://ofbiz.apache.org/ofbiz-demos.html >> > >> > Best regards, >> > Swapnil M Mane, >> > ofbiz.apache.org >>
Re: [GitHub] [ofbiz-site] PierreSmits commented on issue #1: Improved: widget-theme.xsd typos (OFBIZ-11421)
Hello team, I mistakenly created the ticket in OFBiz Jira space, I thought I was selecting the 'Project' field as OFBiz on Infra Jira ticket. Apologies for this, closed the ticket. Here is a reference to Infra ticket: https://issues.apache.org/jira/browse/INFRA-20007 - Best regards, Swapnil M Mane, ofbiz.apache.org On Sun, Mar 22, 2020 at 2:21 PM Swapnil M Mane wrote: > > Hi team, > Here is the Infra Jira ticket to track the progress on this. > https://issues.apache.org/jira/browse/OFBIZ-11471 > > - Best regards, > Swapnil M Mane, > ofbiz.apache.org > > On Tue, Mar 17, 2020 at 10:18 AM Swapnil M Mane > wrote: > > > > Hello team, > > > > For the following repositories, the Git PR notifications are sent to the > > dev@ofbiz.apache.org list. > > > > https://github.com/apache/ofbiz > > https://github.com/apache/ofbiz-framework > > https://github.com/apache/ofbiz-plugins > > https://github.com/apache/ofbiz-tools > > > > Similar to the ofbiz-site repository, > > I will request the Infra team to move these notifications to > > notificati...@ofbiz.apache.org list. > > > > Best regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > > > > > On Mon, Mar 9, 2020 at 5:50 PM Swapnil M Mane > > wrote: > >> > >> Hello team, > >> Here is the Jira ticket to track the progress for this activity > >> https://issues.apache.org/jira/browse/INFRA-19945 > >> > >> Best regards, > >> Swapnil M Mane, > >> ofbiz.apache.org > >> > >> > >> > >> On Sat, Feb 29, 2020 at 10:24 AM Swapnil M Mane > >> wrote: > >>> > >>> Thank you team for inputs, will sync up with the Infra team to proceed > >>> with this. > >>> > >>> Best regards, > >>> Swapnil M Mane, > >>> ofbiz.apache.org > >>> > >>> > >>> > >>> On Thu, Feb 27, 2020 at 3:14 PM Pierre Smits > >>> wrote: > >>>> > >>>> Good advice, Michael. But that don't always happen. > >>>> > >>>> Met vriendelijke groet, > >>>> > >>>> Pierre Smits > >>>> *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since > >>>> 2008 (without privileges) > >>>> > >>>> *Apache Trafodion <https://trafodion.apache.org>, Vice President* > >>>> *Apache Directory <https://directory.apache.org>, PMC Member* > >>>> Apache Incubator <https://incubator.apache.org>, committer > >>>> Apache Steve <https://steve.apache.org>, committer > >>>> > >>>> > >>>> On Thu, Feb 27, 2020 at 10:35 AM Michael Brohl > >>>> wrote: > >>>> > >>>> > Every Git PR also needs a Jira, for which the notifications go to the > >>>> > notifications mailing list. > >>>> > > >>>> > If people want to contribute and follow, they should subscribe to > >>>> > notifications. > >>>> > > >>>> > Maybe we should send a reminder and encourage them to do so instead of > >>>> > mixing notifications and dev again. > >>>> > > >>>> > Michael Brohl > >>>> > > >>>> > ecomify GmbH - www.ecomify.de > >>>> > > >>>> > > >>>> > Am 27.02.20 um 09:54 schrieb Pierre Smits: > >>>> > > With the great difference between the numbers of subscribers of dev@ > >>>> > > and > >>>> > > notifications@ (last time I checked notifications@ had around 50), I > >>>> > > advise against it. > >>>> > > > >>>> > > If we want more people to contribute we need more than just the > >>>> > > handful > >>>> > of > >>>> > > active committers/contributors and employees of system integrators, > >>>> > > we > >>>> > need > >>>> > > to ensure that such notifications get sent to largest subset of our > >>>> > > community (dev@). > >>>> > > > >>>> > > Met vriendelijke groet, > >>>> > > > >>>> > > Pierre Smits > >>>> > > *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> > >&g
Re: [GitHub] [ofbiz-site] PierreSmits commented on issue #1: Improved: widget-theme.xsd typos (OFBIZ-11421)
Hi team, Here is the Infra Jira ticket to track the progress on this. https://issues.apache.org/jira/browse/OFBIZ-11471 - Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Mar 17, 2020 at 10:18 AM Swapnil M Mane wrote: > > Hello team, > > For the following repositories, the Git PR notifications are sent to the > dev@ofbiz.apache.org list. > > https://github.com/apache/ofbiz > https://github.com/apache/ofbiz-framework > https://github.com/apache/ofbiz-plugins > https://github.com/apache/ofbiz-tools > > Similar to the ofbiz-site repository, > I will request the Infra team to move these notifications to > notificati...@ofbiz.apache.org list. > > Best regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Mon, Mar 9, 2020 at 5:50 PM Swapnil M Mane wrote: >> >> Hello team, >> Here is the Jira ticket to track the progress for this activity >> https://issues.apache.org/jira/browse/INFRA-19945 >> >> Best regards, >> Swapnil M Mane, >> ofbiz.apache.org >> >> >> >> On Sat, Feb 29, 2020 at 10:24 AM Swapnil M Mane >> wrote: >>> >>> Thank you team for inputs, will sync up with the Infra team to proceed with >>> this. >>> >>> Best regards, >>> Swapnil M Mane, >>> ofbiz.apache.org >>> >>> >>> >>> On Thu, Feb 27, 2020 at 3:14 PM Pierre Smits wrote: >>>> >>>> Good advice, Michael. But that don't always happen. >>>> >>>> Met vriendelijke groet, >>>> >>>> Pierre Smits >>>> *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since >>>> 2008 (without privileges) >>>> >>>> *Apache Trafodion <https://trafodion.apache.org>, Vice President* >>>> *Apache Directory <https://directory.apache.org>, PMC Member* >>>> Apache Incubator <https://incubator.apache.org>, committer >>>> Apache Steve <https://steve.apache.org>, committer >>>> >>>> >>>> On Thu, Feb 27, 2020 at 10:35 AM Michael Brohl >>>> wrote: >>>> >>>> > Every Git PR also needs a Jira, for which the notifications go to the >>>> > notifications mailing list. >>>> > >>>> > If people want to contribute and follow, they should subscribe to >>>> > notifications. >>>> > >>>> > Maybe we should send a reminder and encourage them to do so instead of >>>> > mixing notifications and dev again. >>>> > >>>> > Michael Brohl >>>> > >>>> > ecomify GmbH - www.ecomify.de >>>> > >>>> > >>>> > Am 27.02.20 um 09:54 schrieb Pierre Smits: >>>> > > With the great difference between the numbers of subscribers of dev@ >>>> > > and >>>> > > notifications@ (last time I checked notifications@ had around 50), I >>>> > > advise against it. >>>> > > >>>> > > If we want more people to contribute we need more than just the handful >>>> > of >>>> > > active committers/contributors and employees of system integrators, we >>>> > need >>>> > > to ensure that such notifications get sent to largest subset of our >>>> > > community (dev@). >>>> > > >>>> > > Met vriendelijke groet, >>>> > > >>>> > > Pierre Smits >>>> > > *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> >>>> > since >>>> > > 2008 (without privileges) >>>> > > >>>> > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* >>>> > > *Apache Directory <https://directory.apache.org>, PMC Member* >>>> > > Apache Incubator <https://incubator.apache.org>, committer >>>> > > Apache Steve <https://steve.apache.org>, committer >>>> > > >>>> > > >>>> > > On Thu, Feb 27, 2020 at 9:33 AM Michael Brohl >>>> > > >>>> > > wrote: >>>> > > >>>> > >> +1, Thanks Swapnil! >>>> > >> >>>> > >> Michael >>>> > >> >>>> > >> Am 27.02.20 um 09:17 schrieb Swapnil M Mane: >>>> > >>> Hi team, >>>> > >>> Should we move these Git notification to >>>> > notificati...@ofbiz.apache.org >>>> > >>> list [1] that we created in the past to avoid notification traffic on >>>> > dev >>>> > >>> list, thoughts? >>>> > >>> >>>> > >>> [1] https://s.apache.org/0jdhc >>>> > >>> >>>> > >>> >>>> > >>> Best regards, >>>> > >>> Swapnil M Mane, >>>> > >>> ofbiz.apache.org >>>> > >>> >>>> > >>> >>>> > >>> >>>> > >>> On Wed, Feb 26, 2020 at 3:24 PM GitBox wrote: >>>> > >>> >>>> > >>>> PierreSmits commented on issue #1: Improved: widget-theme.xsd typos >>>> > >>>> (OFBIZ-11421) >>>> > >>>> URL: >>>> > https://github.com/apache/ofbiz-site/pull/1#issuecomment-591338641 >>>> > >>>> >>>> > >>>> >>>> > >>>> Done. >>>> > >>>> >>>> > >>>> >>>> > >>>> This is an automated message from the Apache Git Service. >>>> > >>>> To respond to the message, please log on to GitHub and use the >>>> > >>>> URL above to go to the specific comment. >>>> > >>>> >>>> > >>>> For queries about this service, please contact Infrastructure at: >>>> > >>>> us...@infra.apache.org >>>> > >>>> >>>> > >>>> >>>> > >>>> With regards, >>>> > >>>> Apache Git Services >>>> > >>>> >>>> > >> >>>> > >>>> >
Re: [GitHub] [ofbiz-site] PierreSmits commented on issue #1: Improved: widget-theme.xsd typos (OFBIZ-11421)
Hello team, For the following repositories, the Git PR notifications are sent to the dev@ofbiz.apache.org list. https://github.com/apache/ofbiz https://github.com/apache/ofbiz-framework https://github.com/apache/ofbiz-plugins https://github.com/apache/ofbiz-tools Similar to the ofbiz-site repository, I will request the Infra team to move these notifications to notificati...@ofbiz.apache.org list. Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Mar 9, 2020 at 5:50 PM Swapnil M Mane wrote: > Hello team, > Here is the Jira ticket to track the progress for this activity > https://issues.apache.org/jira/browse/INFRA-19945 > > Best regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Sat, Feb 29, 2020 at 10:24 AM Swapnil M Mane > wrote: > >> Thank you team for inputs, will sync up with the Infra team to proceed >> with this. >> >> Best regards, >> Swapnil M Mane, >> ofbiz.apache.org >> >> >> >> On Thu, Feb 27, 2020 at 3:14 PM Pierre Smits >> wrote: >> >>> Good advice, Michael. But that don't always happen. >>> >>> Met vriendelijke groet, >>> >>> Pierre Smits >>> *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> >>> since >>> 2008 (without privileges) >>> >>> *Apache Trafodion <https://trafodion.apache.org>, Vice President* >>> *Apache Directory <https://directory.apache.org>, PMC Member* >>> Apache Incubator <https://incubator.apache.org>, committer >>> Apache Steve <https://steve.apache.org>, committer >>> >>> >>> On Thu, Feb 27, 2020 at 10:35 AM Michael Brohl >> > >>> wrote: >>> >>> > Every Git PR also needs a Jira, for which the notifications go to the >>> > notifications mailing list. >>> > >>> > If people want to contribute and follow, they should subscribe to >>> > notifications. >>> > >>> > Maybe we should send a reminder and encourage them to do so instead of >>> > mixing notifications and dev again. >>> > >>> > Michael Brohl >>> > >>> > ecomify GmbH - www.ecomify.de >>> > >>> > >>> > Am 27.02.20 um 09:54 schrieb Pierre Smits: >>> > > With the great difference between the numbers of subscribers of dev@ >>> and >>> > > notifications@ (last time I checked notifications@ had around 50), >>> I >>> > > advise against it. >>> > > >>> > > If we want more people to contribute we need more than just the >>> handful >>> > of >>> > > active committers/contributors and employees of system integrators, >>> we >>> > need >>> > > to ensure that such notifications get sent to largest subset of our >>> > > community (dev@). >>> > > >>> > > Met vriendelijke groet, >>> > > >>> > > Pierre Smits >>> > > *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> >>> > since >>> > > 2008 (without privileges) >>> > > >>> > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* >>> > > *Apache Directory <https://directory.apache.org>, PMC Member* >>> > > Apache Incubator <https://incubator.apache.org>, committer >>> > > Apache Steve <https://steve.apache.org>, committer >>> > > >>> > > >>> > > On Thu, Feb 27, 2020 at 9:33 AM Michael Brohl < >>> michael.br...@ecomify.de> >>> > > wrote: >>> > > >>> > >> +1, Thanks Swapnil! >>> > >> >>> > >> Michael >>> > >> >>> > >> Am 27.02.20 um 09:17 schrieb Swapnil M Mane: >>> > >>> Hi team, >>> > >>> Should we move these Git notification to >>> > notificati...@ofbiz.apache.org >>> > >>> list [1] that we created in the past to avoid notification traffic >>> on >>> > dev >>> > >>> list, thoughts? >>> > >>> >>> > >>> [1] https://s.apache.org/0jdhc >>> > >>> >>> > >>> >>> > >>> Best regards, >>> > >>> Swapnil M Mane, >>> > >>> ofbiz.apache.org >>> > >>> >>> > >>> >>> > >>> >>> > >>> On Wed, Feb 26, 2020 at 3:24 PM GitBox wrote: >>> > >>> >>> > >>>> PierreSmits commented on issue #1: Improved: widget-theme.xsd >>> typos >>> > >>>> (OFBIZ-11421) >>> > >>>> URL: >>> > https://github.com/apache/ofbiz-site/pull/1#issuecomment-591338641 >>> > >>>> >>> > >>>> >>> > >>>> Done. >>> > >>>> >>> > >>>> >>> > >>>> This is an automated message from the Apache Git Service. >>> > >>>> To respond to the message, please log on to GitHub and use the >>> > >>>> URL above to go to the specific comment. >>> > >>>> >>> > >>>> For queries about this service, please contact Infrastructure at: >>> > >>>> us...@infra.apache.org >>> > >>>> >>> > >>>> >>> > >>>> With regards, >>> > >>>> Apache Git Services >>> > >>>> >>> > >> >>> > >>> > >>> >>
Re: Demo instance for OFBiz 17.12 release and remove 13.07 demo
Thank you everyone for your response. Hi Jacques, I will take care of this and will sync with you and the team in case any help needed. Best regards, Swapnil M Mane, ofbiz.apache.org On Sat, Mar 14, 2020 at 4:32 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Hi, > > Someone will handle it? > > Jacques > > Le 06/03/2020 à 10:34, Swapnil M Mane a écrit : > > Hello team, > > Current we have three demo instances [1] for OFBiz. > > > > -- Current Stable Release 16.11 - Demo > > https://demo-stable.ofbiz.apache.org/ordermgr/control/main > > > > -- Developer Trunk - Demo > > https://demo-trunk.ofbiz.apache.org/ordermgr/control/main > > > > -- Previous Stable Release 13.07 - Demo > > https://demo-old.ofbiz.apache.org/ordermgr/control/main > > > > As we have our new OFBiz release 17.12, should we think of taking the > > following actions: > > > > 1. The 'Current Stable Release' instance should have release 17.12 > > i.e. demo-stable.ofbiz.apache.org should deploy on release 17.12 > > > > 2. The 'Previous Stable Release' instance should have release 16.11 > > i.e. demo-old.ofbiz.apache.org should deploy on 16.11 > > > > After this migration, we will *no longer have 13.07 - Demo* instance. > > > > Here are some more details about the 13.07 demo instance. > > The 13.07 instance gets down abruptly very frequently. > > After this, it requires manual interaction to restart, in recent times > > Jacques and I manually restarted it many times. > > Looking at the current scenarios, it seems our users are also not > > using 13.07 demo instance on a frequent basis, because no one from our > > users reports us when it is down ;-) > > > > [1] https://ofbiz.apache.org/ofbiz-demos.html > > > > Best regards, > > Swapnil M Mane, > > ofbiz.apache.org > >
Re: [GitHub] [ofbiz-site] PierreSmits commented on issue #1: Improved: widget-theme.xsd typos (OFBIZ-11421)
Hello team, Here is the Jira ticket to track the progress for this activity https://issues.apache.org/jira/browse/INFRA-19945 Best regards, Swapnil M Mane, ofbiz.apache.org On Sat, Feb 29, 2020 at 10:24 AM Swapnil M Mane wrote: > Thank you team for inputs, will sync up with the Infra team to proceed > with this. > > Best regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Thu, Feb 27, 2020 at 3:14 PM Pierre Smits > wrote: > >> Good advice, Michael. But that don't always happen. >> >> Met vriendelijke groet, >> >> Pierre Smits >> *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since >> 2008 (without privileges) >> >> *Apache Trafodion <https://trafodion.apache.org>, Vice President* >> *Apache Directory <https://directory.apache.org>, PMC Member* >> Apache Incubator <https://incubator.apache.org>, committer >> Apache Steve <https://steve.apache.org>, committer >> >> >> On Thu, Feb 27, 2020 at 10:35 AM Michael Brohl >> wrote: >> >> > Every Git PR also needs a Jira, for which the notifications go to the >> > notifications mailing list. >> > >> > If people want to contribute and follow, they should subscribe to >> > notifications. >> > >> > Maybe we should send a reminder and encourage them to do so instead of >> > mixing notifications and dev again. >> > >> > Michael Brohl >> > >> > ecomify GmbH - www.ecomify.de >> > >> > >> > Am 27.02.20 um 09:54 schrieb Pierre Smits: >> > > With the great difference between the numbers of subscribers of dev@ >> and >> > > notifications@ (last time I checked notifications@ had around 50), I >> > > advise against it. >> > > >> > > If we want more people to contribute we need more than just the >> handful >> > of >> > > active committers/contributors and employees of system integrators, we >> > need >> > > to ensure that such notifications get sent to largest subset of our >> > > community (dev@). >> > > >> > > Met vriendelijke groet, >> > > >> > > Pierre Smits >> > > *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> >> > since >> > > 2008 (without privileges) >> > > >> > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* >> > > *Apache Directory <https://directory.apache.org>, PMC Member* >> > > Apache Incubator <https://incubator.apache.org>, committer >> > > Apache Steve <https://steve.apache.org>, committer >> > > >> > > >> > > On Thu, Feb 27, 2020 at 9:33 AM Michael Brohl < >> michael.br...@ecomify.de> >> > > wrote: >> > > >> > >> +1, Thanks Swapnil! >> > >> >> > >> Michael >> > >> >> > >> Am 27.02.20 um 09:17 schrieb Swapnil M Mane: >> > >>> Hi team, >> > >>> Should we move these Git notification to >> > notificati...@ofbiz.apache.org >> > >>> list [1] that we created in the past to avoid notification traffic >> on >> > dev >> > >>> list, thoughts? >> > >>> >> > >>> [1] https://s.apache.org/0jdhc >> > >>> >> > >>> >> > >>> Best regards, >> > >>> Swapnil M Mane, >> > >>> ofbiz.apache.org >> > >>> >> > >>> >> > >>> >> > >>> On Wed, Feb 26, 2020 at 3:24 PM GitBox wrote: >> > >>> >> > >>>> PierreSmits commented on issue #1: Improved: widget-theme.xsd typos >> > >>>> (OFBIZ-11421) >> > >>>> URL: >> > https://github.com/apache/ofbiz-site/pull/1#issuecomment-591338641 >> > >>>> >> > >>>> >> > >>>> Done. >> > >>>> >> > >>>> >> > >>>> This is an automated message from the Apache Git Service. >> > >>>> To respond to the message, please log on to GitHub and use the >> > >>>> URL above to go to the specific comment. >> > >>>> >> > >>>> For queries about this service, please contact Infrastructure at: >> > >>>> us...@infra.apache.org >> > >>>> >> > >>>> >> > >>>> With regards, >> > >>>> Apache Git Services >> > >>>> >> > >> >> > >> > >> >
Demo instance for OFBiz 17.12 release and remove 13.07 demo
Hello team, Current we have three demo instances [1] for OFBiz. -- Current Stable Release 16.11 - Demo https://demo-stable.ofbiz.apache.org/ordermgr/control/main -- Developer Trunk - Demo https://demo-trunk.ofbiz.apache.org/ordermgr/control/main -- Previous Stable Release 13.07 - Demo https://demo-old.ofbiz.apache.org/ordermgr/control/main As we have our new OFBiz release 17.12, should we think of taking the following actions: 1. The 'Current Stable Release' instance should have release 17.12 i.e. demo-stable.ofbiz.apache.org should deploy on release 17.12 2. The 'Previous Stable Release' instance should have release 16.11 i.e. demo-old.ofbiz.apache.org should deploy on 16.11 After this migration, we will *no longer have 13.07 - Demo* instance. Here are some more details about the 13.07 demo instance. The 13.07 instance gets down abruptly very frequently. After this, it requires manual interaction to restart, in recent times Jacques and I manually restarted it many times. Looking at the current scenarios, it seems our users are also not using 13.07 demo instance on a frequent basis, because no one from our users reports us when it is down ;-) [1] https://ofbiz.apache.org/ofbiz-demos.html Best regards, Swapnil M Mane, ofbiz.apache.org
Re: [GitHub] [ofbiz-site] PierreSmits commented on issue #1: Improved: widget-theme.xsd typos (OFBIZ-11421)
Thank you team for inputs, will sync up with the Infra team to proceed with this. Best regards, Swapnil M Mane, ofbiz.apache.org On Thu, Feb 27, 2020 at 3:14 PM Pierre Smits wrote: > Good advice, Michael. But that don't always happen. > > Met vriendelijke groet, > > Pierre Smits > *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since > 2008 (without privileges) > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > *Apache Directory <https://directory.apache.org>, PMC Member* > Apache Incubator <https://incubator.apache.org>, committer > Apache Steve <https://steve.apache.org>, committer > > > On Thu, Feb 27, 2020 at 10:35 AM Michael Brohl > wrote: > > > Every Git PR also needs a Jira, for which the notifications go to the > > notifications mailing list. > > > > If people want to contribute and follow, they should subscribe to > > notifications. > > > > Maybe we should send a reminder and encourage them to do so instead of > > mixing notifications and dev again. > > > > Michael Brohl > > > > ecomify GmbH - www.ecomify.de > > > > > > Am 27.02.20 um 09:54 schrieb Pierre Smits: > > > With the great difference between the numbers of subscribers of dev@ > and > > > notifications@ (last time I checked notifications@ had around 50), I > > > advise against it. > > > > > > If we want more people to contribute we need more than just the handful > > of > > > active committers/contributors and employees of system integrators, we > > need > > > to ensure that such notifications get sent to largest subset of our > > > community (dev@). > > > > > > Met vriendelijke groet, > > > > > > Pierre Smits > > > *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> > > since > > > 2008 (without privileges) > > > > > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > > > *Apache Directory <https://directory.apache.org>, PMC Member* > > > Apache Incubator <https://incubator.apache.org>, committer > > > Apache Steve <https://steve.apache.org>, committer > > > > > > > > > On Thu, Feb 27, 2020 at 9:33 AM Michael Brohl < > michael.br...@ecomify.de> > > > wrote: > > > > > >> +1, Thanks Swapnil! > > >> > > >> Michael > > >> > > >> Am 27.02.20 um 09:17 schrieb Swapnil M Mane: > > >>> Hi team, > > >>> Should we move these Git notification to > > notificati...@ofbiz.apache.org > > >>> list [1] that we created in the past to avoid notification traffic on > > dev > > >>> list, thoughts? > > >>> > > >>> [1] https://s.apache.org/0jdhc > > >>> > > >>> > > >>> Best regards, > > >>> Swapnil M Mane, > > >>> ofbiz.apache.org > > >>> > > >>> > > >>> > > >>> On Wed, Feb 26, 2020 at 3:24 PM GitBox wrote: > > >>> > > >>>> PierreSmits commented on issue #1: Improved: widget-theme.xsd typos > > >>>> (OFBIZ-11421) > > >>>> URL: > > https://github.com/apache/ofbiz-site/pull/1#issuecomment-591338641 > > >>>> > > >>>> > > >>>> Done. > > >>>> > > >>>> > > >>>> This is an automated message from the Apache Git Service. > > >>>> To respond to the message, please log on to GitHub and use the > > >>>> URL above to go to the specific comment. > > >>>> > > >>>> For queries about this service, please contact Infrastructure at: > > >>>> us...@infra.apache.org > > >>>> > > >>>> > > >>>> With regards, > > >>>> Apache Git Services > > >>>> > > >> > > > > >
Re: [VOTE] [RELEASE] Apache OFBiz 17.12.01 (full version), vote #3
+1 Best regards, Swapnil M Mane, ofbiz.apache.org On Thu, Feb 27, 2020 at 3:20 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > This is the vote thread (3nd attempt) to release "Apache OFBiz 17.12.01": > this is the first release, containing the framework, applications and all > the plugins from the 17.12 release branches. > > The release files can be downloaded from here: > https://dist.apache.org/repos/dist/dev/ofbiz/ > > and are: > * apache-ofbiz-17.12.01.zip > * KEYS: text file with keys > * apache-ofbiz-17.12.01.zip.asc: the detached signature file > * apache-ofbiz-17.12.01.zip.sha512: checksum file > > Please download the zip file, build and test OFBiz and verify the signature > and checksum (for instructions on testing the signatures see > http://www.apache.org/info/verification.html). > > Vote: > > [ +1] release as Apache OFBiz 17.12.01 > [ -1] do not release > > This vote will be open for 5 days. > For more details about this process please read > http://www.apache.org/foundation/voting.html >
Re: [GitHub] [ofbiz-site] PierreSmits commented on issue #1: Improved: widget-theme.xsd typos (OFBIZ-11421)
Hi team, Should we move these Git notification to notificati...@ofbiz.apache.org list [1] that we created in the past to avoid notification traffic on dev list, thoughts? [1] https://s.apache.org/0jdhc Best regards, Swapnil M Mane, ofbiz.apache.org On Wed, Feb 26, 2020 at 3:24 PM GitBox wrote: > PierreSmits commented on issue #1: Improved: widget-theme.xsd typos > (OFBIZ-11421) > URL: https://github.com/apache/ofbiz-site/pull/1#issuecomment-591338641 > > >Done. > > > This is an automated message from the Apache Git Service. > To respond to the message, please log on to GitHub and use the > URL above to go to the specific comment. > > For queries about this service, please contact Infrastructure at: > us...@infra.apache.org > > > With regards, > Apache Git Services >
Re: In preparation for the first release from 17.12
Hi team, As our users are familiar with one unified application, so +1 to release "Apache OFBiz 17.12.01" (framework + plugins) And since the only the framework can be independently used to build any custom enterprise application +1 to release "Apache OFBiz Framework 17.12.01" (framework) I don't have any strong opinion on releasing only plugins, fine with everything we decide as a community, so 0 to "Apache OFBiz Plugins 17.12.01" Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Feb 10, 2020 at 9:32 PM Nicolas Malin wrote: > Hi, > > I most in favor to propose two products like : > > "Apache OFBiz Framework 17.12.01" (framework) > and > "Apache OFBiz Full 17.12.01" (framework + plugins) > > For advanced user, they would use the framework only and retrieve wanted > plugins. > > For discovery, the full version would be available and recommended. > > I don't think that publish plugins alone or each plugin alone would be > an interest for user > > Nicolas > > On 08/02/2020 11:04, Jacopo Cappellato wrote: > > Hi all, > > > > based on various threads in this list, the time we will prepare the first > > release from the 17.12 branch is getting close and, since this is the > first > > one in which the plugins are separated from the framework, there are a > > few decisions to take. > > > > Should we release two products or just one as in the past? > > Two products mean: > > "Apache OFBiz Framework 17.12.01" > > and > > "Apache OFBiz Plugins 17.12.01" > > One product mean" > > "Apache OFBiz 17.12.01" (framework + plugins) > > > > Alternatively, we could publish the two products at different times; > first > > publish "Apache OFBiz Framework 17.12.01" and then later in the year > > publish "Apache OFBiz Plugins 17.12.01"; if this is going to happen then > we > > could have for example multiple releases of the Plugins based on the same > > release of the framework. > > > > One other option is to release independently each plugin (or the ones > that > > we consider stable enough) rather than all the plugins in one file. > > > > Thanks, > > > > Jacopo > > >
[Discussion] Theme for upcoming OFBiz community days?
Hello team, As we have our this year's first OFBiz community day from 21st – 25th February https://s.apache.org/1y062 During the planning of community days, Nicolas suggested a very nice idea, Quoting him, "Do we try for this February to focus on a particular effort: as convert old minilang service to groovy ? or FTL screen to XML." I like the idea, if we conclude on a particular topic, we can set that as a theme for this community days. Addition note: Even after defining theme, contributors are free to make a contribution to their choices. We are just assuming if we set a theme, more contributions are expected in that particular area. Thoughts? P.S. If you are interested in participating in the planning for OFBiz community days, Please free to reply at https://s.apache.org/8fmlz thread OR let us know here on the current thread. We have created a private slack group for the planning and execution discussion, will add you to the group. Best regards, Swapnil M Mane, ofbiz.apache.org
Re: Github & notifications
On Mon, Feb 3, 2020 at 6:10 PM Jacques Le Roux wrote: > It could be indirectly constrained by the ASF dual host, only PMC members > show there. I guess ASF members would also show. > > Jacques > > Le 03/02/2020 à 13:34, Swapnil M Mane a écrit : > > Hi Pierre, > > > > As mentioned, in my last email, > > https://github.com/orgs/apache/teams/ofbiz-committers > > The link above is accessible to members only, it is GitHub related thing, > > don't have much idea on it. > Just for clarification, by members I mean, 'GitHub OFBiz committers team members'. > > Just for information, currently, it showing there are 9 members in this > > team. > > > > Best regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > > > > > On Mon, Feb 3, 2020 at 5:54 PM Pierre Smits > wrote: > > > >> Why is this overview ( > >> https://github.com/orgs/apache/teams/ofbiz-committers) > >> hidden? > >> > >> Best regards, > >> > >> Pierre Smits > >> > >> *Apache Trafodion <https://trafodion.apache.org>, Vice President* > >> *Apache Directory <https://directory.apache.org>, PMC Member* > >> Apache Incubator <https://incubator.apache.org>, committer > >> *Apache OFBiz <https://ofbiz.apache.org>, contributor (without > privileges) > >> since 2008* > >> Apache Steve <https://steve.apache.org>, committer > >> > >> > >> On Mon, Feb 3, 2020 at 1:05 PM Swapnil M Mane > >> wrote: > >> > >>> +1, Jira should be in place independent of the contribution channel. > >>> > >>> Apart from this, it seems we have limited members in GitHub OFBiz > >>> Committers team [1], > >>> So I am not sure on all the committers are getting the pull request > >>> notifications. > >>> > >>> We can use notificati...@ofbiz.apache.org list for the activities > >> related > >>> to pull request > >>> (again this doesn't mean we can skip Jira ticket). > >>> > >>> "Notification on pull request activity" - this is followed by various > >>> Apache projects, like Airflow, Roller etc. > >>> Some projects like Cassandra even have dedicated list for PR > notification > >>> but I think, we don't need a dedicated list for PR, > >>> notificati...@ofbiz.apache.org should work for us. > >>> > >>> As Gil mentioned, we can also explore the Jira + GitHub integration. > >>> > >>> [1] https://github.com/orgs/apache/teams/ofbiz-committers > >>> The link above is accessible to members only. > >>> > >>> [2] https://lists.apache.org/list.html?p...@cassandra.apache.org > >>> > >>> Best regards, > >>> Swapnil M Mane, > >>> ofbiz.apache.org > >>> > >>> > >>> On Mon, Feb 3, 2020 at 4:46 PM Michael Brohl > > >>> wrote: > >>> > >>>> I'm automatically informed about the pull requests, I think that all > >>>> committers get those emails. > >>>> > >>>> IMO, we should make the creation of a Jira mandatory independent of > the > >>>> contribution channel (patch or PR). That would inform everyone about > >> the > >>>> contribution and we have a valid starting point for questions, > >>>> discussion etc. regarding the contribution. > >>>> > >>>> I feel that solely handling this on Github does not increase > >>> transparency. > >>>> Regards, > >>>> > >>>> Michael Brohl > >>>> > >>>> ecomify GmbH - www.ecomify.de > >>>> > >>>> > >>>> Am 03.02.20 um 12:07 schrieb Pierre Smits: > >>>>> Hi All, > >>>>> > >>>>> With the move to Git, we can expect more pull request from Github > >> (see > >>>> also > >>>>> other threads where postings regarding feature branches appeared). > >>>>> Unfortunately, currently no notifications appear in a mailing list > >> when > >>>>> those PullRequests are initiated. > >>>>> > >>>>> It seems to me that, if we want to get more engagements (from github > >>>>> contributors), aspects such as PullRequests should sent a > >> notification > >>> to > >>>>> the dev ml. Otherwise these PullRequests remain in limbo, and we risk > >>> of > >>>>> losing these contributors. > >>>>> > >>>>> > >>>>> Best regards, > >>>>> > >>>>> Pierre Smits > >>>>> > >>>>> *Apache Trafodion <https://trafodion.apache.org>, Vice President* > >>>>> *Apache Directory <https://directory.apache.org>, PMC Member* > >>>>> Apache Incubator <https://incubator.apache.org>, committer > >>>>> *Apache OFBiz <https://ofbiz.apache.org>, contributor (without > >>>> privileges) > >>>>> since 2008* > >>>>> Apache Steve <https://steve.apache.org>, committer > >>>>> > >>>> >
Re: Github & notifications
Hi Pierre, As mentioned, in my last email, https://github.com/orgs/apache/teams/ofbiz-committers The link above is accessible to members only, it is GitHub related thing, don't have much idea on it. Just for information, currently, it showing there are 9 members in this team. Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Feb 3, 2020 at 5:54 PM Pierre Smits wrote: > Why is this overview ( > https://github.com/orgs/apache/teams/ofbiz-committers) > hidden? > > Best regards, > > Pierre Smits > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > *Apache Directory <https://directory.apache.org>, PMC Member* > Apache Incubator <https://incubator.apache.org>, committer > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) > since 2008* > Apache Steve <https://steve.apache.org>, committer > > > On Mon, Feb 3, 2020 at 1:05 PM Swapnil M Mane > wrote: > > > +1, Jira should be in place independent of the contribution channel. > > > > Apart from this, it seems we have limited members in GitHub OFBiz > > Committers team [1], > > So I am not sure on all the committers are getting the pull request > > notifications. > > > > We can use notificati...@ofbiz.apache.org list for the activities > related > > to pull request > > (again this doesn't mean we can skip Jira ticket). > > > > "Notification on pull request activity" - this is followed by various > > Apache projects, like Airflow, Roller etc. > > Some projects like Cassandra even have dedicated list for PR notification > > but I think, we don't need a dedicated list for PR, > > notificati...@ofbiz.apache.org should work for us. > > > > As Gil mentioned, we can also explore the Jira + GitHub integration. > > > > [1] https://github.com/orgs/apache/teams/ofbiz-committers > > The link above is accessible to members only. > > > > [2] https://lists.apache.org/list.html?p...@cassandra.apache.org > > > > Best regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > > > On Mon, Feb 3, 2020 at 4:46 PM Michael Brohl > > wrote: > > > > > I'm automatically informed about the pull requests, I think that all > > > committers get those emails. > > > > > > IMO, we should make the creation of a Jira mandatory independent of the > > > contribution channel (patch or PR). That would inform everyone about > the > > > contribution and we have a valid starting point for questions, > > > discussion etc. regarding the contribution. > > > > > > I feel that solely handling this on Github does not increase > > transparency. > > > > > > Regards, > > > > > > Michael Brohl > > > > > > ecomify GmbH - www.ecomify.de > > > > > > > > > Am 03.02.20 um 12:07 schrieb Pierre Smits: > > > > Hi All, > > > > > > > > With the move to Git, we can expect more pull request from Github > (see > > > also > > > > other threads where postings regarding feature branches appeared). > > > > Unfortunately, currently no notifications appear in a mailing list > when > > > > those PullRequests are initiated. > > > > > > > > It seems to me that, if we want to get more engagements (from github > > > > contributors), aspects such as PullRequests should sent a > notification > > to > > > > the dev ml. Otherwise these PullRequests remain in limbo, and we risk > > of > > > > losing these contributors. > > > > > > > > > > > > Best regards, > > > > > > > > Pierre Smits > > > > > > > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > > > > *Apache Directory <https://directory.apache.org>, PMC Member* > > > > Apache Incubator <https://incubator.apache.org>, committer > > > > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without > > > privileges) > > > > since 2008* > > > > Apache Steve <https://steve.apache.org>, committer > > > > > > > > > > > > >
Re: Github & notifications
+1, Jira should be in place independent of the contribution channel. Apart from this, it seems we have limited members in GitHub OFBiz Committers team [1], So I am not sure on all the committers are getting the pull request notifications. We can use notificati...@ofbiz.apache.org list for the activities related to pull request (again this doesn't mean we can skip Jira ticket). "Notification on pull request activity" - this is followed by various Apache projects, like Airflow, Roller etc. Some projects like Cassandra even have dedicated list for PR notification but I think, we don't need a dedicated list for PR, notificati...@ofbiz.apache.org should work for us. As Gil mentioned, we can also explore the Jira + GitHub integration. [1] https://github.com/orgs/apache/teams/ofbiz-committers The link above is accessible to members only. [2] https://lists.apache.org/list.html?p...@cassandra.apache.org Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Feb 3, 2020 at 4:46 PM Michael Brohl wrote: > I'm automatically informed about the pull requests, I think that all > committers get those emails. > > IMO, we should make the creation of a Jira mandatory independent of the > contribution channel (patch or PR). That would inform everyone about the > contribution and we have a valid starting point for questions, > discussion etc. regarding the contribution. > > I feel that solely handling this on Github does not increase transparency. > > Regards, > > Michael Brohl > > ecomify GmbH - www.ecomify.de > > > Am 03.02.20 um 12:07 schrieb Pierre Smits: > > Hi All, > > > > With the move to Git, we can expect more pull request from Github (see > also > > other threads where postings regarding feature branches appeared). > > Unfortunately, currently no notifications appear in a mailing list when > > those PullRequests are initiated. > > > > It seems to me that, if we want to get more engagements (from github > > contributors), aspects such as PullRequests should sent a notification to > > the dev ml. Otherwise these PullRequests remain in limbo, and we risk of > > losing these contributors. > > > > > > Best regards, > > > > Pierre Smits > > > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > > *Apache Directory <https://directory.apache.org>, PMC Member* > > Apache Incubator <https://incubator.apache.org>, committer > > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without > privileges) > > since 2008* > > Apache Steve <https://steve.apache.org>, committer > > > >
Re: [VOTE] [RELEASE] Apache OFBiz 16.11.07
+1 Best regards, Swapnil M Mane, ofbiz.apache.org On Thu, Jan 30, 2020 at 7:43 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > This is the vote thread to release a new bug fix release for the > release16.11 branch. This new release, "Apache OFBiz 16.11.07" will > supersede all the previous releases from the same branch. > Please consider that this may be the last release in the 16.11 series and > in the future releases will be published from the newer series only. > > The release files can be downloaded from here: > https://dist.apache.org/repos/dist/dev/ofbiz/ > > and are: > * apache-ofbiz-16.11.07.zip > * KEYS: text file with keys > * apache-ofbiz-16.11.07.zip.asc: the detached signature file > * apache-ofbiz-16.11.07.zip.sha512: checksum file > > Please download and test the zip file and its signatures (for instructions > on testing the signatures see http://www.apache.org/info/verification.html > ). > > Vote: > [ +1] release as Apache OFBiz 16.11.07 > [ -1] do not release > > This vote will be open for 5 days. > For more details about this process refer to > http://www.apache.org/foundation/voting.html > > Kind Regards, > > Jacopo >
Re: Migrate all docbook files to asciidoc ?
Thank you so much Olivier for this initiative, indeed the documentation is a critical part for a successful open source project. I am inclined with the Taher's input here. - Best regards, Swapnil M Mane, ofbiz.apache.org On Wed, Jan 29, 2020 at 1:25 AM Taher Alkhateeb wrote: > It sounds like a good initiative to me. I would be careful about pure > converting without reviewing. Some of the documentation is quite outdated > and so maybe convert + review is a reasonable approach. > > On Tue, Jan 28, 2020, 9:52 PM Olivier Heintz wrote: > > > Hi everyone, > > > > I wanted to make progress on the OFBiz documentation, and thus continue > > the existing tasks, at first the one on the accounting component. > > > > It's a bit painful to have to work between the old files in docbook and > > the new ones in asciidoc. > > For me it would be simpler to migrate all the docbooks first, and then > > rework the result. > > > > Does this process bother anyone ? > > > > Olivier > > > > > > > > > > > > > > >
Re: [VOTE] Do not release R17 and directly publish R18 instead.
-1 Best regards, Swapnil M Mane, ofbiz.apache.org On Fri, Jan 24, 2020 at 3:57 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Hi, > > R16 is now an old distribution and has almost reached its end of support. > We can soon expect a last release but we need to think about the next to be > released package > > Some would prefer to release R17 before releasing R18, some would prefer > to bypass R17 release and directly publish R18 instead. > > Vote: > [ +1] Do not release R17 and directly publish R18 instead. > [ -1] Release R17 before releasing R18 > > We had already 3 months to discuss without reaching a consensus, so this > vote will be only open for a week. > > Note that it's not a formal vote to release R17 or R18, as that is another > process documented at > > https://cwiki.apache.org/confluence/display/OFBIZ/Release+Management+Guide+for+OFBiz > > Thank you for your attention > > Jacques > >
Re: Welcome to Olivier Heintz as new committer!
Many congratulations Olivier, welcome aboard!! Best regards, Swapnil M Mane, ofbiz.apache.org On Thu, Jan 16, 2020 at 7:53 PM Taher Alkhateeb wrote: > The OFBiz PMC has invited Olivier Heintz to become a new committer and > we are happy to announce that he has accepted this role. > > Some of the reasons for inviting Olivier Heintz include: > > - He is invested in the OFBiz project and has been a member for many years > - He is taking an initiative towards improving the UI part of the system > - He has functional experience in various areas of the framework > - He enjoys working with the community and collaborating with others > > Please join me in welcoming and congratulating Olivier! > > Cheers, > Taher Alkhateeb >
Re: Welcome Gil Portenseigne and Mathieu Lirzin as new PMC members
Many congratulations Gil and Mathieu!! :) Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Dec 3, 2019 at 3:56 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > The OFBiz PMC has invited Gil Portenseigne and Mathieu Lirzin to become > members of the committee and we are glad to announce that they have > accepted the nomination. > > On behalf of the OFBiz PMC, welcome on board! >
Re: Git repo for each ofbiz plugin
Hi Deepak, Thanks for bringing this topic. The idea looks reasonability good to me. Various Apache projects [1] are following this approach of maintaining the plugins in separate repository. Cordova [2] and Maven [3] are good examples of this. [1] https://github.com/apache?utf8=%E2%9C%93&q=plugins [2] https://github.com/apache?utf8=%E2%9C%93&q=cordova+plugins [3] https://github.com/apache?utf8=%E2%9C%93&q=maven+plugins On Wed, Nov 6, 2019 at 2:31 PM Deepak Dixit wrote: > Hi All, > > As we moved to from svn to git, so I think now its time to create new git > repository for each and indiviaual plugins instead of maintaing single > ofbiz-plugins.git > > It will help to manage the plugin life cycle properly, > if anyone want to use single or set of plugins they can easiliy setup with > the proposed way. > +1 > If we create git repo for each plugins definately we have to manage the > dependencies and release properly, I am confident that as a community we > can manage this thing :) > Indeed, it will be some work but like you I am also confident our vibrant community will manage :) > > If this looks good, I'll initiate further process for the same. > > Please share your thoughts on this. > > Thanks & Regards > -- > Deepak Dixit > ofbiz.apache.org
Re: Migrating to Git
Thank you Deepak for the notes. Team, We are maintaining this document https://cwiki.apache.org/confluence/x/Xg-HBg containing details to help us in migrating from SVN to Git. Please feel free to edit if you feel some information or TODO is missing. Best regards, Swapnil M Mane, ofbiz.apache.org On Fri, Oct 18, 2019 at 12:13 PM Deepak Dixit wrote: > +1 > Once we agree to move to git, we can ask infra for further setup. > > I think we have our readonly git mirror at gitbox, we need to do following: > > - As infra to mark svn ofbiz directory to readonly, make git mirror to > writable > - Update buildboat to use git > - Migrate svn pre/post commit hook > - Update the ofbiz checkout link on website. > - Update the RAT tool if needed to use git repo > - > > > Thanks & Regards > -- > Deepak Dixit > ofbiz.apache.org > > > On Fri, Oct 18, 2019 at 11:26 AM Pranay Pandey < > pranay.pan...@hotwaxsystems.com> wrote: > > > +1 Swapnil M. > > > > Best regards, > > Pranay Pandey > > > > > > On Fri, Oct 18, 2019 at 10:37 AM Swapnil M Mane > > > wrote: > > > > > Thank you Mathieu for reviving the topic. > > > > > > Dear all, > > > As discussed previously, all the essential details are incorporated in > > this > > > document [1] to help us in migrating from SVN to Git. > > > Please have a look and let us know your kind feedback/thoughts. > > > Here are references [2] [3] to our previous discussions for your quick > > > reference. > > > > > > I also feel we should take the next steps in this direction. > > > > > > [1] https://cwiki.apache.org/confluence/x/Xg-HBg > > > [2] https://s.apache.org/lrr3x > > > [3] https://s.apache.org/qsral > > > > > > > > > Best regards, > > > Swapnil M Mane, > > > ofbiz.apache.org > > > > > > > > > > > > On Thu, Oct 17, 2019 at 7:51 PM Mathieu Lirzin < > > mathieu.lir...@nereide.fr> > > > wrote: > > > > > > > Now that the Git synchro is working again, I think it would be great > if > > > > we could move forward regarding the SVN to Git migration. > > > > > > > > I am not sure what needs be done to achieve such result, is it just a > > > > matter of opening a INFRA ticket on Jira? What can I do to help? > > > > > > > > Thanks. > > > > > > > > -- > > > > Mathieu Lirzin > > > > GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37 > > > > > > > > > >
Re: Migrating to Git
Thank you Mathieu for reviving the topic. Dear all, As discussed previously, all the essential details are incorporated in this document [1] to help us in migrating from SVN to Git. Please have a look and let us know your kind feedback/thoughts. Here are references [2] [3] to our previous discussions for your quick reference. I also feel we should take the next steps in this direction. [1] https://cwiki.apache.org/confluence/x/Xg-HBg [2] https://s.apache.org/lrr3x [3] https://s.apache.org/qsral Best regards, Swapnil M Mane, ofbiz.apache.org On Thu, Oct 17, 2019 at 7:51 PM Mathieu Lirzin wrote: > Now that the Git synchro is working again, I think it would be great if > we could move forward regarding the SVN to Git migration. > > I am not sure what needs be done to achieve such result, is it just a > matter of opening a INFRA ticket on Jira? What can I do to help? > > Thanks. > > -- > Mathieu Lirzin > GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37 >
Re: Architecture
Hello Swaroop, Along with the document shared by Jacques, the OFBiz tutorial [1] and video [2] could be a good starting point for learning OFBiz. [1] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Tutorial+-+A+Beginners+Development+Guide [2] https://www.youtube.com/watch?v=bIS2kftvsq4&list=PLobIkeUbRXqc-lwvbdbajPJdbWjFm82Dj Best regards, Swapnil M Mane, ofbiz.apache.org On Mon, Oct 14, 2019 at 4:01 PM SwaroopNaga wrote: > Hi Team, > > I am new to OfBiz , I want to understand flow and Architecture of > OfBiz , please provide me some resources or ways to understand OfBiz better > ... > > Thanks, > Swaroop. >
Re: Adding a CONTRIBUTING.adoc file to the “ofbiz-framework” repository (was: svn commit: r1867663 …)
+1 Mathieu for documenting these rules/conventions, thank you! Best regards, Swapnil M Mane, ofbiz.apache.org On Sun, Sep 29, 2019 at 5:08 PM Mathieu Lirzin wrote: > Hello, > > Pierre Smits writes: > > > Fyi: improvement (tickets) get ‘implemented’, and bugs get ‘fixed’. As > per > > established conventions. > > From what I understood from the examples and common practice [1], this > is only partially true. Improvement tickets can be associated with both > ‘Implemented:’ and ‘Improved:’ commits depending on the type of > improvement: > >- Refactoring => “Improved:” >- New feature => “Implemented:” > > [1] > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template > > > On Sat, 28 Sep 2019 at 15:50 Swapnil M Mane > wrote: > > > >> Hi Deepak, > >> > >> Happy to see your commits in action. :) > >> Just a minor suggestion, we put Jira ticket ID in separate line in > commit > >> log. > >> Also, add colon ':' in Thanks statement. > >> And since the ticket type is 'Improvement', it seems to me, we should > use > >> 'Improved' instead of 'Fixed'. > >> > >> Here is commit template for your quick reference > >> > >> > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template > >> > >> Following commit log template will help us in producing the monthly blog > >> development details. > > As a general rule, I would say that working on a “bug” ticket implies at > least one “Fixed:” commit, but it is possible to associate a > complementary refactoring “Improved:” commit to a “bug” ticket. On the > other hand an “improvement” ticket can not be associated with a “Fixed:” > commit. > > What about adding a CONTRIBUTING.adoc file the repository stating those > rules? This would make things far more visible and explicit than on > Confluence which is not very visible (I often to keep bookmarks to > retrieve some information) and far from the code. > > What do people think? > > -- > Mathieu Lirzin > GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37 >
Re: svn commit: r1867663 - /ofbiz/ofbiz-framework/trunk/framework/common/config/CommonEntityLabels.xml
Hi Deepak, Happy to see your commits in action. :) Just a minor suggestion, we put Jira ticket ID in separate line in commit log. Also, add colon ':' in Thanks statement. And since the ticket type is 'Improvement', it seems to me, we should use 'Improved' instead of 'Fixed'. Here is commit template for your quick reference https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template Following commit log template will help us in producing the monthly blog development details. Thanks for your cooperation. Best regards, Swapnil M Mane, ofbiz.apache.org On Sat, Sep 28, 2019 at 3:56 PM wrote: > Author: deepaknigam > Date: Sat Sep 28 10:26:09 2019 > New Revision: 1867663 > > URL: http://svn.apache.org/viewvc?rev=1867663&view=rev > Log: > Fixed: Serbian CommonEntityLabels for geo entity. (OFBIZ-11209) > Added missing entity label for Serbia. > Thanks Ulrich Heidfeld for your contribution. > > Modified: > > ofbiz/ofbiz-framework/trunk/framework/common/config/CommonEntityLabels.xml > > Modified: > ofbiz/ofbiz-framework/trunk/framework/common/config/CommonEntityLabels.xml > URL: > http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/framework/common/config/CommonEntityLabels.xml?rev=1867663&r1=1867662&r2=1867663&view=diff > > == > --- > ofbiz/ofbiz-framework/trunk/framework/common/config/CommonEntityLabels.xml > (original) > +++ > ofbiz/ofbiz-framework/trunk/framework/common/config/CommonEntityLabels.xml > Sat Sep 28 10:26:09 2019 > @@ -8011,6 +8011,10 @@ > 圣皮埃尔和密克隆群岛 > è –çš®åŸƒçˆ¾å’Œå¯†å…‹éš†ç¾¤å³¶ > > + > +Serbien > +Serbia > + > > سان تومي وبرينسيبي > Sao Tome und Principe > > >
Re: Welcome Pranay Pandey as a new PMC member
Many many congratulations Pranay! Happy for you :-) Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Sep 24, 2019 at 9:07 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Pranay Pandey to become a new member of the > committee and we are glad to announce that he has accepted the nomination. > > Welcome on board Pranay! > > Jacques (on behalf of the OFBiz PMC) > >
Re: svn commit: r1866286 - in /ofbiz/ofbiz-framework/trunk/applications/product: config/ minilang/shipment/issuance/ minilang/shipment/receipt/ minilang/shipment/shipment/ servicedef/
Great, thanks so much Nicolas!
Best regards,
Swapnil M Mane,
ofbiz.apache.org
On Mon, Sep 2, 2019 at 8:54 PM Nicolas Malin
wrote:
> Hi all,
>
> With this last commit, I think we finish the conversion for CRUD in
> mini-lang to entity-auto :)
>
> \o/
>
> Now next step mini-lang to groovy !
>
> Cheers,
>
> Nicolas
>
> On 9/2/19 5:13 PM, nma...@apache.org wrote:
> > Author: nmalin
> > Date: Mon Sep 2 15:13:47 2019
> > New Revision: 1866286
> >
> > URL: http://svn.apache.org/viewvc?rev=1866286&view=rev
> > Log:
> > Improved: Convert Shipment Crud simple service to entity-auto
> > (OFBIZ-6996)
> > I converted all available shipment entities crud currently on simple
> service to entity-auto service :
> > * ItemIssuanceRole
> > * ShipmentItem
> > * ShipmentPackageContent
> > * ShipmentPackageRouteSeg
> > * ShipmentRouteSegment
> > * QuantityBreak
> >
> > I also transformed a simple method call to a permission service:
> checkCanChangeShipmentStatus, who check for a shipment is it on good status
> for the change.
> > With this last conversion, the permission control set on the service
> definition instead of core service
> >
> > Modified:
> >
> ofbiz/ofbiz-framework/trunk/applications/product/config/ProductErrorUiLabels.xml
> >
> ofbiz/ofbiz-framework/trunk/applications/product/minilang/shipment/issuance/IssuanceServices.xml
> >
> ofbiz/ofbiz-framework/trunk/applications/product/minilang/shipment/receipt/ShipmentReceiptServices.xml
> >
> ofbiz/ofbiz-framework/trunk/applications/product/minilang/shipment/shipment/ShipmentServices.xml
> >
> ofbiz/ofbiz-framework/trunk/applications/product/servicedef/secas_shipment.xml
> >
> ofbiz/ofbiz-framework/trunk/applications/product/servicedef/services_shipment.xml
> >
> > Modified:
> ofbiz/ofbiz-framework/trunk/applications/product/config/ProductErrorUiLabels.xml
> > URL:
> http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/applications/product/config/ProductErrorUiLabels.xml?rev=1866286&r1=1866285&r2=1866286&view=diff
> >
> ==
> > ---
> ofbiz/ofbiz-framework/trunk/applications/product/config/ProductErrorUiLabels.xml
> (original)
> > +++
> ofbiz/ofbiz-framework/trunk/applications/product/config/ProductErrorUiLabels.xml
> Mon Sep 2 15:13:47 2019
> > @@ -1489,6 +1489,10 @@
> > åˆ›å»ºå¿«é€Ÿæ·»åŠ å ˜åž‹æ•°æ ®æ—¶å
> ‘生交易错误：${errMessage}。
> >xml:lang="zh-TW">æ–°å»ºå¿«é€Ÿå¢žåŠ è®Šåž‹è³‡æ–™æ™‚ç™¼ç”Ÿäº¤æ˜“éŒ¯èª¤:
> ${errMessage}.
> >
> > +
> > +Cannot perform this operation when the
> shipment [${testShipment.shipmentId}] is in the
> ${testShipmentStatus.description} [${testShipment.statusId}]
> status."
> > +Impossible de réaliser l'opération
> demandée quand l'expédition [${testShipment.shipmentId}] est dans le
> statut ${testShipmentStatus.description} [${testShipment.statusId}]
> > +
> >key="variantevents.variantProductId_required_but_missing_enter_an_id">
> > variantProductId wir benötigt, fehlt
> aber, bitte geben Sie eine ID für die neue Produktvariante an.
> > variantProductId is required but missing,
> please enter an id for the new variant product.
> >
> > Modified:
> ofbiz/ofbiz-framework/trunk/applications/product/minilang/shipment/issuance/IssuanceServices.xml
> > URL:
> http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/applications/product/minilang/shipment/issuance/IssuanceServices.xml?rev=1866286&r1=1866285&r2=1866286&view=diff
> >
> ==
> > ---
> ofbiz/ofbiz-framework/trunk/applications/product/minilang/shipment/issuance/IssuanceServices.xml
> (original)
> > +++
> ofbiz/ofbiz-framework/trunk/applications/product/minilang/shipment/issuance/IssuanceServices.xml
> Mon Sep 2 15:13:47 2019
> > @@ -22,10 +22,6 @@ under the License.
> > xmlns="http://ofbiz.apache.org/Simple-Method";
> xsi:schemaLocation="http://ofbiz.apache.org/Simple-Method
> http://ofbiz.apache.org/dtds/simple-methods.xsd";>
> >
> >short-description="Create ItemIssuance">
> > -
> > - method-name="checkCanChangeShipmentStatusPacked"
> xml-resource="component://product/minilang/shipment/shipment/ShipmentServices.xml"/>
> > -
> > -
> >value-field=&q
Advance OFBiz tutorials
Hello team, In the year 2017, we revamped the OFBiz tutorial [1] and simplified it for new adopters. In this process, by design, we removed some advance topics to make the tutorial simpler. Now, we are planning to write tutorials on following advance OFBiz topics, -- ECA (Event Condition Action) -- Group Service -- Service Interface -- Extending an existing OOTB Entity -- Ajaxify the Request If you want any topic to be consider, please let us know. We will plan to include that topic in our roadmap. Also, if you willing to help in this effort, you are most welcome. [1] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Tutorial+-+A+Beginners+Development+Guide Best regards, Swapnil M Mane, ofbiz.apache.org
Re: [VOTE] [RELEASE] Apache OFBiz 16.11.06 - second attempt
+1, thank you Jacopo! Everything seems good - 1. Checksums and signing certificate $ ../ofbiz-tools/verify-ofbiz-release.sh apache-ofbiz-16.11.06.zip sha check of file: apache-ofbiz-16.11.06.zip Using sha file: apache-ofbiz-16.11.06.zip.sha512 apache-ofbiz-16.11.06.zip: 407F03CF C0A60B0F 363E83FC 55C0D301 DDF323DC 016B2C96 CA624791 046E8367 AE629A38 F4CE597F AE1E1F2E C504E895 D22E6C6A 4FA2E958 30F1EB3F 62A81E01 apache-ofbiz-16.11.06.zip: 407F03CF C0A60B0F 363E83FC 55C0D301 DDF323DC 016B2C96 CA624791 046E8367 AE629A38 F4CE597F AE1E1F2E C504E895 D22E6C6A 4FA2E958 30F1EB3F 62A81E01 sha checksum OK GPG verification output gpg: Signature made Tue Aug 27 15:05:16 2019 IST gpg:using RSA key 7A580908847AF9E0 gpg: Good signature from "Jacopo Cappellato (CODE SIGNING KEY) < jaco...@apache.org>" 2. Initializing gradle wrapper, build, and tests are successful, the steps followed are as follows (using macOS Mojave OS) - -- Unzip apache-ofbiz-16.11.06.zip -- Executed the ./gradle/init-gradle-wrapper cmd -- Executed load and test command $ ./gradlew loadDefault testIntegration BUILD SUCCESSFUL Best regards, Swapnil M Mane, ofbiz.apache.org On Tue, Aug 27, 2019 at 3:18 PM Jacopo Cappellato < jacopo.cappell...@gmail.com> wrote: > This is the second vote thread to release a new bug fix release for the > release16.11 branch. > This new release, "Apache OFBiz 16.11.06" will supersede all the previous > releases from the same branch. > The release files can be downloaded from here: > > https://dist.apache.org/repos/dist/dev/ofbiz/ > > and are: > > * apache-ofbiz-16.11.06.zip > * KEYS: text file with keys > * apache-ofbiz-16.11.06.zip.asc: the detached signature file > * apache-ofbiz-16.11.06.zip.sha512: checksum file > > Please download and test the zip file and its signatures (for instructions > on testing the signatures see http://www.apache.org/info/verification.html > ). > > The preview of the Release Notes can be found at: > https://ofbiz.apache.org/release-notes-16.11.06.html > > Vote: > [ +1] release as Apache OFBiz 16.11.06 > [ -1] do not release > > In order to provide enough time to discuss and test the candidate files, > this vote will be open for at least 10 days. > > For more details about this process please read > http://www.apache.org/foundation/voting.html > > Best Regards, > Jacopo Cappellato >
Re: [DISCUSSION] where download gradle-wrapper.jar ?
Thanks so much, Jacques and Nicolas for your help in this, highly appreciated. Also, thank you, everyone involved in the efforts! Best Regards, Swapnil M Mane, ofbiz.apache.org On Tue, Jul 9, 2019 at 8:22 PM Jacques Le Roux wrote: > Le 04/07/2019 à 12:06, Jacques Le Roux a écrit : > > Le 04/07/2019 à 11:07, Nicolas Malin a écrit : > >> On 03/07/2019 14:27, Jacques Le Roux wrote: > >>> Le 02/07/2019 à 09:45, Jacques Le Roux a écrit : > >>>> Le 02/07/2019 à 08:46, Jacopo Cappellato a écrit : > >>>>> On Tue, Jul 2, 2019 at 7:14 AM Jacques Le Roux < > jacques.le.r...@les7arts.com> > >>>>> wrote: > >>>>> > >>>>>> [...] > >>>>> > >>>>>> It's only a RM issue. It's when packaging that we are tying OFBiz > code > >>>>>> with a Gradle version. > >>>>>> > >>>>>> It's only then that we need to modify the gradlew script, to call an > >>>>>> init-gradle-wrapper script if the wrapper is missing. > >>>>>> > >>>>>> What do you think folks? Notably you Jacopo, with your RM hat on? > >>>>> > >>>>> I think that the direction we are heading is to not include it in the > >>>>> releases and add instructions in the release's README file to tell > the user > >>>>> how to download it. > >>>>> So we could keep the wrappers (if we like) in the trunk and/or > release > >>>>> branches and remove them when we package/publish a new release. > >>>>> > >>>>> Jacopo > >>>> > >>>> Keeping the wrapper in branches is certainly easier for demos, > Buildbot and working copies. > >>>> > >>>> For the releases, my proposition was to alleviate the charge on users > and their customers. > >>>> > >>>> I'm not against letting them grab it. Maybe we could deliver an > init-gradle-wrapper script version which would do the work for them > >>>> > >>>> But again we would need to maintain it and it's benign to grab the > wrapper files and put them in OFBiz-root-dir/gradle/wrapper folder. > >>>> > >>>> Back to basic :) > >>>> > >>>> Jacques > >>>> > >>>> > >>> OK, if nobody is against, I'll revert all related changes in trunk > (including Nicolas's and Mathieu's) and Buildbot in 3 days, and will close > >>> OFBIZ-10145. > >>> > >>> No maintenance will be needed, all will be handled during the RM phase > as Jacopo initially suggested. > >>> > >>> We will need to keep only the "Manual setting" section (w/o its title) > in the main README.adoc. And to clearly document the RM phase. > >>> > >>> Thank you to all who discussed and provided ideas and code. > >>> > >>> Jacques > >>> > >> No problem to revert on trunk however I'm in favor to keep an > init-gradle-wrapper to help first discovery without complex preparation and > the > >> script maintenance is really easy. > >> > >> So we can have on documentation advisable part with install gradle from > official source and other part for unfamiliar people with quick start > >> through init-gradle-wrapper. > >> > >> After I'm always disturbed to have a different process to initialize > OFBiz between release branch and released package but I can live very well > >> with it. > >> > >> Nicolas > >> > >> > > This can even exist for Windows: +1 > > > > Jacques > > > > > Hi, > > At revision: 1862745 I have removed all changes done for OFBIZ-10145 < > https://issues.apache.org/jira/browse/OFBIZ-10145> so far. The wrapper > stays in > branches and trunk. Now all should be handled during the Release > Management phase. > > I'll soon tackle the documentation changes... > > Jacques > >
Re: Next step to migrate OFBiz from Subversion (SVN) to Git
Hello team, All the essential details are incorporated in this document [1] to help us in migrating from SVN to Git. Please have a look and let us know your kind thoughts. [1] https://cwiki.apache.org/confluence/x/Xg-HBg Best Regards, Swapnil M Mane, ofbiz.apache.org On Thu, May 9, 2019 at 9:26 AM Swapnil M Mane wrote: > Thank you Deepak for your comments, I am also inline with this. > The document [1] contains the information of switching version control > from SVN to Git (with existing contribution flow). > > > [1] https://cwiki.apache.org/confluence/x/Xg-HBg > > > - Best Regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Wed, May 8, 2019 at 12:22 PM Deepak Dixit > wrote: > >> Thanks you Swapnil for your effort, >> >> I agree with Mathieu, as a first step we have to focus on switching >> version control from svn to git (with existing contribution flow), >> once it has done we can discuss the contribution flow using GitHub >> feature. >> >> Kind Regards, >> Deepak Dixit >> DIRECTOR OF PRODUCT ENGINEERING >> mobile: +91 9826754548 >> email: deepak.di...@hotwax.co >> *www.hotwax.co <http://www.hotwax.co/>* >> >> >> On Wed, May 1, 2019 at 7:14 PM Swapnil M Mane >> wrote: >> >>> Hi team, >>> >>> Thanks so much everyone for participating in the discussion [1] to >>> migrate >>> OFBiz from Subversion (SVN) to Git version control system. >>> >>> As we have concluded to move our source repository from SVN to Git. >>> Based on our previous discussions [1], here is the document [2] which can >>> help us to strategies our migration. >>> >>> This document contain all the relevant topics which need to consider >>> before, during and after migration to Git. >>> >>>1. Code Repository >>>2. Workflow >>> 1. Small Features / Bug Fixes >>> 2. Large Features >>>3. Buildbot configuration with Git (Build Scripts) >>>4. Revert workflow >>> 1. Revert Pull Request >>> 2. Revert a commit >>>5. Backport the fixes >>>6. Release management >>>7. Equivalent of svn:auto-props properties >>>8. Update the website, wiki documents and references >>> >>> The workflow in document is suggested by Taher in thread [1], and based >>> on >>> my experience with Git, I have added respective the points in the above >>> sections. >>> >>> I have added some task in document which needs to done, confluence >>> provide >>> use feature to assign the task in the document itself. >>> Example, I have assigned two tasks to me under "Update the website, wiki >>> documents and references" section. We can use this feature distribute our >>> tasks. >>> >>> I request everyone to please have a look into this document and kindly >>> share your thoughts. >>> Also, feel free to update the document. >>> >>> >>> [1] >>> >>> https://lists.apache.org/thread.html/9f89b2a24ff427dffaf71294fc20306994fd1c19a6b24e64c4b06d71@1431423796@%3Cdev.ofbiz.apache.org%3E >>> [2] https://cwiki.apache.org/confluence/x/Xg-HBg >>> >>> >>> - Best Regards, >>> Swapnil M Mane, >>> ofbiz.apache.org >>> >>
Re: [DISCUSSION] where download gradle-wrapper.jar ?
Thanks, everyone for sharing your kind thoughts. I am also inclined towards allowing users to follow the standard Gradle installation process. We tried our best to make the user's life easier by avoiding their intervention in downloading respective Gradle (resulting the changes in gradlew and gradlew.bat files and writing init-gradle-wrapper script), but, it seems this will brings various complexities and maintenance issues to us like -- Upgrading the Gradle version -- Distribution of the wrapper jar So IMO, let's keep things simple and let the users follow standard Gradle installation. Best Regards, Swapnil M Mane, ofbiz.apache.org On Mon, Jul 1, 2019 at 1:52 PM Jacques Le Roux wrote: > Le 01/07/2019 à 06:53, Jacopo Cappellato a écrit : > > On Sun, Jun 30, 2019 at 5:31 PM Mathieu Lirzin < > mathieu.lir...@nereide.fr> > > wrote: > > > >> [...] > >> As a consequence, I would recommend keeping the wrapper jar in our VCS > >> repository, and simply remove it along side the “gradlew” scripts from > >> our release archives. We would then provide preliminary build > >> instructions stating the required version of Gradle and let users choose > >> how they want to install it [1]. > >> > >> [1] https://docs.gradle.org/current/userguide/installation.html > > > > I tend to agree with Mathieu. > > The above approach would also cover another concern I had with some of > the > > proposals: since release files can be downloaded by a potentially large > > number of users, they must be distributed thru the mirror network [*]; > > distributing the wrapper jar from our svn, git or website would not scale > > up well and could cause excessive load on these server. > > > > Jacopo > > > > [*] https://www.apache.org/dev/release-distribution > > After working on a Buildbot solution, I suggested this way because I > thought it would be easy for our users, and maybe our own tranquillity. > > I did not think about scaling. We speak about 55 Kb, the connexions would > be very short, so not much at the same time. > > It started from this Mark Thomas's remark in LEGAL-288: > > < so I don't think Infra would have any objections.>> > > Though with my last proposition, to allow imperceptible Gradle upgrade, > this download would be for each call to OFBiz gradlew anywhere. That's > indeed > something to consider. > > Nicolas suggested to get the wrapper from Git. That can be done, but needs > a solution when it disappears there. And it's maybe not fair to them. > > I agree, the easiest way for us is certainly to let users follow the > standard Gradle installation process as they do for Java. > > I'm not against that, just another step that we tried to avoid to our > users and their customers. > > For working copies checked out (including Buildbot and demos) we can keep > the wrapper where it is. > > Following LEGAL-288, that's what I initially described in OFBIZ-10145. It > was a nice tour :) > > Can we conclude? > > Jacques > > >
Re: Getting Started with Apache OFBiz Manufacturing in 5 Easy Steps
Thanks so much, Sharan for this valuable contribution, highly appreciated!! @Team, We are making slight changes (creating confluence document from PDF, updating the screenshots, etc.) in original PDF document to sync with the latest OFBiz release. Here is the initial version of improved document [1], currently in WIP, will be completed soon. (Thanks to Archana Asthana for participating in the effort of syncing the document with the latest release) [1] https://cwiki.apache.org/confluence/x/Pw3HBg - Best Regards, Swapnil M Mane, ofbiz.apache.org On Tue, Jun 25, 2019 at 2:34 AM Sharan Foga wrote: > Hi All > > I saw a note about the Getting Started with Apache OFBiz Manufacturing & > MRP in 5 Easy Steps tutorial document that I wrote a while ago that is > being added to the wiki as individual pages. The original pdf tutorial > document I contributed included a copyright notice which is probably why my > name was included in the title. > > Swapnil has already followed up with me and I am happy to release the > copyright for this tutorial document and fully contribute it back to under > ASL v2 so the project so the community is free to use, change or update it > as needed. > > Thanks > Sharan > >
Re: Welcome to Pawan Verma as new committer!
Many congratulations Pawan. Welcome aboard! - Best Regards, Swapnil M Mane, ofbiz.apache.org On Thu, Jun 13, 2019 at 11:20 AM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Pawan to become a new committer and we are > pleased to announce that he has accepted. > > Pawan is part of the community for 2 years and has being quite active and > proficient, notably these last times with several smart propositions. > > He also helps a lot of Jiras and answers properly on MLs. > > Please join me in welcoming and congratulating Pawan. > > Jacques > >
Re: Welcome to Deepak Nigam as new committer!
Many congratulations Deepak. Welcome aboard! - Best Regards, Swapnil M Mane, ofbiz.apache.org On Thu, Jun 13, 2019 at 11:20 AM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > The OFBiz PMC has invited Deepak to become a new committer and we are > pleased to announce that he has accepted. > > Deepak is part of the community since January 2016 and has proved to be > committed since. > > He notably made a great work for OFBIZ-10518 "Inventory (Supply) > Allocation Planning " > > He not only worked in Jira, but also answered accurately on MLs where he > supported our users. > > Please join me in welcoming and congratulating Deepak. > > Jacques > >
Re: Improve steps on Mailing Lists page
+1, thanks Aditya. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Wed, Jun 5, 2019 at 10:49 AM Aditya Sharma wrote: > Hello everyone, > > The current steps for subscribing on Mailing lists page[1]: > 1. Click the button of the mailing list you want to subscribe to > 2. On the following page, click the 'Subscribe' button > 3. Send the automatically created email from your email client > 4. You will receive an email about the mailing list manager program (EZMLM) > Congratulations! You are now subscribed > > The issue with current steps is on list page[2] when user clicks subscribe > button it opens up the email client but it is not necessary that user uses > any email client. I think we should also add direct steps as available for > unsubscribing. > > To subscribe from any of the following lists, please send an empty, > subjectless email to mailing list subscribe addresses. > >- user-subscr...@ofbiz.apache.org >- dev-subscr...@ofbiz.apache.org >- commits-subscr...@ofbiz.apache.org >- notifications-subscr...@ofbiz.apache.org > > 1. https://ofbiz.apache.org/mailing-lists.html > 2. https://lists.apache.org/list.html?u...@ofbiz.apache.org > > Thanks and Regards > Aditya Sharma >
Fwd: Apache Roadshow India in 2020?
Hello Devs, Just for your information, we are exploring the possibility of Apache Roadshow India in 2020 [1]. (If roadshow planned, definitely, there will be the OFBiz track :) If you and interested and want to give feedback or help with planning, please subscribe to d...@community.apache.org and provide feedback there. [1] https://s.apache.org/BJTl - Best Regards, Swapnil M Mane, ofbiz.apache.org -- Forwarded message - From: Sharan Foga Date: Sun, Jun 2, 2019 at 2:52 PM Subject: Apache Roadshow India in 2020? To: Hi All With all the suggestions coming up for locations for potential Roadshows, the idea of doing a Roadshow in India has been raised again. The suggested timeframe is Q1 2020 as the weather is good (not too hot, not too cold) also not too many other conferences are happening around that time. The potential location is Gurgaon / Gurugram which has good transport links and seems to be a tech hub. I am working with Swapnil ,who is active on this list and few others I know from OFBiz who are based in India who have offered to help with the organisation and management. We are currently working to put together a proposal. So as part of an initial step I would like to gauge the feedback from our community. What do people think? (And also is anyone interested in helping out ?) Thanks Sharan - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: buildbot failure in on ofbizBranch18Framework
Hello team, I confirm, the build failure is not related to rev #1860275 - Best Regards, Swapnil M Mane, ofbiz.apache.org On Tue, May 28, 2019 at 8:15 PM wrote: > The Buildbot has detected a new failure on builder ofbizBranch18Framework > while building . Full details are available at: > https://ci.apache.org/builders/ofbizBranch18Framework/builds/139 > > Buildbot URL: https://ci.apache.org/ > > Buildslave for this Build: lares_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named > 'onBranch18FrameworkCommit' triggered this build > Build Source Stamp: [branch ofbiz/ofbiz-framework/branches/release18.12] > 1860275 > Blamelist: swapnilmmane > > BUILD FAILED: failed shell_2 > > Sincerely, > -The Buildbot > > > >
Re: Fresh Install
Hi Craig, This issue could be related to your JDK version. Can you please share the details on which OFBiz and Java version you are using? Also, please refer to this mail thread [1], this might help you. [1] https://markmail.org/thread/iuxnioqiijhrkukp - Best Regards, Swapnil M Mane, ofbiz.apache.org On Tue, May 28, 2019 at 2:19 AM Craig Parker wrote: > I've left directions for myself to get OFBiz up and running on an Ubuntu > machine, but I'm missing something. ./gradlew ofbiz is giving me no > output, but isn't starting up either. I can't remember where I saw > documentation for showing different output. > > > >
Re: Reviving the OFBiz community day
Thanks so much Sharan for your kind help :-) I have created sprint - "OFBiz Community Day (May 2019)" and associated it with an issue for testing purpose. Everything is working as expected. P.S. To set the sprint on any issue, simply click on the "Edit" option on the issue and select the sprint field. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Fri, May 17, 2019 at 2:07 AM Sharan Foga wrote: > Hi All > > One of things we did for the community days is to use Jira Sprints to > identify the issues to work on. As Swapnil is co-ordinating this effort - > I've added him to the Jira admins so that he can create sprints. I have > just created a scrum board that we can use. > > Please feel to try it and if it doesn't work well for the community days > then we can delete the board, sprints etc and try something else. > > Thanks > Sharan > > On 2019/05/15 11:21:22, Swapnil M Mane wrote: > > Thanks team! > > I will post the detailed information about upcoming community day on the > > user mailing list. > > > > > > - Best Regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > On Fri, May 10, 2019 at 12:33 PM Devanshu Vyas < > vyas.devansh...@gmail.com> > > wrote: > > > > > Great initiative and love to be a part of it. +1 > > > > > > > > > Thanks & Regards, > > > Devanshu Vyas. > > > > > > > > > On Thu, May 9, 2019 at 4:05 PM Swapnil M Mane > > > > wrote: > > > > > > > Thanks so much everyone for your comments. > > > > > > > > The community days are organized once per quarter so a total of four > (4) > > > > events throughout the year. Since we skipped the February 2019 month. > > > Here > > > > are the proposed dates for this year's community day. > > > > Contributors can select any single day based on there availability > and > > > > preferences. > > > > > > > > > > > >- Q1 - Community Days *February 2019* - N/A > > > > > > > > > > > >- Q2 - Community Days *May 2019* are *Friday 24th, Saturday 25th, > > > Sunday > > > >26th, Monday 27th and Tuesday 28th* > > > > > > > > > > > >- Q3 - Community Days *August 2019* are *Friday 23rd, Saturday > 24th, > > > >Sunday 25th, Monday 26th and Tuesday 27th* > > > > > > > > > > > >- Q4 - Community Days* November 2019 *are *Friday 22nd, Saturday > 23rd, > > > >Sunday 24th, Monday 25th and Tuesday 26nd* > > > > > > > > > > > > If we are fine these days, I will share the *detailed* updates on > user's > > > > mailing list. > > > > > > > > > > > > - Thanks & Regards, > > > > Swapnil M Mane, > > > > ofbiz.apache.org > > > > > > > > > > > > > > > > On Fri, Apr 26, 2019 at 2:06 PM Nicolas Malin < > nicolas.ma...@nereide.fr> > > > > wrote: > > > > > > > > > I follow you on this way :) > > > > > > > > > > On 26/04/2019 09:09, Sanjay Yadav wrote: > > > > > > Nice initiative, Swapnil. I am in for community day. > > > > > > > > > > > > Best Regards, > > > > > > > > > > > > *Sanjay Yadav* | Manager, QA > > > > > > HotWax Systems <http://www.hotwaxsystems.com/> > > > > > > 80, Scheme No. 78, Indore, M.P. 452010, India > > > > > > Mobile Phone: 787 918 8830 | Linkedin: Sanjay-Yadav > > > > > > <https://www.linkedin.com/in/sanjay-yadav/> > > > > > > > > > > > > > > > > > > On Thu, Apr 25, 2019 at 10:54 AM Swapnil M Mane < > > > > swapnilmm...@apache.org > > > > > > > > > > > > wrote: > > > > > > > > > > > >> Hello team, > > > > > >> We are having a great community, I would like to thank everyone > for > > > > > their > > > > > >> participation. > > > > > >> > > > > > >> In year 2017, we start celebrating the OFBiz community days [1]. > > > > > >> The contribution during community days played very significant > role > > > in > > > > > >> improvement of framework. > > > > > >> Should we start this celebration again, thought? > > > > > >> > > > > > >> > > > > > >> [1] > > > > > > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days > > > > > >> > > > > > >> > > > > > >> - Best Regards, > > > > > >> Swapnil M Mane, > > > > > >> ofbiz.apache.org > > > > > >> > > > > > > > > > > > > > > >
Re: Reviving the OFBiz community day
Thanks team! I will post the detailed information about upcoming community day on the user mailing list. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Fri, May 10, 2019 at 12:33 PM Devanshu Vyas wrote: > Great initiative and love to be a part of it. +1 > > > Thanks & Regards, > Devanshu Vyas. > > > On Thu, May 9, 2019 at 4:05 PM Swapnil M Mane > wrote: > > > Thanks so much everyone for your comments. > > > > The community days are organized once per quarter so a total of four (4) > > events throughout the year. Since we skipped the February 2019 month. > Here > > are the proposed dates for this year's community day. > > Contributors can select any single day based on there availability and > > preferences. > > > > > >- Q1 - Community Days *February 2019* - N/A > > > > > >- Q2 - Community Days *May 2019* are *Friday 24th, Saturday 25th, > Sunday > >26th, Monday 27th and Tuesday 28th* > > > > > >- Q3 - Community Days *August 2019* are *Friday 23rd, Saturday 24th, > >Sunday 25th, Monday 26th and Tuesday 27th* > > > > > >- Q4 - Community Days* November 2019 *are *Friday 22nd, Saturday 23rd, > >Sunday 24th, Monday 25th and Tuesday 26nd* > > > > > > If we are fine these days, I will share the *detailed* updates on user's > > mailing list. > > > > > > - Thanks & Regards, > > Swapnil M Mane, > > ofbiz.apache.org > > > > > > > > On Fri, Apr 26, 2019 at 2:06 PM Nicolas Malin > > wrote: > > > > > I follow you on this way :) > > > > > > On 26/04/2019 09:09, Sanjay Yadav wrote: > > > > Nice initiative, Swapnil. I am in for community day. > > > > > > > > Best Regards, > > > > > > > > *Sanjay Yadav* | Manager, QA > > > > HotWax Systems <http://www.hotwaxsystems.com/> > > > > 80, Scheme No. 78, Indore, M.P. 452010, India > > > > Mobile Phone: 787 918 8830 | Linkedin: Sanjay-Yadav > > > > <https://www.linkedin.com/in/sanjay-yadav/> > > > > > > > > > > > > On Thu, Apr 25, 2019 at 10:54 AM Swapnil M Mane < > > swapnilmm...@apache.org > > > > > > > > wrote: > > > > > > > >> Hello team, > > > >> We are having a great community, I would like to thank everyone for > > > their > > > >> participation. > > > >> > > > >> In year 2017, we start celebrating the OFBiz community days [1]. > > > >> The contribution during community days played very significant role > in > > > >> improvement of framework. > > > >> Should we start this celebration again, thought? > > > >> > > > >> > > > >> [1] > > > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days > > > >> > > > >> > > > >> - Best Regards, > > > >> Swapnil M Mane, > > > >> ofbiz.apache.org > > > >> > > > > > >
Re: Reviving the OFBiz community day
Thanks so much everyone for your comments. The community days are organized once per quarter so a total of four (4) events throughout the year. Since we skipped the February 2019 month. Here are the proposed dates for this year's community day. Contributors can select any single day based on there availability and preferences. - Q1 - Community Days *February 2019* - N/A - Q2 - Community Days *May 2019* are *Friday 24th, Saturday 25th, Sunday 26th, Monday 27th and Tuesday 28th* - Q3 - Community Days *August 2019* are *Friday 23rd, Saturday 24th, Sunday 25th, Monday 26th and Tuesday 27th* - Q4 - Community Days* November 2019 *are *Friday 22nd, Saturday 23rd, Sunday 24th, Monday 25th and Tuesday 26nd* If we are fine these days, I will share the *detailed* updates on user's mailing list. - Thanks & Regards, Swapnil M Mane, ofbiz.apache.org On Fri, Apr 26, 2019 at 2:06 PM Nicolas Malin wrote: > I follow you on this way :) > > On 26/04/2019 09:09, Sanjay Yadav wrote: > > Nice initiative, Swapnil. I am in for community day. > > > > Best Regards, > > > > *Sanjay Yadav* | Manager, QA > > HotWax Systems <http://www.hotwaxsystems.com/> > > 80, Scheme No. 78, Indore, M.P. 452010, India > > Mobile Phone: 787 918 8830 | Linkedin: Sanjay-Yadav > > <https://www.linkedin.com/in/sanjay-yadav/> > > > > > > On Thu, Apr 25, 2019 at 10:54 AM Swapnil M Mane > > > wrote: > > > >> Hello team, > >> We are having a great community, I would like to thank everyone for > their > >> participation. > >> > >> In year 2017, we start celebrating the OFBiz community days [1]. > >> The contribution during community days played very significant role in > >> improvement of framework. > >> Should we start this celebration again, thought? > >> > >> > >> [1] > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days > >> > >> > >> - Best Regards, > >> Swapnil M Mane, > >> ofbiz.apache.org > >> >
Re: Next step to migrate OFBiz from Subversion (SVN) to Git
Thank you Deepak for your comments, I am also inline with this. The document [1] contains the information of switching version control from SVN to Git (with existing contribution flow). [1] https://cwiki.apache.org/confluence/x/Xg-HBg - Best Regards, Swapnil M Mane, ofbiz.apache.org On Wed, May 8, 2019 at 12:22 PM Deepak Dixit wrote: > Thanks you Swapnil for your effort, > > I agree with Mathieu, as a first step we have to focus on switching > version control from svn to git (with existing contribution flow), > once it has done we can discuss the contribution flow using GitHub > feature. > > Kind Regards, > Deepak Dixit > DIRECTOR OF PRODUCT ENGINEERING > mobile: +91 9826754548 > email: deepak.di...@hotwax.co > *www.hotwax.co <http://www.hotwax.co/>* > > > On Wed, May 1, 2019 at 7:14 PM Swapnil M Mane > wrote: > >> Hi team, >> >> Thanks so much everyone for participating in the discussion [1] to migrate >> OFBiz from Subversion (SVN) to Git version control system. >> >> As we have concluded to move our source repository from SVN to Git. >> Based on our previous discussions [1], here is the document [2] which can >> help us to strategies our migration. >> >> This document contain all the relevant topics which need to consider >> before, during and after migration to Git. >> >>1. Code Repository >>2. Workflow >> 1. Small Features / Bug Fixes >> 2. Large Features >>3. Buildbot configuration with Git (Build Scripts) >>4. Revert workflow >> 1. Revert Pull Request >> 2. Revert a commit >>5. Backport the fixes >>6. Release management >>7. Equivalent of svn:auto-props properties >>8. Update the website, wiki documents and references >> >> The workflow in document is suggested by Taher in thread [1], and based on >> my experience with Git, I have added respective the points in the above >> sections. >> >> I have added some task in document which needs to done, confluence provide >> use feature to assign the task in the document itself. >> Example, I have assigned two tasks to me under "Update the website, wiki >> documents and references" section. We can use this feature distribute our >> tasks. >> >> I request everyone to please have a look into this document and kindly >> share your thoughts. >> Also, feel free to update the document. >> >> >> [1] >> >> https://lists.apache.org/thread.html/9f89b2a24ff427dffaf71294fc20306994fd1c19a6b24e64c4b06d71@1431423796@%3Cdev.ofbiz.apache.org%3E >> [2] https://cwiki.apache.org/confluence/x/Xg-HBg >> >> >> - Best Regards, >> Swapnil M Mane, >> ofbiz.apache.org >> >
Re: Security alerts on monthly blog entries?
+1 - Best Regards, Swapnil M Mane, ofbiz.apache.org On Thu, May 2, 2019 at 8:09 PM Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > +1 > > Jacopo > > On Thu, May 2, 2019 at 4:18 PM Jacques Le Roux < > jacques.le.r...@les7arts.com> > wrote: > > > Hi, > > > > I was wondering: would it not be good to use the blog to alert about > > resolved security issues (both w/ and w/o CVE) when it applies? > > > > Jacques > > > > >
Re: Adding Apache License link in main navigation (footer) of OFBiz site
Changes are pushed at rev #1858515 and #1858519 in ofbiz-site. Now all the Whimsy site checks [1] are passed. [1] https://whimsy.apache.org/site/project/ofbiz - Thanks & Regards, Swapnil M Mane, ofbiz.apache.org On Wed, Apr 24, 2019 at 2:41 PM Swapnil M Mane wrote: > Sure Deepak, thank you for the comment. > > > - Best Regards, > Swapnil M Mane, > ofbiz.apache.org > > > > On Wed, Apr 24, 2019 at 11:49 AM Deepak Dixit > wrote: > >> Hi Swapnil, >> >> I think we should use the following link as licenses >> https://www.apache.org/licenses/LICENSE-2.0 >> >> Kind Regards, >> Deepak Dixit >> >> >> On Wed, Apr 24, 2019 at 10:52 AM Swapnil M Mane >> wrote: >> >> > Hello team, >> > >> > Whimsy site check [1] showing the fail result in 'License' check type >> for >> > OFBiz site [2]. >> > >> > It is showing message - >> > "URL expected to match regular expression: ^https?://.* >> > apache.org/licenses/?$" >> > >> > But we already have a link of license [3] in the footer of OFBiz site >> with >> > text Licensed under the Apache License, Version 2.0. >> > >> > Thus I communicate with Whimy team and here is the response from them, >> > >> > === >> > There are no standard navigation links: >> > >> > https://www.apache.org/foundation/marks/pmcs#navigation >> > === >> > >> > Reference from link above >> > >> > > These links can appear in whatever main navigation system your site >> uses >> > > on all top level pages for the project or subproject. >> > >> > >> > So, I think, we should add License link in the "ASF Information" >> section, >> > defined in the *footer* of OFBiz site [2]. >> > Please let me know your thoughts on this. >> > >> > >> > [1] https://whimsy.apache.org/site/project/ofbiz >> > [2] https://ofbiz.apache.org/ >> > [3] https://www.apache.org/licenses/ >> > >> > >> > - Best Regards, >> > Swapnil M Mane, >> > ofbiz.apache.org >> > >> >
Re: Next step to migrate OFBiz from Subversion (SVN) to Git
Dear Mathieu, You are 200% correct, please accept my kind apologies for this. I have update the document [1] with appropriate information. Thanks so much for correcting me. [1] https://cwiki.apache.org/confluence/x/Xg-HBg - Best Regards, Swapnil M Mane, ofbiz.apache.org On Wed, May 1, 2019 at 8:54 PM Mathieu Lirzin wrote: > Hello Swapnil, > > Swapnil M Mane writes: > > > As we have concluded to move our source repository from SVN to Git. > > Based on our previous discussions [1], here is the document [2] which can > > help us to strategies our migration. > > > > This document contain all the relevant topics which need to consider > > before, during and after migration to Git. > > > I request everyone to please have a look into this document and kindly > > share your thoughts. > > Also, feel free to update the document. > > I appreciate your writing effort, however I think your writing tends to > mix Git and Github workflows which are two separate things. > > As far as I understand it, we agreed to change our version control > system to use Git not to change our contribution workflow to use Github. > Contributions will continue to be done via JIRA, patches and the ML, as > long as we don't discuss and vote for that. > > Personnally I will be against using Github social features (issues, > pull-request, wiki, ...) in our contribution process. > > Thanks. > > -- > Mathieu Lirzin > GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37 >
Next step to migrate OFBiz from Subversion (SVN) to Git
Hi team, Thanks so much everyone for participating in the discussion [1] to migrate OFBiz from Subversion (SVN) to Git version control system. As we have concluded to move our source repository from SVN to Git. Based on our previous discussions [1], here is the document [2] which can help us to strategies our migration. This document contain all the relevant topics which need to consider before, during and after migration to Git. 1. Code Repository 2. Workflow 1. Small Features / Bug Fixes 2. Large Features 3. Buildbot configuration with Git (Build Scripts) 4. Revert workflow 1. Revert Pull Request 2. Revert a commit 5. Backport the fixes 6. Release management 7. Equivalent of svn:auto-props properties 8. Update the website, wiki documents and references The workflow in document is suggested by Taher in thread [1], and based on my experience with Git, I have added respective the points in the above sections. I have added some task in document which needs to done, confluence provide use feature to assign the task in the document itself. Example, I have assigned two tasks to me under "Update the website, wiki documents and references" section. We can use this feature distribute our tasks. I request everyone to please have a look into this document and kindly share your thoughts. Also, feel free to update the document. [1] https://lists.apache.org/thread.html/9f89b2a24ff427dffaf71294fc20306994fd1c19a6b24e64c4b06d71@1431423796@%3Cdev.ofbiz.apache.org%3E [2] https://cwiki.apache.org/confluence/x/Xg-HBg - Best Regards, Swapnil M Mane, ofbiz.apache.org
Re: buildbot failure in on ofbizBranch16
Hi team, All the tests are passed on my local. The commit 1858322 [1] should not be responsible for buildbot failure. [1] https://github.com/apache/ofbiz/commit/e29cf094893c1abb160f5ebac2d09f62d2290ef9 - Best Regards, Swapnil M Mane, ofbiz.apache.org On Sun, Apr 28, 2019 at 7:25 PM wrote: > The Buildbot has detected a new failure on builder ofbizBranch16 while > building . Full details are available at: > https://ci.apache.org/builders/ofbizBranch16/builds/191 > > Buildbot URL: https://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named 'onOfbizR16Commit' > triggered this build > Build Source Stamp: [branch ofbiz/branches/release16.11] 1858322 > Blamelist: swapnilmmane > > BUILD FAILED: failed shell_2 > > Sincerely, > -The Buildbot > > > >
Re: Manufacturer Support In Promotion Engine
Hi Rishi, This seems good addition to me in promotion engine, +1. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Sat, Apr 27, 2019 at 6:32 PM Rishi Solanki wrote: > Devs, > Currently promotion engine support all the discount based on party, > category, party role, party classification, shipping etc.. And promotion > engine based on the condition decide that the promotion will apply for > customer purchase over the cart or cart item depending upon the action. > > I would like to propose to add support in promotion engine, so that , we > can add promotion against manufacturing party and should apply to all the > products manufactured by that party. > > For example; > M1, M2 are two manufacturers. > M1P1 and M1P2 are products manufactured by M1. > M2P1 and M2P2 are products manufactured by M2. > > Now M1 gives 10% discount on all products M1, and if customer purchase all > products with quantity ONE. > > Assuming all items price is $100. Then CartTotal will be $400 and discount > amount will be $20. As discount is on M1 products only. > > Best Regards, > -- > *Rishi Solanki* | Sr Manager, Enterprise Software Development > HotWax Systems <http://www.hotwaxsystems.com/> > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, > Indore, > M.P 452010 > Linkedin: *Rishi Solanki* > <https://www.linkedin.com/in/rishi-solanki-62271b7/> > Direct: +91-9893287847 >
Re: ReturnContactMech is not used
+1 - Best Regards, Swapnil M Mane, ofbiz.apache.org On Sat, Apr 27, 2019 at 12:33 PM Vaibhav Jain < vaibhav.j...@hotwaxsystems.com> wrote: > *Bottom line:* > ReturnContactMech entity is not used in OFBiz > > *Story:* > ContactMech of parties involved in an order is captured in OrderContactMech > entity. > ContactMech of parties involved in the return is not captured in > ReturnContactMech entity. > > Kind Regards, > *Vaibhav Jain* | Senior Enterprise Software Engineer > HotWax Systems <http://www.hotwaxsystems.com/> > Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, > Indore, > M.P 452010 > Linkedin: *Vaibhav Jain* <https://www.linkedin.com/in/vaibhav-jain-170793/ > > > > [image: Mailtrack] > < > https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&; > > > Sender > notified by > Mailtrack > < > https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&; > > > 04/27/19, > 12:23:48 PM >
Re: [DISCUSSION] JIRA notifications and reaching contributors
I am also inline with Michael's comments. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Thu, Apr 25, 2019 at 4:48 PM Michael Brohl wrote: > I strongly suggest to stay with the split between notifications@ and dev@. > > It makes the dev@ discussions a lot better to follow, these would drown > in the Jira notifications. I suspect that we would make users > unsubscribe dev@ if we would have notifications@ in there also. > > If people are interested in getting the notifications, they can > subscribe anytime. It might be reasonable to encourage people in the > dev@/user@ lists to subscribe there if we believe they are not aware of > the notifications@ list. > > Regards, > > Michael Brohl > > ecomify GmbH - www.ecomify.de > > > Am 25.04.19 um 12:20 schrieb Pierre Smits: > > Hi All, > > > > Back in 2016 it was decided that notifications go to the separate mailing > > list notifications@ofbiz.a.o. See [1]. And looking at latest numbers > > reported regarding subscriptions to our mailing lists, we have: > > > > - user@: 926 > > - dev@: 574 > > - commits@: 218 > > - notifications@: 78 > > > > The numbers regarding user@, dev@ and notifications@ are from > 2018-06-20, > > and the number regarding notifications@ is from 2018-03-20, see [2]. > > > > The numbers indicate that about 14% of our contributor potential > subscribed > > to the dev@ sees these notifications about bugs and improvements, and > less > > than 9% of our greater community (subscribed to user@) are reached. > And > > when we factor in the impact of PMC members and committers (I can only > > guess how many of those have subscribed) on notifications@) the ratios > are > > even worse. > > > > The effect of the low number of subscriptions to notifications@ is that > we > > don't reach our potential and that we don't see the input of dev@ and > user@ > > subscribers, leading to an overload of those working tickets. > > > > Did we take a wrong turn back in 2016? And should we not revert the > > resolution of the vote to have notifications go back to dev@ to get more > > contributions (potentially leading to more - active - committers that > share > > and lessen the work load? > > > > What do you think? > > > > > > [1] [VOTE] Create a "notifications" mailing list > > < > https://ofbiz.markmail.org/message/6hlbap7a6cam3rm2?q=%22%5BVOTE%5D+Create+a+%22notifications%22+mailing+list+%22+list:org%2Eapache%2Eofbiz%2Edev+order:date-forward > > > > > > > > > > Best regards, > > > > Pierre Smits > > > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > > *Apache Directory <https://directory.apache.org>, PMC Member* > > Apache Incubator <https://incubator.apache.org>, committer > > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without > privileges) > > since 2008* > > Apache Steve <https://steve.apache.org>, committer > > > >
Re: Reviving the OFBiz community day
Wow, thoughts travels Pierre! I am also working a document for migration of OFBiz from SVN to Git. It is at very beginning state, hopefully will share it by this end of week. :) - Best Regards, Swapnil M Mane, ofbiz.apache.org On Thu, Apr 25, 2019 at 2:19 PM Pierre Smits wrote: > Great initiative. > > Would love to see such event to help moving the git issue forward. See [1] > > [1] git commit workflow for ofbiz > < > https://ofbiz.markmail.org/message/iojtu6abffow2p43?q=%22git+commit+workflow+for+ofbiz%22+list:org%2Eapache%2Eofbiz%2Edev+order:date-forward > > > > Best regards, > > Pierre Smits > > *Apache Trafodion <https://trafodion.apache.org>, Vice President* > *Apache Directory <https://directory.apache.org>, PMC Member* > Apache Incubator <https://incubator.apache.org>, committer > *Apache OFBiz <https://ofbiz.apache.org>, contributor (without privileges) > since 2008* > Apache Steve <https://steve.apache.org>, committer > > > On Thu, Apr 25, 2019 at 7:24 AM Swapnil M Mane > wrote: > > > Hello team, > > We are having a great community, I would like to thank everyone for their > > participation. > > > > In year 2017, we start celebrating the OFBiz community days [1]. > > The contribution during community days played very significant role in > > improvement of framework. > > Should we start this celebration again, thought? > > > > > > [1] > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days > > > > > > - Best Regards, > > Swapnil M Mane, > > ofbiz.apache.org > > >
Reviving the OFBiz community day
Hello team, We are having a great community, I would like to thank everyone for their participation. In year 2017, we start celebrating the OFBiz community days [1]. The contribution during community days played very significant role in improvement of framework. Should we start this celebration again, thought? [1] https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days - Best Regards, Swapnil M Mane, ofbiz.apache.org
Re: Adding Apache License link in main navigation (footer) of OFBiz site
Sure Deepak, thank you for the comment. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Wed, Apr 24, 2019 at 11:49 AM Deepak Dixit wrote: > Hi Swapnil, > > I think we should use the following link as licenses > https://www.apache.org/licenses/LICENSE-2.0 > > Kind Regards, > Deepak Dixit > > > On Wed, Apr 24, 2019 at 10:52 AM Swapnil M Mane > wrote: > > > Hello team, > > > > Whimsy site check [1] showing the fail result in 'License' check type for > > OFBiz site [2]. > > > > It is showing message - > > "URL expected to match regular expression: ^https?://.* > > apache.org/licenses/?$" > > > > But we already have a link of license [3] in the footer of OFBiz site > with > > text Licensed under the Apache License, Version 2.0. > > > > Thus I communicate with Whimy team and here is the response from them, > > > > === > > There are no standard navigation links: > > > > https://www.apache.org/foundation/marks/pmcs#navigation > > === > > > > Reference from link above > > > > > These links can appear in whatever main navigation system your site > uses > > > on all top level pages for the project or subproject. > > > > > > So, I think, we should add License link in the "ASF Information" section, > > defined in the *footer* of OFBiz site [2]. > > Please let me know your thoughts on this. > > > > > > [1] https://whimsy.apache.org/site/project/ofbiz > > [2] https://ofbiz.apache.org/ > > [3] https://www.apache.org/licenses/ > > > > > > - Best Regards, > > Swapnil M Mane, > > ofbiz.apache.org > > >
Adding Apache License link in main navigation (footer) of OFBiz site
Hello team, Whimsy site check [1] showing the fail result in 'License' check type for OFBiz site [2]. It is showing message - "URL expected to match regular expression: ^https?://.* apache.org/licenses/?$" But we already have a link of license [3] in the footer of OFBiz site with text Licensed under the Apache License, Version 2.0. Thus I communicate with Whimy team and here is the response from them, === There are no standard navigation links: https://www.apache.org/foundation/marks/pmcs#navigation === Reference from link above > These links can appear in whatever main navigation system your site uses > on all top level pages for the project or subproject. So, I think, we should add License link in the "ASF Information" section, defined in the *footer* of OFBiz site [2]. Please let me know your thoughts on this. [1] https://whimsy.apache.org/site/project/ofbiz [2] https://ofbiz.apache.org/ [3] https://www.apache.org/licenses/ - Best Regards, Swapnil M Mane, ofbiz.apache.org
Re: ***UNCHECKED*** Marital Status not managed properly in Person entity
+1 - Best Regards, Swapnil M Mane, ofbiz.apache.org On Tue, Apr 9, 2019 at 12:51 PM Suraj Khurana wrote: > Hello, > > Currently, *maritalStatus* is managed as an indicator (Y/N) in *Person* > entity. I think we can enhance it and make it derived from *Enumeration* > pattern. > > *Classification of legal marital status* > >- 1 - Married (and not separated) ... >- 2 - Widowed (including living common law) ... >- 3 - Separated (and not Divorced) ... >- 4 - Divorced (including living common law) ... >- 5 - Single (including living common law) > > Please share your thoughts. > > -- > Best regards, > Suraj Khurana > TECHNICAL CONSULTANT > mobile: +91 9669750002 > email: suraj.khur...@hotwax.co > *www.hotwax.co <http://www.hotwax.co/>* >
Re: buildbot failure in on ofbizTrunkFramework
I confirm it is not related to the commit at rev #1856598. Maybe it is due to any previous changes. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Sat, Mar 30, 2019 at 11:23 AM wrote: > The Buildbot has detected a new failure on builder ofbizTrunkFramework > while building . Full details are available at: > https://ci.apache.org/builders/ofbizTrunkFramework/builds/731 > > Buildbot URL: https://ci.apache.org/ > > Buildslave for this Build: silvanus_ubuntu > > Build Reason: The AnyBranchScheduler scheduler named > 'onTrunkFrameworkCommit' triggered this build > Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1856598 > Blamelist: swapnilmmane > > BUILD FAILED: failed shell_2 > > Sincerely, > -The Buildbot > > > >
Re: Strong dependency of OFBiz build on JCenter
Thank you so much Jacopo, Taher, Nicolas for your kind inputs. +1 for adding more repositories (maven seems good to me). - Best Regards, Swapnil M Mane, www.hotwax.co On Sat, Mar 23, 2019 at 9:34 PM Taher Alkhateeb wrote: > Ahh I get it now. > > In that case the challenge might be making sure the naming and transitive > dependencies are equivalent on both sides. > > Maybe another solution is to create two files, one for maven and the other > for jcenter each with its own unique set of dependencies that can be tested > and ensured correct behavior. This way differences in names or transitive > dependencies are not an issue. > > On Sat, Mar 23, 2019, 5:09 PM Jacopo Cappellato < > jacopo.cappell...@hotwaxsystems.com> wrote: > > > Just to clarify, I was suggesting that we could add more repositories, > not > > replace Jcenter with another one: the redundancy would mitigate the risk > of > > unavailability. > > > > Jacopo > > > > On Fri, Mar 22, 2019 at 6:07 PM Taher Alkhateeb < > > slidingfilame...@gmail.com> > > wrote: > > > > > Whatever repository you choose, there is always the risk of going down. > > > > > > To mitigate this risk, you can (after deploying the system) use the - > > > -offline flag when running gradle. Alternatively you can simply run the > > > java - jar command. > > > > > > On Fri, Mar 22, 2019, 10:41 AM Swapnil M Mane < > > > swapnil.m...@hotwaxsystems.com> wrote: > > > > > > > Hello team, > > > > > > > > Yesterday JCenter was down for some time, due to which I was unable > to > > > > start the OFBiz server (because the build was failed). > > > > Status of JCenter can be found at [1]. > > > > > > > > This is a severe issue because it may be possible during any > production > > > > deployment, JCenter is down. Do we have any solution for the issue? > > > > Please let me know if I am missing anything. > > > > > > > > [1] https://status.bintray.com/ > > > > > > > > Here is stacktrace of build failure. > > > > == > > > > *> Task :compileTestJava* FAILED > > > > > > > > FAILURE: Build failed with an exception. > > > > > > > > * What went wrong: > > > > Execution failed for task ':compileTestJava'. > > > > > Could not resolve all files for configuration > > ':testCompileClasspath'. > > > >> Could not resolve org.mockito:mockito-core:2.+. > > > > Required by: > > > > project : > > > > > Failed to list versions for org.mockito:mockito-core. > > > > > Unable to load Maven meta-data from > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > . > > > > > Could not HEAD ' > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > '. > > > >> jcenter.bintray.com > > > > > Failed to list versions for org.mockito:mockito-core. > > > > > Unable to load Maven meta-data from > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > . > > > > > Could not HEAD ' > > > > > > https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml > > > > < > > > > > > > > > > https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg > > > > > > > > > '. > > > >> jcenter.bintray.com > > > > > > > > * Try: > > > > Run with *--stacktrace* option to get the stack trace. Run with > > *--info* > > > or > > > > *--debug* option to get more log output. Run with *--scan* to get > full > > > > insights. > > > > > > > > * Get more help at *https://help.gradle.org > > > > < > > > > > > > > > > https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q > > > > >* > > > > > > > > *BUILD FAILED* in 1m 14s > > > > == > > > > > > > > - Best Regards, > > > > Swapnil M Mane, > > > > www.hotwax.co > > > > > > > > > >
Strong dependency of OFBiz build on JCenter
Hello team, Yesterday JCenter was down for some time, due to which I was unable to start the OFBiz server (because the build was failed). Status of JCenter can be found at [1]. This is a severe issue because it may be possible during any production deployment, JCenter is down. Do we have any solution for the issue? Please let me know if I am missing anything. [1] https://status.bintray.com/ Here is stacktrace of build failure. == *> Task :compileTestJava* FAILED FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':compileTestJava'. > Could not resolve all files for configuration ':testCompileClasspath'. > Could not resolve org.mockito:mockito-core:2.+. Required by: project : > Failed to list versions for org.mockito:mockito-core. > Unable to load Maven meta-data from https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> . > Could not HEAD ' https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> '. > jcenter.bintray.com > Failed to list versions for org.mockito:mockito-core. > Unable to load Maven meta-data from https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> . > Could not HEAD ' https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml <https://www.google.com/url?q=https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNG-BdHXv5XipPli0zc2Lzk033SwEg> '. > jcenter.bintray.com * Try: Run with *--stacktrace* option to get the stack trace. Run with *--info* or *--debug* option to get more log output. Run with *--scan* to get full insights. * Get more help at *https://help.gradle.org <https://www.google.com/url?q=https://help.gradle.org&sa=D&source=hangouts&ust=1553323118761000&usg=AFQjCNF7cVissA1Dr2SsZDCnovsUYDUE7Q>* *BUILD FAILED* in 1m 14s == - Best Regards, Swapnil M Mane, www.hotwax.co
Re: svn commit: r1855403 - /ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
Done with the suggested changes Scott.
trunk at rev 1855898
release18.12 at rev 1855899
release17.12 at rev 1855900
release16.11 at rev 1855901
Thanks again for valuable inputs.
- Best Regards,
Swapnil M Mane,
ofbiz.apache.org
On Fri, Mar 15, 2019 at 9:52 AM Swapnil M Mane
wrote:
> Makes perfect sense, thanks so much for the input Scott.
> I will do the suggested changes.
>
>
> - Best Regards,
> Swapnil M Mane,
> ofbiz.apache.org
>
>
>
> On Fri, Mar 15, 2019 at 5:36 AM Scott Gray
> wrote:
>
>> Hi Swapnil,
>>
>> A minor thing, but I wonder if it would be better to move this check
>> underneath node.getTextContent()? If we assume that most nodes will
>> contain text then it might be more efficient to do a null check after
>> retrieving nodeValue.
>>
>> e.g.
>> Node node = (Node) obj;
>> String nodeValue = node.getTextContent();
>> if (nodeValue == null) {
>> // Check node type and return obj;
>> }
>> if ("String".equals(type) || "java.lang.String".equals(type)) {
>> return nodeValue;
>> ...
>>
>> Regards
>> Scott
>>
>>
>> On Thu, 14 Mar 2019, 01:27 , wrote:
>>
>> > Author: swapnilmmane
>> > Date: Wed Mar 13 12:27:13 2019
>> > New Revision: 1855403
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1855403&view=rev
>> > Log:
>> > Fixed: simpleTypeConvert always returns Null for Document, Document Type
>> > and Notation Node (OFBIZ-10832)
>> >
>> > As per the code, getTextContent() method is used get text content of the
>> > node and its descendants but the node.getTextContent() always return
>> Null
>> > for the following Node type
>> > DOCUMENT_NODE, DOCUMENT_TYPE_NODE, NOTATION_NODE [1]
>> >
>> > Since we can't get the text value of Document, Document Type and
>> Notation
>> > Node, thus simply return the same object.
>> >
>> > [1]
>> >
>> https://docs.oracle.com/javase/7/docs/api/org/w3c/dom/Node.html#getTextContent()
>> >
>> > Thanks: Deepak Dixit for reviewing the code.
>> >
>> > Modified:
>> >
>> >
>> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
>> >
>> > Modified:
>> >
>> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
>> > URL:
>> >
>> http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java?rev=1855403&r1=1855402&r2=1855403&view=diff
>> >
>> >
>> ==
>> > ---
>> >
>> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
>> > (original)
>> > +++
>> >
>> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
>> > Wed Mar 13 12:27:13 2019
>> > @@ -289,6 +289,17 @@ public class ObjectType {
>> > }
>> > if (obj instanceof Node) {
>> > Node node = (Node) obj;
>> > +
>> > +/* We can't get the text value of Document, Document Type
>> and
>> > Notation Node,
>> > + * thus simply returning the same object from
>> > simpleTypeOrObjectConvert method.
>> > + * Please refer to OFBIZ-10832 Jira and
>> > + *
>> >
>> https://docs.oracle.com/javase/7/docs/api/org/w3c/dom/Node.html#getTextContent()
>> > for more details.
>> > + */
>> > +short nodeType = node.getNodeType();
>> > +if (Node.DOCUMENT_NODE == nodeType ||
>> Node.DOCUMENT_TYPE_NODE
>> > == nodeType || Node.NOTATION_NODE == nodeType) {
>> > +return obj;
>> > +}
>> > +
>> > String nodeValue = node.getTextContent();
>> > if ("String".equals(type) ||
>> "java.lang.String".equals(type))
>> > {
>> > return nodeValue;
>> >
>> >
>> >
>>
>
Re: OFBiz Video Tutorial Series
On Mon, Mar 18, 2019 at 7:38 PM Swapnil M Mane wrote: > Hello team, > > Here are some updates on the OFBiz video tutorial effort. > As a first step, created a playlist for Apache OFBiz [1]. > As a first step, created a playlist for Apache OFBiz Tutorial [1]. > > Highlights of this playlist are > 1.) It contains the videos in a sequential manner from beginner to expert. > 2.) This playlist will *always* be in sync with the trunk branch. > The main idea is to always have videos which work with OFBiz trunk branch. > This surely helps the beginner developers. > > Thus, I have made some changes in the video description, like added the > following information in the video description - > "Reference OFBiz release in the video is Release 16.11. This process will > also work with the OFBiz trunk branch." > > In the future, if any video is not synced with trunk, we will create the > new video and will add it in the playlist. The title of the old video will > be changed and will include the compatible release-specific detail. > > I am currently working on 'OFBiz directory structure and component' video, > after adding it in the playlist. I will share the playlist information on > the user mailing list also. > > Thanks, Pranay Pandey for your continuous contribution and help on this. > Everyone, please feel free to add your comments and thoughts. > > [1] > https://www.youtube.com/watch?v=bIS2kftvsq4&list=PLobIkeUbRXqc-lwvbdbajPJdbWjFm82Dj > > - Best Regards, > Swapnil M Mane, > ofbiz.apache.org > >
OFBiz Video Tutorial Series
Hello team, Here are some updates on the OFBiz video tutorial effort. As a first step, created a playlist for Apache OFBiz [1]. Highlights of this playlist are 1.) It contains the videos in a sequential manner from beginner to expert. 2.) This playlist will *always* be in sync with the trunk branch. The main idea is to always have videos which work with OFBiz trunk branch. This surely helps the beginner developers. Thus, I have made some changes in the video description, like added the following information in the video description - "Reference OFBiz release in the video is Release 16.11. This process will also work with the OFBiz trunk branch." In the future, if any video is not synced with trunk, we will create the new video and will add it in the playlist. The title of the old video will be changed and will include the compatible release-specific detail. I am currently working on 'OFBiz directory structure and component' video, after adding it in the playlist. I will share the playlist information on the user mailing list also. Thanks, Pranay Pandey for your continuous contribution and help on this. Everyone, please feel free to add your comments and thoughts. [1] https://www.youtube.com/watch?v=bIS2kftvsq4&list=PLobIkeUbRXqc-lwvbdbajPJdbWjFm82Dj - Best Regards, Swapnil M Mane, ofbiz.apache.org
Re: svn commit: r1855403 - /ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
Makes perfect sense, thanks so much for the input Scott.
I will do the suggested changes.
- Best Regards,
Swapnil M Mane,
ofbiz.apache.org
On Fri, Mar 15, 2019 at 5:36 AM Scott Gray
wrote:
> Hi Swapnil,
>
> A minor thing, but I wonder if it would be better to move this check
> underneath node.getTextContent()? If we assume that most nodes will
> contain text then it might be more efficient to do a null check after
> retrieving nodeValue.
>
> e.g.
> Node node = (Node) obj;
> String nodeValue = node.getTextContent();
> if (nodeValue == null) {
> // Check node type and return obj;
> }
> if ("String".equals(type) || "java.lang.String".equals(type)) {
> return nodeValue;
> ...
>
> Regards
> Scott
>
>
> On Thu, 14 Mar 2019, 01:27 , wrote:
>
> > Author: swapnilmmane
> > Date: Wed Mar 13 12:27:13 2019
> > New Revision: 1855403
> >
> > URL: http://svn.apache.org/viewvc?rev=1855403&view=rev
> > Log:
> > Fixed: simpleTypeConvert always returns Null for Document, Document Type
> > and Notation Node (OFBIZ-10832)
> >
> > As per the code, getTextContent() method is used get text content of the
> > node and its descendants but the node.getTextContent() always return Null
> > for the following Node type
> > DOCUMENT_NODE, DOCUMENT_TYPE_NODE, NOTATION_NODE [1]
> >
> > Since we can't get the text value of Document, Document Type and Notation
> > Node, thus simply return the same object.
> >
> > [1]
> >
> https://docs.oracle.com/javase/7/docs/api/org/w3c/dom/Node.html#getTextContent()
> >
> > Thanks: Deepak Dixit for reviewing the code.
> >
> > Modified:
> >
> >
> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
> >
> > Modified:
> >
> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
> > URL:
> >
> http://svn.apache.org/viewvc/ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java?rev=1855403&r1=1855402&r2=1855403&view=diff
> >
> >
> ==
> > ---
> >
> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
> > (original)
> > +++
> >
> ofbiz/ofbiz-framework/trunk/framework/base/src/main/java/org/apache/ofbiz/base/util/ObjectType.java
> > Wed Mar 13 12:27:13 2019
> > @@ -289,6 +289,17 @@ public class ObjectType {
> > }
> > if (obj instanceof Node) {
> > Node node = (Node) obj;
> > +
> > +/* We can't get the text value of Document, Document Type
> and
> > Notation Node,
> > + * thus simply returning the same object from
> > simpleTypeOrObjectConvert method.
> > + * Please refer to OFBIZ-10832 Jira and
> > + *
> >
> https://docs.oracle.com/javase/7/docs/api/org/w3c/dom/Node.html#getTextContent()
> > for more details.
> > + */
> > +short nodeType = node.getNodeType();
> > +if (Node.DOCUMENT_NODE == nodeType ||
> Node.DOCUMENT_TYPE_NODE
> > == nodeType || Node.NOTATION_NODE == nodeType) {
> > +return obj;
> > +}
> > +
> > String nodeValue = node.getTextContent();
> > if ("String".equals(type) ||
> "java.lang.String".equals(type))
> > {
> > return nodeValue;
> >
> >
> >
>
Re: storeOrder Service
+1 - Best Regards, Swapnil M Mane On Fri, Mar 1, 2019 at 3:22 PM Rishi Solanki wrote: > Dear All, > While working with storeOrder service, I observe that few order header > level values not passed and stored in that service. Also no code support > exists for those order header fields. Below are the fields which is not > taken care by the service code, please let me know if we can add > conditional support for these field, that means if the value comes in > parameter then it will be stored otherwise not. > - priority > - isRushOrder > > These values can be reset after creating order by using updateOrderHeader > service, but I think this should be fine to have these and other missing > values of header level as IN parameters and handled by the service. > > Please let me know in case of any objections, I would like to commit the > proposed changes. > > Best Regards, > -- > Rishi Solanki > Sr Manager, Enterprise Software Development > HotWax Systems Pvt. Ltd. > Direct: +91-9893287847 > http://www.hotwaxsystems.com > www.hotwax.co >
Re: Direct donations
+1 to update the footer with both the links. - Best Regards, Swapnil M Mane, ofbiz.apache.org On Wed, Feb 20, 2019 at 6:34 PM Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > Hi Jacques, > > the link to the "Donations" page is mentioned in the first line of the > "Sponsorship" page, so it should be easy to find anyway. > However we could modify our footer item from "Sponsorship" to "Sponsorship > and Donations" (in which each words redirects to the relevant page. > > Jacopo > > > On Wed, Feb 20, 2019 at 1:39 PM Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > Hi, > > > > I know we have a link in the site for "Sponsorship" to a page which > > contains the below link. > > > > But what about adding a direct "Donations" link to > > https://www.apache.org/foundation/contributing.html? > > > > Jacques > > > > >
Re: Welcome to Mathieu Lirzin as new committer!
Many congratulations Mathieu, welcome aboard :-) - Best Regards, Swapnil M Mane, ofbiz.apache.org On Tue, Feb 19, 2019 at 10:46 PM Taher Alkhateeb wrote: > The OFBiz PMC has invited Mathieu Lirzin to become a new committer and > we are happy to announce that he has accepted this role. > > Some of the reasons for inviting Mathieu include: > > - He is invested in the OFBiz project and has delivered substantial > work to the code base. > - He has demonstrated solid technical skills. > - He adopts a professional attitude towards coding and software > development. > - He engages thoughtfully with others and likes to work with the community. > > Please join me in welcoming and congratulating Mathieu! > > Cheers, > Taher Alkhateeb >
Re: OFBiz Demo not usable
:-D Thanks for the information, Jacques! - Best Regards, Swapnil M Mane On Tue, Feb 5, 2019 at 12:23 PM Jacques Le Roux < jacques.le.r...@les7arts.com> wrote: > Hi, > > I think I already wrote about that. There was a French deputy < > https://en.wikipedia.org/wiki/Henri_Queuille> in the 20th century who > said: > > « Il n’est pas de problème qu’une absence de solution ne finisse par > résoudre ». > > which can be translated to > > There is no problem that a lack of solution does not solve in the end > > Of course it's humour, but it worked again :-) > > Because every night the demos are starting again as if it was their 1st day > > It does not always work, sometimes people are playing with them too much > and broke them, poor things :'( > > Thanks for your patience > > Jacques > > Le 05/02/2019 à 05:43, Swapnil M Mane a écrit : > > Hello Dennis, > > Are you referring to this instance - > > https://demo-trunk.ofbiz.apache.org/ordermgr/control/main > > It is working as expected on my machine, can you please check again. > > > > > > - Best Regards, > > Swapnil M Mane, > > > > > > On Mon, Feb 4, 2019 at 10:02 PM Dennis Balkir > > wrote: > > > >> Hi Devs, > >> > >> it seems like the Trunk Demo is not usable at the moment. > >> Everytime I open it up, I just get a non-styled version of the page, > >> with the menu all over it and nothing else. I tried clearing browser > >> data, but this didn't work either. > >> > >> The login page looks normal though. > >> > >> I don't really know what happened, maybe someone can take a look? > >> > >> Thanks and regards, > >> Dennis > >> > >> >
Re: OFBiz Demo not usable
Hello Dennis, Are you referring to this instance - https://demo-trunk.ofbiz.apache.org/ordermgr/control/main It is working as expected on my machine, can you please check again. - Best Regards, Swapnil M Mane, On Mon, Feb 4, 2019 at 10:02 PM Dennis Balkir wrote: > Hi Devs, > > it seems like the Trunk Demo is not usable at the moment. > Everytime I open it up, I just get a non-styled version of the page, > with the menu all over it and nothing else. I tried clearing browser > data, but this didn't work either. > > The login page looks normal though. > > I don't really know what happened, maybe someone can take a look? > > Thanks and regards, > Dennis > >
[jira] [Commented] (OFBIZ-7844) View Customer request link is broken in mail send to the customer
[ https://issues.apache.org/jira/browse/OFBIZ-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380718#comment-15380718 ] Swapnil M Mane commented on OFBIZ-7844: --- Thanks [~pandeypranay]! :-) > View Customer request link is broken in mail send to the customer > - > > Key: OFBIZ-7844 > URL: https://issues.apache.org/jira/browse/OFBIZ-7844 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk > Reporter: Swapnil M Mane >Assignee: Pranay Pandey > Fix For: Upcoming Branch > > Attachments: OFBIZ-7844_1307.patch, OFBIZ-7844_trunk.patch > > > Mail send to the customer when any Customer request is created, or Completed, > or added the note on customer request. > The link provided in the mail to see it's customer request is broken. > The link generated in mail is > https://localhost:8443/myportal/control/showPortletDecorator?portalPortletId=ViewCustRequest&id=9000 > *Reason:* The 'showPortletDecorator' controller request doesn't exist. > As per the exploration, In rev #925723 > http://svn.apache.org/viewvc?limit_changes=0&view=revision&revision=925723 > we have removed the 'showPortletDecorator' request-map from > 'showPortletMainDecorator' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7844) View Customer request link is broken in mail send to the customer
[ https://issues.apache.org/jira/browse/OFBIZ-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane updated OFBIZ-7844: -- Summary: View Customer request link is broken in mail send to the customer (was: View Custome request link is broken in mail send to the customer) > View Customer request link is broken in mail send to the customer > - > > Key: OFBIZ-7844 > URL: https://issues.apache.org/jira/browse/OFBIZ-7844 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk > Reporter: Swapnil M Mane > Assignee: Swapnil M Mane > Attachments: OFBIZ-7844_1307.patch, OFBIZ-7844_trunk.patch > > > Mail send to the customer when any Customer request is created, or Completed, > or added the note on customer request. > The link provided in the mail to see it's customer request is broken. > The link generated in mail is > https://localhost:8443/myportal/control/showPortletDecorator?portalPortletId=ViewCustRequest&id=9000 > *Reason:* The 'showPortletDecorator' controller request doesn't exist. > As per the exploration, In rev #925723 > http://svn.apache.org/viewvc?limit_changes=0&view=revision&revision=925723 > we have removed the 'showPortletDecorator' request-map from > 'showPortletMainDecorator' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7844) View Custome request link is broken in mail send to the customer
[ https://issues.apache.org/jira/browse/OFBIZ-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane updated OFBIZ-7844: -- Attachment: OFBIZ-7844_1307.patch OFBIZ-7844_trunk.patch Attaching the patch. Fixed the issue where customer note request link is broken in mail send to the user when any Customer request created, or Completed, or added the note on customer request. Updated the reference of 'showPortletDecorator' to 'showPortletMainDecorator'. > View Custome request link is broken in mail send to the customer > > > Key: OFBIZ-7844 > URL: https://issues.apache.org/jira/browse/OFBIZ-7844 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk > Reporter: Swapnil M Mane >Assignee: Swapnil M Mane > Attachments: OFBIZ-7844_1307.patch, OFBIZ-7844_trunk.patch > > > Mail send to the customer when any Customer request is created, or Completed, > or added the note on customer request. > The link provided in the mail to see it's customer request is broken. > The link generated in mail is > https://localhost:8443/myportal/control/showPortletDecorator?portalPortletId=ViewCustRequest&id=9000 > *Reason:* The 'showPortletDecorator' controller request doesn't exist. > As per the exploration, In rev #925723 > http://svn.apache.org/viewvc?limit_changes=0&view=revision&revision=925723 > we have removed the 'showPortletDecorator' request-map from > 'showPortletMainDecorator' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7844) View Custome request link is broken in mail send to the customer
Swapnil M Mane created OFBIZ-7844: - Summary: View Custome request link is broken in mail send to the customer Key: OFBIZ-7844 URL: https://issues.apache.org/jira/browse/OFBIZ-7844 Project: OFBiz Issue Type: Bug Components: order Affects Versions: Trunk, Release Branch 14.12, Release Branch 13.07 Reporter: Swapnil M Mane Mail send to the customer when any Customer request is created, or Completed, or added the note on customer request. The link provided in the mail to see it's customer request is broken. The link generated in mail is https://localhost:8443/myportal/control/showPortletDecorator?portalPortletId=ViewCustRequest&id=9000 *Reason:* The 'showPortletDecorator' controller request doesn't exist. As per the exploration, In rev #925723 http://svn.apache.org/viewvc?limit_changes=0&view=revision&revision=925723 we have removed the 'showPortletDecorator' request-map from 'showPortletMainDecorator' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-7844) View Custome request link is broken in mail send to the customer
[ https://issues.apache.org/jira/browse/OFBIZ-7844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane reassigned OFBIZ-7844: - Assignee: Swapnil M Mane > View Custome request link is broken in mail send to the customer > > > Key: OFBIZ-7844 > URL: https://issues.apache.org/jira/browse/OFBIZ-7844 > Project: OFBiz > Issue Type: Bug > Components: order >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk > Reporter: Swapnil M Mane > Assignee: Swapnil M Mane > > Mail send to the customer when any Customer request is created, or Completed, > or added the note on customer request. > The link provided in the mail to see it's customer request is broken. > The link generated in mail is > https://localhost:8443/myportal/control/showPortletDecorator?portalPortletId=ViewCustRequest&id=9000 > *Reason:* The 'showPortletDecorator' controller request doesn't exist. > As per the exploration, In rev #925723 > http://svn.apache.org/viewvc?limit_changes=0&view=revision&revision=925723 > we have removed the 'showPortletDecorator' request-map from > 'showPortletMainDecorator' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7817) Party manager home screen generates console error
Swapnil M Mane created OFBIZ-7817:
-
Summary: Party manager home screen generates console error
Key: OFBIZ-7817
URL: https://issues.apache.org/jira/browse/OFBIZ-7817
Project: OFBiz
Issue Type: Bug
Components: party
Affects Versions: Trunk
Reporter: Swapnil M Mane
Assignee: Swapnil M Mane
When we navigate to the 'Party' Manager component, following error is generated
{code}
2016-07-16 10:34:48,273 |ttp-nio-8443-exec-10 |GenericDelegator
|E| Error getting entity definition from model
org.ofbiz.entity.GenericModelException: Could not find definition for entity
name PartyClassificationGroupAndType
at
org.ofbiz.entity.model.ModelReader.getModelEntity(ModelReader.java:489)
~[trunk.jar:?]
at
org.ofbiz.entity.GenericDelegator.getModelEntity(GenericDelegator.java:407)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelFormField$EntityOptions.addOptionValues(ModelFormField.java:1904)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelFormField$FieldInfoWithOptions.getAllOptionValues(ModelFormField.java:2065)
[trunk.jar:?]
at
org.ofbiz.widget.renderer.macro.MacroFormRenderer.renderDropDownField(MacroFormRenderer.java:756)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelFormField$DropDownField.renderFieldString(ModelFormField.java:1811)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelFormField.renderFieldString(ModelFormField.java:722)
[trunk.jar:?]
at
org.ofbiz.widget.renderer.FormRenderer.renderSingleFormString(FormRenderer.java:1199)
[trunk.jar:?]
at org.ofbiz.widget.renderer.FormRenderer.render(FormRenderer.java:264)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Form.renderWidgetString(ModelScreenWidget.java:1053)
[trunk.jar:?]
at
org.ofbiz.widget.renderer.macro.MacroScreenRenderer.renderScreenletSubWidget(MacroScreenRenderer.java:682)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Screenlet.renderWidgetString(ModelScreenWidget.java:599)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$DecoratorSection.renderWidgetString(ModelScreenWidget.java:906)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$SectionsRenderer.render(ModelScreenWidget.java:127)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$DecoratorSectionInclude.renderWidgetString(ModelScreenWidget.java:943)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:459)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:459)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Container.renderWidgetString(ModelScreenWidget.java:459)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:164)
[trunk.jar:?]
at
org.ofbiz.widget.model.ScreenFactory.renderReferencedScreen(ScreenFactory.java:214)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$IncludeScreen.renderWidgetString(ModelScreenWidget.java:780)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget.renderSubWidgetsString(ModelScreenWidget.java:98)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreenWidget$Section.renderWidgetString(ModelScreenWidget.java:280)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelScreen.renderScreenString(ModelScreen.java:164)
[trunk.jar:?]
at
org.ofbiz.widget.model.ScreenFactory.renderReferencedScreen(ScreenFactory.java:214)
[trunk.jar:?]
at
org.ofbiz.widget.model.ModelSc
[jira] [Updated] (OFBIZ-7311) Formatting and renaming of the CSS files as per best practices
[
https://issues.apache.org/jira/browse/OFBIZ-7311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil M Mane updated OFBIZ-7311:
--
Attachment: OFBIZ-7311-removed_references_of_maincss.patch
Hello team,
I have removed the unused references of the maincss.css from source code, done
the following things
1.) Removed 'maincss.css' entry from 'allowedPaths' param of from web.xml
*Reason:* Since, there is no file like 'maincss.css' exist under any includes
directory.
2.) Removed the unused references of maincss.css from FTLs, code
{code}
{code}
has been removed.
*Reason:* This is an interesting thing, these FTLs were using the maincss.css
located under the images directory.
When I look the history of these files, following were my findings,
The 'maincss.css' file under the 'images' directory exist in release4.0
http://svn.apache.org/repos/asf/ofbiz/branches/release4.0/framework/images/webapp/images/
after this release, this files no longer exist there.
3.) Also, I have updated one file 'InventoryNoticeEmail.ftl' and used the basic
HTML code to style, instead of using style defined in 'maincss.css' which were
exist in release-4.0
4.) Updated some references from 'maincss.css' to style.css in comments.
5.) Also removed the entry of including '/images/maincss.css' and
'/images/mainrtl.css' in SimpleDecorator
Since, these files no longer exist after release-4.0.
Dear [~pandeypranay], [~wt] and team,
Please have a look this patch :)
Thanks!
> Formatting and renaming of the CSS files as per best practices
> --
>
> Key: OFBIZ-7311
> URL: https://issues.apache.org/jira/browse/OFBIZ-7311
> Project: OFBiz
> Issue Type: Improvement
> Components: themes
>Affects Versions: Trunk
>Reporter: Swapnil M Mane
>Assignee: Pranay Pandey
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7311-bizznesstime.patch,
> OFBIZ-7311-bluelight.patch, OFBIZ-7311-droppingcrumbs.patch,
> OFBIZ-7311-flatgrey.patch, OFBIZ-7311-multiflex.patch,
> OFBIZ-7311-rainbowstone.patch,
> OFBIZ-7311-removed_references_of_maincss.patch,
> OFBIZ-7311-renamed-maincss-to-style.patch, OFBIZ-7311-tomahawk.patch
>
>
> In CSS files, we are having various inconsistency in the formatting of the
> code for e.g. we have following types of code formatting
> // No space
> {code}
> ul#preferences-menu a:hover {
> text-decoration: none;
> }
> {code}
> // Space of 2
> {code}
> div.autocomplete ul {
> list-style-type:none;
> margin:0;
> padding:0;
> }
> {code}
> // Space of 4
> {code}
> .control-area a {
> font-size: 1.1em;
> color: #5CA3D7;
> }
> {code}
> For better readability we should format the existing files with space of 4.
> Also for some theme, we named CSS files as *maincss.css* and for some, we
> named it as *style.css*. We can rename these file as per best practices for
> consistency.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-7704) 'original page' field is partially visible in create 'New Portal Page' screen
[ https://issues.apache.org/jira/browse/OFBIZ-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Swapnil M Mane updated OFBIZ-7704: -- Attachment: new_portal_page.png > 'original page' field is partially visible in create 'New Portal Page' screen > - > > Key: OFBIZ-7704 > URL: https://issues.apache.org/jira/browse/OFBIZ-7704 > Project: OFBiz > Issue Type: Bug > Components: specialpurpose/myportal >Affects Versions: Trunk > Reporter: Swapnil M Mane >Assignee: Swapnil M Mane >Priority: Minor > Attachments: new_portal_page.png > > > In the screen of new portal page creation, the 'original page' is partially > visible and going out of the screen. > Steps to regenerate > #1) Go to My Portal > #2) select Preferences sub-menu > #3) Select the option 'New Portal Page' > (https://localhost:8443/myportal/control/NewPortalPage?parentPortalPageId=MYPORTAL_EMPLOYEE) > Please find the attachment for more details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7704) 'original page' field is partially visible in create 'New Portal Page' screen
Swapnil M Mane created OFBIZ-7704:
-
Summary: 'original page' field is partially visible in create 'New
Portal Page' screen
Key: OFBIZ-7704
URL: https://issues.apache.org/jira/browse/OFBIZ-7704
Project: OFBiz
Issue Type: Bug
Components: specialpurpose/myportal
Affects Versions: Trunk
Reporter: Swapnil M Mane
Assignee: Swapnil M Mane
Priority: Minor
In the screen of new portal page creation, the 'original page' is partially
visible and going out of the screen.
Steps to regenerate
#1) Go to My Portal
#2) select Preferences sub-menu
#3) Select the option 'New Portal Page'
(https://localhost:8443/myportal/control/NewPortalPage?parentPortalPageId=MYPORTAL_EMPLOYEE)
Please find the attachment for more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7575) Styling is not applied on Logs in LogView screen
[ https://issues.apache.org/jira/browse/OFBIZ-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352294#comment-15352294 ] Swapnil M Mane commented on OFBIZ-7575: --- Thanks everyone for communication, indeed a debatable topic for bug or improvement ;-) But as [~soledad] said, was in Log4j (release12.04) and broken with Log4j2 (because of new log pattern) (versions after release12.04) thus I considered it as Bug. Also, thanks [~pandeypranay] for backporting. > Styling is not applied on Logs in LogView screen > > > Key: OFBIZ-7575 > URL: https://issues.apache.org/jira/browse/OFBIZ-7575 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Swapnil M Mane >Assignee: Pranay Pandey > Fix For: 14.12.01, 15.12.01, 13.07.04 > > Attachments: OFBIZ-7575-after.png, OFBIZ-7575-before.png, > OFBIZ-7575.patch > > > In LogView screen (https://localhost:8443/webtools/control/LogView) the > styling on logs should be applied on the basis of its type. > for e.g. the error should be shown in red, the warning should be in blue etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7575) Styling is not applied on Logs in LogView screen
[ https://issues.apache.org/jira/browse/OFBIZ-7575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15351326#comment-15351326 ] Swapnil M Mane commented on OFBIZ-7575: --- Thanks [~pandeypranay]! :-) > Styling is not applied on Logs in LogView screen > > > Key: OFBIZ-7575 > URL: https://issues.apache.org/jira/browse/OFBIZ-7575 > Project: OFBiz > Issue Type: Bug > Components: framework/webtools >Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk, > Release Branch 15.12 >Reporter: Swapnil M Mane >Assignee: Pranay Pandey > Fix For: 14.12.01, 15.12.01, 13.07.04 > > Attachments: OFBIZ-7575-after.png, OFBIZ-7575-before.png, > OFBIZ-7575.patch > > > In LogView screen (https://localhost:8443/webtools/control/LogView) the > styling on logs should be applied on the basis of its type. > for e.g. the error should be shown in red, the warning should be in blue etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7061) Autocompletion for Compound Widget
[
https://issues.apache.org/jira/browse/OFBIZ-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347988#comment-15347988
]
Swapnil M Mane commented on OFBIZ-7061:
---
Thanks [~jacques.le.roux]!
> Autocompletion for Compound Widget
> --
>
> Key: OFBIZ-7061
> URL: https://issues.apache.org/jira/browse/OFBIZ-7061
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: james yong
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7061.patch, OFBIZ-7061.patch, OFBIZ-7061.patch
>
>
> I am trying to enable auto-completion when coding compound widget.
> My plan as follows:
> 1. The following xsd will be modified to use namespace
> site-conf.xsd
> widget-form.xsd
> widget-screen.xsd
> widget-menu.xsd
> simple-methods.xsd
> For example, in site-conf.xsd, we add the following document level attribute
> {code}
> xmlns="http://ofbiz.apache.org/sc";
> targetNamespace="http://ofbiz.apache.org/sc";
> {code}
> 2. Import the above schema into compound-widgets.xsd so that compound widgets
> use only one consolidated schema.
> 3. Update ExampleCompoundWidgets.xml to use the new compound-widgets.xsd. For
> example
> {code}
> http://www.w3.org/2001/XMLSchema-instance";
> xmlns:sc="http://ofbiz.apache.org/sc";
> xmlns:m="http://ofbiz.apache.org/m";
> xmlns:s="http://ofbiz.apache.org/s";
> xmlns:f="http://ofbiz.apache.org/f";
> xmlns:sm="http://ofbiz.apache.org/sm";
>
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/compound-widgets.xsd";>
>
>
>
> path="component://example/widget/example/ExampleCompoundWidgets.xml"/>
>
>
> auth="true"/> value="CompoundWidgets2"/>
>
> page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets1"/>
> page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets2"/>
>
> .. the rest
> {code}
> 4. Change java code to support reading xml with namespace (i.e. xml for
> compound widgets)
> 5. Update the attributes at document level for rest of the controllers,
> menus, forms, simple methods and screens. Current setting will not work for
> schema with a namespace. For example, in controller.xml, we will change
> {code}
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/site-conf.xsd”
> {code}
> to
> {code}
> xmlns="http://ofbiz.apache.org/sc”
> xsi:schemaLocation="http://ofbiz.apache.org/dtds/site-conf-ns.xsd”>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OFBIZ-7061) Autocompletion for Compound Widget
[
https://issues.apache.org/jira/browse/OFBIZ-7061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347752#comment-15347752
]
Swapnil M Mane commented on OFBIZ-7061:
---
Dear [~jacques.le.roux],
Preferences screen under in 'My Portal' component is broken
(https://localhost:8443/myportal/control/ManagePortalPages?parentPortalPageId=MYPORTAL_EMPLOYEE),
it is because of missing
{code}
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
{code}
in framework/common/widget/PortalPageForms.xml
Might be it is missed under the commit at rev #1749634 :)
http://svn.apache.org/viewvc/ofbiz/trunk/framework/common/widget/PortalPageForms.xml?limit_changes=0&r1=1749634&r2=1749633&pathrev=1749634
Thanks!
> Autocompletion for Compound Widget
> --
>
> Key: OFBIZ-7061
> URL: https://issues.apache.org/jira/browse/OFBIZ-7061
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: james yong
>Assignee: Jacques Le Roux
>Priority: Minor
> Fix For: Upcoming Branch
>
> Attachments: OFBIZ-7061.patch, OFBIZ-7061.patch, OFBIZ-7061.patch
>
>
> I am trying to enable auto-completion when coding compound widget.
> My plan as follows:
> 1. The following xsd will be modified to use namespace
> site-conf.xsd
> widget-form.xsd
> widget-screen.xsd
> widget-menu.xsd
> simple-methods.xsd
> For example, in site-conf.xsd, we add the following document level attribute
> {code}
> xmlns="http://ofbiz.apache.org/sc";
> targetNamespace="http://ofbiz.apache.org/sc";
> {code}
> 2. Import the above schema into compound-widgets.xsd so that compound widgets
> use only one consolidated schema.
> 3. Update ExampleCompoundWidgets.xml to use the new compound-widgets.xsd. For
> example
> {code}
> http://www.w3.org/2001/XMLSchema-instance";
> xmlns:sc="http://ofbiz.apache.org/sc";
> xmlns:m="http://ofbiz.apache.org/m";
> xmlns:s="http://ofbiz.apache.org/s";
> xmlns:f="http://ofbiz.apache.org/f";
> xmlns:sm="http://ofbiz.apache.org/sm";
>
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/compound-widgets.xsd";>
>
>
>
> path="component://example/widget/example/ExampleCompoundWidgets.xml"/>
>
>
> auth="true"/> value="CompoundWidgets2"/>
>
> page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets1"/>
> page="component://example/widget/example/ExampleCompoundWidgets.xml#CompoundWidgets2"/>
>
> .. the rest
> {code}
> 4. Change java code to support reading xml with namespace (i.e. xml for
> compound widgets)
> 5. Update the attributes at document level for rest of the controllers,
> menus, forms, simple methods and screens. Current setting will not work for
> schema with a namespace. For example, in controller.xml, we will change
> {code}
> xsi:noNamespaceSchemaLocation="http://ofbiz.apache.org/dtds/site-conf.xsd”
> {code}
> to
> {code}
> xmlns="http://ofbiz.apache.org/sc”
> xsi:schemaLocation="http://ofbiz.apache.org/dtds/site-conf-ns.xsd”>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
