[ 
https://issues.apache.org/jira/browse/OFBIZ-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17460076#comment-17460076
 ] 

Michael Brohl commented on OFBIZ-12459:
---------------------------------------

I will continue to ignore your untenable accusations and conspiratorial 
theories and will not respond to them further.
{quote}As soon as you actually start merging my contributions into the 
codebase, actually start collaborating with me on improvements, actually start 
recognising my merit, my way (of reacting to your comments) may change.
{quote}
I do exactly that: collaborate with you on improvements. I propose changes to 
your contribution to make it an acceptable contribution, be non-breaking and 
backwards compatible. I spend my time to explain my reasons. What else can I do?

If you can only accept collaborations with you in the sense that it will go 
into the codebase without review and quality check, you should collaborate with 
yourself in your own projects. Collaboration IS discussion, hearing other 
opinions and working with other people.

If we don't do that, we'll have a mess in the codebase very soon.
{quote}A suggestion: if you're so keen on OFBiz users working with having 
SystemProperty configuration records as .property file elements (as you 
remarked in OFBIZ-6670 regarding OFBiz DEVOPS work being a nightmare), why 
don't you contribute e.g. a Confluence page called:
{quote}
That's completely nonsense. The established way of configuration as a base in 
OFBiz is file based for a long time. There are serious OFBiz installations out 
there which use them. The projects drives businesses around the world. We have 
to provide consistency and do improvements thoroughly and carefully.

Why should we destroy trust in the project by making ill-considered changes?

Again, in case you do not understand my proposal in the first place:

EntityUtilProperties has a fallback mechanism. If the API finds a 
SystemProperty for a configuration key in the database, it will be used. If 
not, the corresponding file based property will be used. So all you have to do 
to have a non-breaking solution which provides additional value for users who 
want to use SystemProperty is to leave the properties file as-is, use 
EntityUtilProperties as you did in the code and provide the loading data for 
SystemProperty as a template without making it load per default. Easy.

> Cybersource - configuration
> ---------------------------
>
>                 Key: OFBIZ-12459
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12459
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>            Assignee: Pierre Smits
>            Priority: Major
>              Labels: 3rdParty, cybersource, fintech, integration
>
> Move 3rd party Fintech integration configuration for Cybersource from 
> initialisation configuration to runtime configuration.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to