Re: [jira] [Updated] (OFBIZ-11472) Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo

[Pierre Smits]

HI Swapnil,

Your update of OFBIZ-11472 made me wonder about the OFBiz sprints. See [1].
Shoul tickets in the section 'Issues not completed' not be pushed back to
the backlog?


[1]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=318=OFBIZ=reporting=sprintRetrospective=601

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OEM - The OFBiz Extensions Marketplace1
http://oem.ofbizci.net/oci-2/
1 not affiliated to (and not endorsed by) the OFBiz project


On Wed, May 20, 2020 at 8:12 PM Swapnil Mane (Jira)  wrote:

>
>  [
> https://issues.apache.org/jira/browse/OFBIZ-11472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Swapnil Mane updated OFBIZ-11472:
> -
> Sprint: OFBiz Community Day (May 2020)
>
> > Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> > ---
> >
> > Key: OFBIZ-11472
> > URL: https://issues.apache.org/jira/browse/OFBIZ-11472
> > Project: OFBiz
> >  Issue Type: Task
> >  Components: Demo
> >Reporter: Swapnil Mane
> >Assignee: Swapnil Mane
> >Priority: Minor
> >  Time Spent: 20m
> >  Remaining Estimate: 0h
> >
> > As discussed at [https://s.apache.org/kn1f9] thread,
> > We will setup new demo instance for 17.12 and obsolete 13.07.
> > The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> > Currently, OFBiz has three demo instance:
> > -- Previous Stable Release 13.07 - Demo
> > https://demo-old.ofbiz.apache.org/ordermgr/control/main
> > -- 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
> > So, as per new plan.
> > https://demo-old.ofbiz.apache.org will point to 16.11 (which is
> currently pointed at https://demo-stable.ofbiz.apache.org)
> > And the newly setup 17.12 will be served at
> https://demo-stable.ofbiz.apache.org
> >
> > For this, we will need to make changes in the deployment scripts.
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>

Re: [GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #117: Improved: Update Data Sets

[Pierre Smits]

It happened to me a few times that a PR didn't pass the quality gates of
SonarCloud. And it helped me to correct the situation on a next push

RE: BTW is a PR pushable if the SonarCloud tests don't  pass?
SonarCloud tests are done AFTER the PR is created. Then it checks on every
commit coming in from where the PR was originated.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
Apache Steve , committer


On Wed, May 20, 2020 at 8:15 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> For me both are useless, I have never seen a SonarCloud Quality Gate not
> passing and this information is visible on the PR before pushing it
>
> BTW is a PR pushable if the SonarCloud tests don't  pass?
>
> I could filter them, but by experience I tend to privilege cutting at
> root. Because maintainer email filters is not my cup of tea.
>
> Jacques
>
> Le 20/05/2020 à 19:54, Pawan Verma a écrit :
> > Hi Pierre,
> >
> > For me, this one is good --> Kudos, SonarCloud Quality Gate passed!
> >
> > This one seems to be useless --> sonarcloud[bot] removed a comment on
> pull
> > request
>
>

Re: [GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #117: Improved: Update Data Sets

[Jacques Le Roux]

For me both are useless, I have never seen a SonarCloud Quality Gate not 
passing and this information is visible on the PR before pushing it

BTW is a PR pushable if the SonarCloud tests don't  pass?

I could filter them, but by experience I tend to privilege cutting at root. 
Because maintainer email filters is not my cup of tea.

Jacques

Le 20/05/2020 à 19:54, Pawan Verma a écrit :

Hi Pierre,

For me, this one is good --> Kudos, SonarCloud Quality Gate passed!

This one seems to be useless --> sonarcloud[bot] removed a comment on pull
request

Re: [GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #117: Improved: Update Data Sets

[Pawan Verma]

Hi Pierre,

For me, this one is good --> Kudos, SonarCloud Quality Gate passed!

This one seems to be useless --> sonarcloud[bot] removed a comment on pull
request
-- 
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com


On Wed, May 20, 2020 at 11:02 PM Pierre Smits 
wrote:

> Just curious, but what do we want to get into the ml from github?
>
> If infra needs to be involved for modifications, then we better have lost
> of action items ready.
>
> Mvg
>
> Pierre
>
> Op wo 20 mei 2020 19:13 schreef Pawan Verma  >:
>
> > Hey Jacques, Pierre
> >
> > Yes, I also feel it's useless and annoying. IMO If we can mute this
> > notification, it would be a great thing.
> > --
> > Thanks & Regards
> > Pawan Verma
> > Technical Consultant
> > *HotWax Systems*
> > *Enterprise open source experts*
> > http://www.hotwaxsystems.com
> >
> >
> > On Wed, May 20, 2020 at 9:39 PM Pierre Smits 
> > wrote:
> >
> > > Not an issue. At least here, as I filter those out in my mail client.
> > >
> > > Met vriendelijke groet,
> > >
> > > Pierre Smits
> > > *Proud* *contributor** of* Apache OFBiz 
> > since
> > > 2008 (without privileges)
> > >
> > > *Apache Trafodion , Vice President*
> > > *Apache Directory , PMC Member*
> > > Apache Incubator , committer
> > > Apache Steve , committer
> > >
> > >
> > > On Wed, May 20, 2020 at 5:17 PM Jacques Le Roux <
> > > jacques.le.r...@les7arts.com> wrote:
> > >
> > > > Hi All,
> > > >
> > > > Do we have to suffer the comment then removed all time?
> > > >
> > > > It uselessly clutters the email boxes, isn't?
> > > >
> > > > Thanks
> > > >
> > > > Jacques
> > > >
> > > > Le 20/05/2020 à 14:31, GitBox a écrit :
> > > > > sonarcloud[bot] removed a comment on pull request #117:
> > > > > URL:
> > > >
> > >
> >
> https://github.com/apache/ofbiz-framework/pull/117#issuecomment-630424349
> > > > >
> > > > >
> > > > > Kudos, SonarCloud Quality Gate passed!
> > > > >
> > > > > [ > > > alt='Bug' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> > > )
> > > > [ > > > alt='A' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> > > )
> > > > [0 Bugs](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> > > > )
> > > > > [ > > > alt='Vulnerability' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> > > )
> > > > [ > > > alt='A' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> > > )
> > > > [0 Vulnerabilities](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> > > )
> > > > (and [ > > > alt='Security Hotspot' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT
> > > )
> > > > [0 Security Hotspots](https://sonarcloud.io/project/issue
> > > > >
> > > >
> > >
> >
> s?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT)
> > > > to review)
> > > > > [ > > > alt='Code Smell' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> > > )
> > > > [ > > > alt='A' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> > > )
> > > > [0 Code Smells](
> > > >
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> > > > )
> > > > >
> > > > > [ > > > alt='No Coverage information' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117
> > > )
> > > > No Coverage information
> > > > > [ > > > alt='0.0%' width='16' height='16' />](
> > > >
> > >
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list
> > > )
> > > > [0.0% Duplication](
> > > >
> > >
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list
> > > > )
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > 
> > > > > 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
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
>

Re: [GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #117: Improved: Update Data Sets

[Pierre Smits]

Just curious, but what do we want to get into the ml from github?

If infra needs to be involved for modifications, then we better have lost
of action items ready.

Mvg

Pierre

Op wo 20 mei 2020 19:13 schreef Pawan Verma :

> Hey Jacques, Pierre
>
> Yes, I also feel it's useless and annoying. IMO If we can mute this
> notification, it would be a great thing.
> --
> Thanks & Regards
> Pawan Verma
> Technical Consultant
> *HotWax Systems*
> *Enterprise open source experts*
> http://www.hotwaxsystems.com
>
>
> On Wed, May 20, 2020 at 9:39 PM Pierre Smits 
> wrote:
>
> > Not an issue. At least here, as I filter those out in my mail client.
> >
> > Met vriendelijke groet,
> >
> > Pierre Smits
> > *Proud* *contributor** of* Apache OFBiz 
> since
> > 2008 (without privileges)
> >
> > *Apache Trafodion , Vice President*
> > *Apache Directory , PMC Member*
> > Apache Incubator , committer
> > Apache Steve , committer
> >
> >
> > On Wed, May 20, 2020 at 5:17 PM Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> > > Hi All,
> > >
> > > Do we have to suffer the comment then removed all time?
> > >
> > > It uselessly clutters the email boxes, isn't?
> > >
> > > Thanks
> > >
> > > Jacques
> > >
> > > Le 20/05/2020 à 14:31, GitBox a écrit :
> > > > sonarcloud[bot] removed a comment on pull request #117:
> > > > URL:
> > >
> >
> https://github.com/apache/ofbiz-framework/pull/117#issuecomment-630424349
> > > >
> > > >
> > > > Kudos, SonarCloud Quality Gate passed!
> > > >
> > > > [ > > alt='Bug' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> > )
> > > [ > > alt='A' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> > )
> > > [0 Bugs](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> > > )
> > > > [ > > alt='Vulnerability' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> > )
> > > [ > > alt='A' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> > )
> > > [0 Vulnerabilities](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> > )
> > > (and [ > > alt='Security Hotspot' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT
> > )
> > > [0 Security Hotspots](https://sonarcloud.io/project/issue
> > > >
> > >
> >
> s?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT)
> > > to review)
> > > > [ > > alt='Code Smell' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> > )
> > > [ > > alt='A' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> > )
> > > [0 Code Smells](
> > >
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> > > )
> > > >
> > > > [ > > alt='No Coverage information' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117
> > )
> > > No Coverage information
> > > > [ > > alt='0.0%' width='16' height='16' />](
> > >
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list
> > )
> > > [0.0% Duplication](
> > >
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list
> > > )
> > > >
> > > >
> > > >
> > > >
> > > > 
> > > > 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
> > > >
> > > >
> > >
> > >
> >
>

Re: [GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #117: Improved: Update Data Sets

[Pawan Verma]

Hey Jacques, Pierre

Yes, I also feel it's useless and annoying. IMO If we can mute this
notification, it would be a great thing.
-- 
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com


On Wed, May 20, 2020 at 9:39 PM Pierre Smits  wrote:

> Not an issue. At least here, as I filter those out in my mail client.
>
> Met vriendelijke groet,
>
> Pierre Smits
> *Proud* *contributor** of* Apache OFBiz  since
> 2008 (without privileges)
>
> *Apache Trafodion , Vice President*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> Apache Steve , committer
>
>
> On Wed, May 20, 2020 at 5:17 PM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > Hi All,
> >
> > Do we have to suffer the comment then removed all time?
> >
> > It uselessly clutters the email boxes, isn't?
> >
> > Thanks
> >
> > Jacques
> >
> > Le 20/05/2020 à 14:31, GitBox a écrit :
> > > sonarcloud[bot] removed a comment on pull request #117:
> > > URL:
> >
> https://github.com/apache/ofbiz-framework/pull/117#issuecomment-630424349
> > >
> > >
> > > Kudos, SonarCloud Quality Gate passed!
> > >
> > > [ > alt='Bug' width='16' height='16' />](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> )
> > [ > alt='A' width='16' height='16' />](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> )
> > [0 Bugs](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> > )
> > > [ > alt='Vulnerability' width='16' height='16' />](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> )
> > [ > alt='A' width='16' height='16' />](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> )
> > [0 Vulnerabilities](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY
> )
> > (and [ > alt='Security Hotspot' width='16' height='16' />](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT
> )
> > [0 Security Hotspots](https://sonarcloud.io/project/issue
> > >
> >
> s?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT)
> > to review)
> > > [ > alt='Code Smell' width='16' height='16' />](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> )
> > [ > alt='A' width='16' height='16' />](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> )
> > [0 Code Smells](
> >
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> > )
> > >
> > > [ > alt='No Coverage information' width='16' height='16' />](
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117
> )
> > No Coverage information
> > > [ > alt='0.0%' width='16' height='16' />](
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list
> )
> > [0.0% Duplication](
> >
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list
> > )
> > >
> > >
> > >
> > >
> > > 
> > > 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
> > >
> > >
> >
> >
>

Re: [GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #117: Improved: Update Data Sets

[Pierre Smits]

Not an issue. At least here, as I filter those out in my mail client.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
Apache Steve , committer


On Wed, May 20, 2020 at 5:17 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi All,
>
> Do we have to suffer the comment then removed all time?
>
> It uselessly clutters the email boxes, isn't?
>
> Thanks
>
> Jacques
>
> Le 20/05/2020 à 14:31, GitBox a écrit :
> > sonarcloud[bot] removed a comment on pull request #117:
> > URL:
> https://github.com/apache/ofbiz-framework/pull/117#issuecomment-630424349
> >
> >
> > Kudos, SonarCloud Quality Gate passed!
> >
> > [ alt='Bug' width='16' height='16' />](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG)
> [ alt='A' width='16' height='16' />](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG)
> [0 Bugs](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG
> )
> > [ alt='Vulnerability' width='16' height='16' />](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY)
> [ alt='A' width='16' height='16' />](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY)
> [0 Vulnerabilities](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY)
> (and [ alt='Security Hotspot' width='16' height='16' />](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT)
> [0 Security Hotspots](https://sonarcloud.io/project/issue
> >
>  
> s?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT)
> to review)
> > [ alt='Code Smell' width='16' height='16' />](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL)
> [ alt='A' width='16' height='16' />](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL)
> [0 Code Smells](
> https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL
> )
> >
> > [ alt='No Coverage information' width='16' height='16' />](
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117)
> No Coverage information
> > [ alt='0.0%' width='16' height='16' />](
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list)
> [0.0% Duplication](
> https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list
> )
> >
> >
> >
> >
> > 
> > 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
> >
> >
>
>

Re: [GitHub] [ofbiz-framework] sonarcloud[bot] removed a comment on pull request #117: Improved: Update Data Sets

[Jacques Le Roux]

Hi All,

Do we have to suffer the comment then removed all time?

It uselessly clutters the email boxes, isn't?

Thanks

Jacques

Le 20/05/2020 à 14:31, GitBox a écrit :

sonarcloud[bot] removed a comment on pull request #117:
URL: https://github.com/apache/ofbiz-framework/pull/117#issuecomment-630424349


Kudos, SonarCloud Quality Gate passed!

[](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=BUG)

[](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY) 
[](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY) [0 
Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=VULNERABILITY) 
(and [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT) [0 
Security Hotspots](https://sonarcloud.io/project/issue
  
s?id=apache_ofbiz-framework=117=false=SECURITY_HOTSPOT)
 to review)
[](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL)
 [](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL)
 [0 Code 
Smells](https://sonarcloud.io/project/issues?id=apache_ofbiz-framework=117=false=CODE_SMELL)

[](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117) No Coverage information

[](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list)
 [0.0% 
Duplication](https://sonarcloud.io/component_measures?id=apache_ofbiz-framework=117=new_duplicated_lines_density=list)






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

Re: New Online Help, base on ci.apache.org/projects/ofbiz/site/ofbizdoc

[Jacques Le Roux]

Thanks Olivier,

I must add that it's the current location and it would need more work to change 
it, notably Infra help

Jacques

Le 20/05/2020 à 16:24, Olivier Heintz a écrit :

Yes, of course

My explanation was not clear, I propose to have one documentation by release 
and use it in the relative help

My question is more about using (or not) 
ci.apache.org/projects/ofbiz/site/${release}/ofbizdoc

Le 20/05/2020 à 08:32, Michael Brohl a écrit :

Hi Olivier,

wouldn't it be better to have different documentation paths for the
different branches?

If we would show the trunk documentation/help for stable branches, it
will most likely be wrong in some cases.

Another thought: it would be great if we could have the docs available
at ofbiz.apache.org/docs/trunk/, ofbiz.apache.org/docs/r18.12/ etc.

Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 19.05.20 um 11:54 schrieb Olivier Heintz:

Hi Community,

I need some comment or thought about one of point of the solution proposed.

Is there some people against the fact of used 
ci.apache.org/projects/ofbiz/site/ofbizdoc (generate for the trunk) for the 
ofbiz help ?

As I explained in my previous email, ci.apache.org/projects/ofbiz/site/ofbizdoc 
would be the default value for userDocUri, (but value in
general.properties can be change with the local place of doc generation).

If community think, it's a good step solution (on the road to the new help 
system), I will create a JIRA for generating the doc on all supported
branches (currently, it's only done for r17)

I just finished to migrate AccountingHelpData.xml to added the 
Jira 11693 created with a patch proposed

if this solution is accepted, (and all asciidoc integrated) next step is to 
work component by component
For each:
1. add in the component decorator 
Hi community,

First step about Docbook migration to asciidoc is done, all existing files have 
been converted
(waiting a review before PR merge)

Next step is to have a new help system,

I propose to do a very simple solution which would be a link to a documentation 
site.
This solution would use
1. at ofbiz level, a default proprety for documentation website uri
2. at the screen level
  * it would be possible to give a other uri (for user documentation)
  * if the anchor in the user documentation for this screen is put, the new 
help is used otherwise the older link is used

If this solution is validated, next step will be to update all the screens with 
the correct link value

I propose to create the Jira (and the implmentation) with this very simple 
solution (using the doc generated by Buildbot as documentation site)
when some other people with a good knowledge of gradle and/or ofbiz cms have 
time to do a internal documentation website, it will be possible to
change the default uri ;-)

what's your opinion about ?


Le 26/02/2020 à 17:10, Olivier Heintz a écrit :

inline

Le 26/02/2020 à 14:02, Taher Alkhateeb a écrit :

Hello Olivier,

Without digging into much detail, I can say that it's a good idea to
switch the online help system to asciidoc.

The current structure of asciidoc templates is designed to be a full
manual document. To link up different pages to different sections, you
need to break the documentation down to smaller files and then combine
them. This way you can have both the "big" manual and the "per screen"
help section.

In my experience, as I'm working with
- current ofbiz online help
- ofbiz webhelp
- some static doc website done with Grav (build with multiple small files)
- some static doc website done with asciidoc (only one large file)
- ...

With multiple small files it's needed to have a very good search engine and a 
global index / TOC

With the One page doc, the TOC is very large and not always very convenient, 
but exist and the browser-find works
and it's easy to navigate between details and generality

So, as a user, I prefer help base on One page documentation.

Also, gradle might not be enough for online help. A more robust
solution could involve integrating asciidoc at the framework level to
dynamically generate help. So this is another idea to consider.

When we have tried, in the past to dynamically generate html from standard 
docbook process it was too slow
it's why it was decide to use a freemarker template to do the generation, 
even if only 5% of docbook syntax
was managed.

Documentation not change very often, static page seem enough for our need.


On Wed, Feb 26, 2020 at 2:29 PM Olivier Heintz  wrote:

Hi all,

Currently OFBiz Online help work with docbook files with html generation done 
by a ftl template.
   Link between screen and file to show is done with some content associated 
with key-word

Decision has been done to no more used docbook format but now use asciidoc 
format.

User-manual.adoc should be the new reference for user help. How to use it for 
online help ?

I think it's important that online help is link to a internal help 

Re: Modify OFBiz commit message template

[James Yong]

+1 to 


[Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira 
title | Free text] [(OFBIZ-)]

[More detailed explanation of what has been done and what the fix achieves,
sideeffects etc.]

[Thanks:] [ for ... and  for]


Regards,
James


On 2020/05/20 09:01:45, Jacques Le Roux  wrote: 
> Hi,
> 
> With Git IMO it's convenient (more information) to have the Jira number in 
> the title, eg: https://markmail.org/message/cyslglyoh5gf7l7t
> 
> If nobody disagree I'd like to modify
> 
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template
> 
> We could have
> 
> 
> 
> [Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira 
> title | Free text] [(OFBIZ-)]
> 
> [(OFBIZ-)]
> 
> [More detailed explanation of what has been done and what the fix achieves,
> sideeffects etc.]
> 
> [Thanks:] [ for ... and  for]
> 
> 
> 
> But I would prefer:
> 
> [Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira 
> title | Free text] [(OFBIZ-)]
> 
> [More detailed explanation of what has been done and what the fix achieves,
> sideeffects etc.]
> 
> [Thanks:] [ for ... and  for]
> 
> 
> Opinions?
> 
> Thanks
> 
> Jacques
> 
> 

Re: New Online Help, base on ci.apache.org/projects/ofbiz/site/ofbizdoc

[Olivier Heintz]

Yes, of course

My explanation was not clear, I propose to have one documentation by release 
and use it in the relative help

My question is more about using (or not) 
ci.apache.org/projects/ofbiz/site/${release}/ofbizdoc

Le 20/05/2020 à 08:32, Michael Brohl a écrit :
> Hi Olivier,
> 
> wouldn't it be better to have different documentation paths for the 
> different branches?
> 
> If we would show the trunk documentation/help for stable branches, it 
> will most likely be wrong in some cases.
> 
> Another thought: it would be great if we could have the docs available 
> at ofbiz.apache.org/docs/trunk/, ofbiz.apache.org/docs/r18.12/ etc.
> 
> Thanks,
> 
> Michael Brohl
> 
> ecomify GmbH - www.ecomify.de
> 
> 
> Am 19.05.20 um 11:54 schrieb Olivier Heintz:
>> Hi Community,
>>
>> I need some comment or thought about one of point of the solution proposed.
>>
>> Is there some people against the fact of used 
>> ci.apache.org/projects/ofbiz/site/ofbizdoc (generate for the trunk) for the 
>> ofbiz help ?
>>
>> As I explained in my previous email, 
>> ci.apache.org/projects/ofbiz/site/ofbizdoc would be the default value for 
>> userDocUri, (but value in
>> general.properties can be change with the local place of doc generation).
>>
>> If community think, it's a good step solution (on the road to the new help 
>> system), I will create a JIRA for generating the doc on all supported
>> branches (currently, it's only done for r17)
>>
>> I just finished to migrate AccountingHelpData.xml to added the > field="helpAnchor" to the correct screens, so now it's really possible to 
>> see if
>> it's usable. I will updated the JIRA 11693.
>>
>> Olivier
>>
>> Le 12/05/2020 à 16:42, Olivier Heintz a écrit :
>>> Jira 11693 created with a patch proposed
>>>
>>> if this solution is accepted, (and all asciidoc integrated) next step is to 
>>> work component by component
>>> For each:
>>> 1. add in the component decorator >> Title in user-documentation
>>> 2. using heldata.xml to update all screens which had a dedicated text for 
>>> help, with the new helpAnchor value
>>>
>>> It's not a too large task, which can be maybe add in the task list for the 
>>> next community days, and so finish the migration from docbook to asciidoc 
>>> ;-)
>>>
>>> any thoughts?
>>>
>>> ps: this week, I will do this job for accounting component
>>>
>>> Le 11/05/2020 à 15:38, Olivier Heintz a écrit :
 Hi community,

 First step about Docbook migration to asciidoc is done, all existing files 
 have been converted
 (waiting a review before PR merge)

 Next step is to have a new help system,

 I propose to do a very simple solution which would be a link to a 
 documentation site.
 This solution would use
1. at ofbiz level, a default proprety for documentation website uri
2. at the screen level
  * it would be possible to give a other uri (for user documentation)
  * if the anchor in the user documentation for this screen is put, the 
 new help is used otherwise the older link is used

 If this solution is validated, next step will be to update all the screens 
 with the correct link value

 I propose to create the Jira (and the implmentation) with this very simple 
 solution (using the doc generated by Buildbot as documentation site)
 when some other people with a good knowledge of gradle and/or ofbiz cms 
 have time to do a internal documentation website, it will be possible to
 change the default uri ;-)

 what's your opinion about ?


 Le 26/02/2020 à 17:10, Olivier Heintz a écrit :
> inline
>
> Le 26/02/2020 à 14:02, Taher Alkhateeb a écrit :
>> Hello Olivier,
>>
>> Without digging into much detail, I can say that it's a good idea to
>> switch the online help system to asciidoc.
>>
>> The current structure of asciidoc templates is designed to be a full
>> manual document. To link up different pages to different sections, you
>> need to break the documentation down to smaller files and then combine
>> them. This way you can have both the "big" manual and the "per screen"
>> help section.
> In my experience, as I'm working with
>- current ofbiz online help
>- ofbiz webhelp
>- some static doc website done with Grav (build with multiple small 
> files)
>- some static doc website done with asciidoc (only one large file)
>- ...
>
> With multiple small files it's needed to have a very good search engine 
> and a global index / TOC
>
> With the One page doc, the TOC is very large and not always very 
> convenient, but exist and the browser-find works
>and it's easy to navigate between details and generality
>
> So, as a user, I prefer help base on One page documentation.
>> Also, gradle might not be enough for online help. A more robust
>> solution could involve integrating 

Re: OFBiz Monthly Blog

[Pierre Smits]

Great idea, Pranay,

Such communications are an important aide to help grow the interest in or
product and our project, hopefully leading to more contributors.

Where is the link to the preview? So that I can see what the style and
format is for submissions.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
Apache Steve , committer


On Thu, May 7, 2020 at 4:39 PM Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> Hello Devs,
>
> Should we re-start our monthly blog?
> https://blogs.apache.org/ofbiz/
>
> Always a good way to keep engaging the interesting parties through social
> media who aren't subscribed to mailing lists.
>
> Thoughts?
>
> Kind regards,
> Pranay Pandey
>

Re: OFBiz Monthly Blog

[Michael Brohl]

Hi everyone,

I have created the blog entries for Jan-April 2020 and added the dev 
details. Thanks Ulrich Heidfeld for putting them together!


Someone willing to add the introduction/news text?

Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 07.05.20 um 22:00 schrieb Michael Brohl:

+1
We will provide the dev details as usual.

Thanks,
Michael


Am 07.05.2020 um 16:38 schrieb Pranay Pandey :

Hello Devs,

Should we re-start our monthly blog?
https://blogs.apache.org/ofbiz/

Always a good way to keep engaging the interesting parties through social
media who aren't subscribed to mailing lists.

Thoughts?

Kind regards,
Pranay Pandey




smime.p7s
Description: S/MIME Cryptographic Signature

Re: Modify OFBiz commit message template

[Benjamin Jugl]

Hello everyone,

Am 20.05.20 um 11:36 schrieb Pierre Smits:

The subject can be quite lengthy (as I have experienced a few times when
doing PRs). I suggest to moving the ticket Id to the front of the first
line.
Also, whatever the categorisation is ([Implemented | Improved | Fixed |
Completed| Documented | Reverted]: this should be referenced (at least) in
the ticket.

While having everything significant (like the categorisation) on the first
line is desirable, the minimum is the ticket ID.

I concur.


I don't mind (people) to click through to the ticket to get a better
understanding.


I used to edit the commit messages for the publication on the blog a 
while ago.
Having to click through all tickets to get a better understanding is not 
much fun. Even with the status quo it has to be done sometimes.
Although I cherish the learning that can take place by diving into 
resolved issues it is quite timeconsuming and cumbersome.


I like the "Thanks" even though it is not technically needed, it is 
always nice to read it.

Re: Modify OFBiz commit message template

[Pierre Smits]

Can GitHub be configured that when a ticket Id is present it is shown as a
link to the ticket in Jira. IIRC I have seen it happening.

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
Apache Steve , committer


On Wed, May 20, 2020 at 11:36 AM Pierre Smits 
wrote:

> The subject can be quite lengthy (as I have experienced a few times when
> doing PRs). I suggest to moving the ticket Id to the front of the first
> line.
> Also, whatever the categorisation is ([Implemented | Improved | Fixed |
> Completed| Documented | Reverted]: this should be referenced (at least) in
> the ticket.
>
> While having everything significant (like the categorisation) on the first
> line is desirable, the minimum is the ticket ID.
>
> I don't mind (people) to click through to the ticket to get a better
> understanding.
>
> What are best practices from other (Apache/Open Source) projects?
>
> Met vriendelijke groet,
>
> Pierre Smits
> *Proud* *contributor** of* Apache OFBiz  since
> 2008 (without privileges)
>
> *Apache Trafodion , Vice President*
> *Apache Directory , PMC Member*
> Apache Incubator , committer
> Apache Steve , committer
>
>
> On Wed, May 20, 2020 at 11:03 AM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
>> Hi,
>>
>> With Git IMO it's convenient (more information) to have the Jira number
>> in the title, eg: https://markmail.org/message/cyslglyoh5gf7l7t
>>
>> If nobody disagree I'd like to modify
>>
>>
>> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template
>>
>> We could have
>>
>> 
>>
>> [Implemented | Improved | Fixed | Completed| Documented | Reverted]:
>> [Jira title | Free text] [(OFBIZ-)]
>>
>> [(OFBIZ-)]
>>
>> [More detailed explanation of what has been done and what the fix
>> achieves,
>> sideeffects etc.]
>>
>> [Thanks:] [ for ... and  for]
>>
>> 
>>
>> But I would prefer:
>> 
>> [Implemented | Improved | Fixed | Completed| Documented | Reverted]:
>> [Jira title | Free text] [(OFBIZ-)]
>>
>> [More detailed explanation of what has been done and what the fix
>> achieves,
>> sideeffects etc.]
>>
>> [Thanks:] [ for ... and  for]
>>
>> 
>> Opinions?
>>
>> Thanks
>>
>> Jacques
>>
>>

Re: Modify OFBiz commit message template

[Pierre Smits]

The subject can be quite lengthy (as I have experienced a few times when
doing PRs). I suggest to moving the ticket Id to the front of the first
line.
Also, whatever the categorisation is ([Implemented | Improved | Fixed |
Completed| Documented | Reverted]: this should be referenced (at least) in
the ticket.

While having everything significant (like the categorisation) on the first
line is desirable, the minimum is the ticket ID.

I don't mind (people) to click through to the ticket to get a better
understanding.

What are best practices from other (Apache/Open Source) projects?

Met vriendelijke groet,

Pierre Smits
*Proud* *contributor** of* Apache OFBiz  since
2008 (without privileges)

*Apache Trafodion , Vice President*
*Apache Directory , PMC Member*
Apache Incubator , committer
Apache Steve , committer


On Wed, May 20, 2020 at 11:03 AM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi,
>
> With Git IMO it's convenient (more information) to have the Jira number in
> the title, eg: https://markmail.org/message/cyslglyoh5gf7l7t
>
> If nobody disagree I'd like to modify
>
>
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template
>
> We could have
>
> 
>
> [Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira
> title | Free text] [(OFBIZ-)]
>
> [(OFBIZ-)]
>
> [More detailed explanation of what has been done and what the fix achieves,
> sideeffects etc.]
>
> [Thanks:] [ for ... and  for]
>
> 
>
> But I would prefer:
> 
> [Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira
> title | Free text] [(OFBIZ-)]
>
> [More detailed explanation of what has been done and what the fix achieves,
> sideeffects etc.]
>
> [Thanks:] [ for ... and  for]
>
> 
> Opinions?
>
> Thanks
>
> Jacques
>
>

Modify OFBiz commit message template

[Jacques Le Roux]

Hi,

With Git IMO it's convenient (more information) to have the Jira number in the 
title, eg: https://markmail.org/message/cyslglyoh5gf7l7t

If nobody disagree I'd like to modify

https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+commit+message+template

We could have



[Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira 
title | Free text] [(OFBIZ-)]

[(OFBIZ-)]

[More detailed explanation of what has been done and what the fix achieves,
sideeffects etc.]

[Thanks:] [ for ... and  for]



But I would prefer:

[Implemented | Improved | Fixed | Completed| Documented | Reverted]: [Jira 
title | Free text] [(OFBIZ-)]

[More detailed explanation of what has been done and what the fix achieves,
sideeffects etc.]

[Thanks:] [ for ... and  for]


Opinions?

Thanks

Jacques

Re: enter a date directly, no more possible

[Pawan Verma]

Thanks, Olivier for the report. This bug was introduced by me under
OFBIZ-10432 and I've fixed it at bc0afa3. Thanks!
-- 
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com


On Wed, May 20, 2020 at 1:50 PM Olivier Heintz <
holivier.li...@ofbizextra.org> wrote:

> Hi,
>
> This morning on demo-trunk, it seems, it's no more possible to enter a
> date-time in a date-time field without using the calendar icon !
>
> ex: on party, added a security group
> The field seems to be disable
>
> is it normal ?  it's not really convenient
>
> Olivier
>

enter a date directly, no more possible

[Olivier Heintz]

Hi,

This morning on demo-trunk, it seems, it's no more possible to enter a 
date-time in a date-time field without using the calendar icon !

ex: on party, added a security group
The field seems to be disable

is it normal ?  it's not really convenient

Olivier

Re: New Online Help, base on ci.apache.org/projects/ofbiz/site/ofbizdoc

[Michael Brohl]

Hi Olivier,

wouldn't it be better to have different documentation paths for the 
different branches?


If we would show the trunk documentation/help for stable branches, it 
will most likely be wrong in some cases.


Another thought: it would be great if we could have the docs available 
at ofbiz.apache.org/docs/trunk/, ofbiz.apache.org/docs/r18.12/ etc.


Thanks,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 19.05.20 um 11:54 schrieb Olivier Heintz:

Hi Community,

I need some comment or thought about one of point of the solution proposed.

Is there some people against the fact of used 
ci.apache.org/projects/ofbiz/site/ofbizdoc (generate for the trunk) for the 
ofbiz help ?

As I explained in my previous email, ci.apache.org/projects/ofbiz/site/ofbizdoc 
would be the default value for userDocUri, (but value in
general.properties can be change with the local place of doc generation).

If community think, it's a good step solution (on the road to the new help 
system), I will create a JIRA for generating the doc on all supported
branches (currently, it's only done for r17)

I just finished to migrate AccountingHelpData.xml to added the 
Jira 11693 created with a patch proposed

if this solution is accepted, (and all asciidoc integrated) next step is to 
work component by component
For each:
1. add in the component decorator 
Hi community,

First step about Docbook migration to asciidoc is done, all existing files have 
been converted
(waiting a review before PR merge)

Next step is to have a new help system,

I propose to do a very simple solution which would be a link to a documentation 
site.
This solution would use
   1. at ofbiz level, a default proprety for documentation website uri
   2. at the screen level
 * it would be possible to give a other uri (for user documentation)
 * if the anchor in the user documentation for this screen is put, the new 
help is used otherwise the older link is used

If this solution is validated, next step will be to update all the screens with 
the correct link value

I propose to create the Jira (and the implmentation) with this very simple 
solution (using the doc generated by Buildbot as documentation site)
when some other people with a good knowledge of gradle and/or ofbiz cms have 
time to do a internal documentation website, it will be possible to
change the default uri ;-)

what's your opinion about ?


Le 26/02/2020 à 17:10, Olivier Heintz a écrit :

inline

Le 26/02/2020 à 14:02, Taher Alkhateeb a écrit :

Hello Olivier,

Without digging into much detail, I can say that it's a good idea to
switch the online help system to asciidoc.

The current structure of asciidoc templates is designed to be a full
manual document. To link up different pages to different sections, you
need to break the documentation down to smaller files and then combine
them. This way you can have both the "big" manual and the "per screen"
help section.

In my experience, as I'm working with
   - current ofbiz online help
   - ofbiz webhelp
   - some static doc website done with Grav (build with multiple small files)
   - some static doc website done with asciidoc (only one large file)
   - ...

With multiple small files it's needed to have a very good search engine and a 
global index / TOC

With the One page doc, the TOC is very large and not always very convenient, 
but exist and the browser-find works
   and it's easy to navigate between details and generality

So, as a user, I prefer help base on One page documentation.

Also, gradle might not be enough for online help. A more robust
solution could involve integrating asciidoc at the framework level to
dynamically generate help. So this is another idea to consider.

When we have tried, in the past to dynamically generate html from standard 
docbook process it was too slow
   it's why it was decide to use a freemarker template to do the generation, 
even if only 5% of docbook syntax
   was managed.

Documentation not change very often, static page seem enough for our need.


On Wed, Feb 26, 2020 at 2:29 PM Olivier Heintz  wrote:

Hi all,

Currently OFBiz Online help work with docbook files with html generation done 
by a ftl template.
  Link between screen and file to show is done with some content associated 
with key-word

Decision has been done to no more used docbook format but now use asciidoc 
format.

User-manual.adoc should be the new reference for user help. How to use it for 
online help ?

I think it's important that online help is link to a internal help (which can 
be modified) not to a Apache-OFBiz-website-Help
but this point of view can be discuss.

To be able to have OFBiz internal help, three points should be solved :
1) with asciidoc we have multiple documentations, it seem important to have a 
"website" to be able to access easily all the doc.
how to "encapsulate" each html documentation generated in a "website"
2) generation doc process put html and pdf files in build directory, how it's 
possible