Re: Strong dependency of OFBiz build on JCenter

[Nicolas Malin]

Hi,

I think the Jacopo's suggest will be a good improvement. The last years 
I told with a Herve Boutemy (hboutemy, maven-pmc) that explain me why 
it's better to use maven central :) . But historically we resolved all 
jar dependencies on jcenter and personally I didn't check yet if all jar 
resolution done with jcenter are also present on maven central.


Nicolas

On 22/03/2019 08:40, Swapnil M Mane 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

.
 > Could not HEAD '
https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml

'.
> 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

.
 > Could not HEAD '
https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml

'.
> 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
*

*BUILD FAILED* in 1m 14s
==

- Best Regards,
Swapnil M Mane,
www.hotwax.co

Re: Strong dependency of OFBiz build on JCenter

[Taher Alkhateeb]

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
>

When do we need a JIRA? (was: svn commit: r1855798 - /ofbiz/ofbiz-framework/trunk/build.gradle)

[Mathieu Lirzin]

Hello,

In the same spirit, I want to know if it is OK to improve or add some
Javadoc without opening a ticket on JIRA?

Thanks.

Mathieu Lirzin  writes:

> Hello Michael,
>
> Michael Brohl  writes:
>
>> don't we have Jira's for all these changes?
>>
>> If yes, please provide the issue number within the commit message so
>> that we have them in the monthly blog post/dev details.
>>
>> If no, we should have them, at least in the future.
>
> Sorry if the process I followed was not the right one.
>
> I must confess that the policy regarding how refactoring (done by
> committers) must be handled in term of JIRA creation, is not clear to
> me.  The block “When to create a Jira issue” on OFBiz wiki [1] is not
> helping much in that regard.  Maybe there is an implicit consensus in
> that regard that I am not aware of?
>
> My reasoning for not creating a JIRA was that those commits are pure
> refactoring meaning they are implementation details that don't change
> the observable behavior of the build and they are not part of a global
> plan.  Basically those cleanups happened by looking around while working
> on OFBIZ-10866 [2] but are unrelated to the endeavour of that task.
>
> What would you recommend in that scenario?
>
>> If these changes affect the documentation, the README.md should also
>> be edited to reflect them and stay in sync with the code.
>
> Sure I agree that's an important guideline to follow.
>
> Thanks.
>
> [1] 
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Contributors+Best+Practices
> [2] https://issues.apache.org/jira/browse/OFBIZ-10866

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37

Re: Strong dependency of OFBiz build on JCenter

[Jacopo Cappellato]

Adding one or more additional repositories in build.gradle (at the moment
we have only jcenter()) can be a solution.

Jacopo

On Fri, Mar 22, 2019 at 8: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
>

POC of HR-Documentation by process

[Olivier Heintz]

Hello Everyone,

I propose some modifications on HR documentation,
but I want to present the options I have chosen to be able to discuss with the 
community if they are a consensus or not for these options.

To help the discussion, I have done a part of HR documentation with these 
option to better explain ;-)
an example is often more clear than a long explanation.

You can see the documentation modified at 
https://ofbizadoc.ofbizextra.org/html5/user-manual.html
you can easily compare with the current trunk release at 
https://ofbizadoc.ofbizextra.org/html5/user-manual-std.html 
Same for pdf

Option 1: documentation drive by process
=
Each process is described via a scenario explained like a tutorial, and each 
time a core object is used, a link is done to its chapter.
It's done for the first process "Organization, Job Position and Definition"
current HR TOC
--
3.2. Human Resources
    3.2.1. About Human Resources
    3.2.2. Human Resources Processes
    3.2.3. Employee Positions
    3.2.4. Employees
    3.2.5. Employments
    3.2.6. Performance Review
    3.2.7. Qualifications
    3.2.8. Recruitment
    3.2.9. Skills
    3.2.10. Resumes
    3.2.11. Training
    3.2.12. Leave
    3.2.13. Security
    3.2.14. Global HR Settings
    3.2.15. Glossary
Proposed HR TOC

4. Human Resources
    4.1. About this documentation
    4.2. About Human Resources
    4.3. HR Processes
    4.3.1. Organization, Job Position and Definition
    4.3.2. Recruitment, Candidate Selection and Hiring
    4.3.3. Employee Training and Development
    4.3.4. Performance Management and Employee Evaluation
    4.3.5. Employee Salary and Benefits Administration
    4.4. HR core object
    4.4.1. Employee Positions
    4.4.2. Employees
    4.4.3. Employments
    4.4.4. Performance Review
    4.4.5. Qualifications
    4.4.6. Recruitment
    4.4.7. Skills
    4.4.8. Resumes
    4.4.9. Training
    4.4.10. Leave
    4.4.11. Security
    4.5. Global HR Settings
    4.5.1. Skills Types
    4.6. HR Data model
    4.6.1. Employee Position
    4.6.2. Employment
    4.6.3. Qualification, Skill, Review
    4.6.4. HR App intra-application integration
    4.7. Glossary

option 2: Associated a scenario UI test for each process
=
I have done one for the first process : "Organization, Job Position and 
Definition"
with WebDriver-selenium
to check if it works, I run it each days on the demo trunk environment 
https://demo-trunk.ofbiz.apache.org
and you can download the video (with comment) at
https://jenkins.ofbizextra.org/view/Trunk-Sel./job/02_Ofbiz_trunk_wktr1_SeleniumWebDriver_tests/168/artifact/build/test-output/CompanyOrganization-implementation.avi

it's speed on the video but it's easy to slow it by your video reader to have 
time to read comment or understand which action is done.


option 3: change the level  of  from 2 (==) to 1 (=)
=
TOC become
...
Core Business Applications
    3. Accounting
    4. Human Resources


option 4: add a chapter "About this documentation"
=
This chapter present the main OFBiz GUI rules with some screenshot

and link between tutorial and video of "Scenario GUI Test"


option 5: add a HR Data model with partial diagram
=
Each diagram is focus on One (or two) main entity(ies)
Each diagram show only main relationship between entities to better explain the 
major entity of the diagram


option 6: add a general OFBiz Glossary
=
For all general concept used by multiples components

Modification 7: Change the Human Resources Generality (the HR starting text)

Re-Used Human Resources introduction done in previous documentation proposition 
(WebHelp).

Modification 8: Remove EmplPosition from HR--Glossary because EmplPosition is a 
chapter of HR Core Object



I proposed to have a two level of discussion :
1) By option, discuss about if it's a good or not idea
2) If there is a consensus about an option that is a good idea, discuss about 
the implementation ( or content) of this option

After it will be easy to create jira by option or by file ...

How does that all sound to you?
Please let me know your thoughts, feedback, and improvement suggestions

Strong dependency of OFBiz build on JCenter

[Swapnil M Mane]

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

.
> Could not HEAD '
https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml

'.
   > 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

.
> Could not HEAD '
https://jcenter.bintray.com/org/mockito/mockito-core/maven-metadata.xml

'.
   > 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
*

*BUILD FAILED* in 1m 14s
==

- Best Regards,
Swapnil M Mane,
www.hotwax.co