Hello Devs,
Recently, we have pushed integration of the First Data payment gateway to
OOTB. When we were doing that, we got one question about repository
management for third-party applications. We have one ticket [1] open in
JIRA about moving third party code from framework to separate repositories
to make framework lightweight.
Now the question is how we are going to manage the repository structure for
third party integration codes. If we talk about payment gateways, we have
around 12 different integrations available in the framework component. If
we move them to plugins as a separate plugin, it will increase the number
of plugins in the plugin repository. I am personally not in favor of that.
We should have some type of repository categorization there. One
categorization I would like to suggest is to have separate repository all
together for third party integrations and to have a Gradle task to fetch
only required third party integration inside plugins directory as like we
have done for plugins repository itself:
apache -
-- ofbiz-framework
-- ofbiz-plugins
-- *ofbiz-thrid-party*
-- ofbiz-site
-- ofbiz-tools
I would like to invite thoughts on this so that we can proceed with the
migration of third party code out of the framework.
[1] https://issues.apache.org/jira/browse/OFBIZ-7415
Kind Regards,
--
Pritam Kute
