[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478547#comment-16478547 ] Hans Bakker commented on OFBIZ-10407: - Yes we need newer copies of these filesor add a script to modify them as was done with entityrngine.properties.further the changeurl.sh was copied by accident and it is questionable if the change url part of initStart is required let first let the community decide if this is acceptable before we put more work in this,. > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478540#comment-16478540 ] Deepak Nigam commented on OFBIZ-10407: -- Thanks for the detailed information [~hansbak] . Now, cache.properties file is making some sense to me but if we talk about the trunk (in Dockerfile also, we are taking checkout from trunk), there is a change in theme pattern. So we should check the utility of widget.properties file once again. > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478390#comment-16478390 ] Shi Jinghai commented on OFBIZ-4274: Yes, swagger is suitable for api document. We're using swagger as api document. As trying to contribute a webpos2 component, I'm cleaning the api and translating the document into English. Our swagger doc in yaml format, it's more convenient than json format. We haven't used swagger as a validator until now. The only problem I met is on expressing OFBiz auth, I don't know how to define a http or https path in openapi spec. !swagger-pos-openapi.png! > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shi Jinghai updated OFBIZ-4274: --- Attachment: swagger-pos-openapi.png > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml, swagger-pos-openapi.png > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478370#comment-16478370 ] Hans Bakker commented on OFBIZ-10407: - I changed the priority to major, because installing demo systems (yes even the ofbiz dmo version) should be done with docker to follow these important software developments. Ofbiz also should , as all major open source systems do, provide an official docker image with every release. > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hans Bakker updated OFBIZ-10407: Priority: Major (was: Minor) > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Major > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478359#comment-16478359 ] Hans Bakker commented on OFBIZ-10407: - Thanks Deepak for your comments. Yes in GrowERP we are using OFBiz-16 and these files are enabling cache within ofbiz. It will copy these files into the ofbiz system when the dockerimage is starting up. This initial patch for ofbiz is welcoming comments as much as possible because docker not only is the choice for running a system in production but also to do OS independent software development. For your information we are using the docker-machine command to automatically install a docker environment on AWS on a 4 processor 16Gb instance en running 9 small ofbiz/growerp instances on it with excellent performance. examples: antwebsystems.com, productfromthailand,com growerp.com growerpdemo.com I think that the docker production environment is much better than the tenant function in OFBiz and that the tenant function should be removed. Regards, Hans > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Minor > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478111#comment-16478111 ] Mathieu Lirzin commented on OFBIZ-4274: --- Indeed to document REST APIs, OpenAPI specs are useful when used in combinaison of Swagger UI. Defining the routing and the spec in the same file similarly to what [https://camel.apache.org/swagger-java.html] does would be convenient. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478082#comment-16478082 ] Jacques Le Roux commented on OFBIZ-4274: Also I was wondering if https://swagger.io/ could not be of help in your work and its future. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16478079#comment-16478079 ] Jacques Le Roux commented on OFBIZ-4274: Hi Mathieu, This is very promising and Camel is certainly a good choice. BTW we have an [OFBizian|https://www.ofbizian.com/search/label/OFBiz] now part of the [Camel PMC|https://projects.apache.org/committee.html?camel] and still an [OFBiz PMC member|https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+PMC+Members+and+Committers] That could certainly help ;) [~bibryam] has also articles at http://camel.apache.org/articles.html and [GitHub|https://github.com/bibryam/ofbiz-camel]. This [article|http://www.ofbizian.com/2017/12/which-camel-dsl-to-choose-and-why.html] might be particularly interesting... HTH :) > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-4274) Implement a REST Servlet
[ https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477992#comment-16477992 ] Mathieu Lirzin commented on OFBIZ-4274: --- I have been [studying for a month|https://markmail.org/message/ulsnwg6vs53f5o5w] the various options to expose OFBiz services and entities as an HTTP REST API. The main parts of this endeavor consists in: * Defining a Domain Specific Language to associate routes to services. * Choosing a platform to handle the HTTP requests Existing Web frameworks (Juneau, CXF, Vert.x, ...) provide solutions for solving both aspects. However their DSL tend to not fit the XML configuration idiom of OFBiz, and are generally tied to a particular Language (Java, Groovy, ...). Moreover I am a bit reluctant to make OFBiz dependent on a particular framework which is not backed by a solid standard (like [JAX-RS|https://en.wikipedia.org/wiki/Java_API_for_RESTful_Web_Services]). Besides those web frameworks, I have discovered [Apache Camel|https://camel.apache.org/] which is a mature integration framework based on the patterns described in the excellent [Enterprise Integration Patterns|https://en.wikipedia.org/wiki/Enterprise_Integration_Patterns] book. Camel provides a [REST DSL|https://camel.apache.org/rest-dsl] which seems to fit OFBiz idioms nicely since it can be written both in XML and Java, and it handles generic endpoints. While in the long run I think It might be interesting to [integrate Camel within OFBiz|https://github.com/bibryam/ofbiz-camel] more deeply since it seems that integration of OFBiz with external solutions seems to be the norm (in my short experience), having to deal with its genericity would be a bit overwhelming for me. So what I am proposing here is to take inspiration from this REST DSL and adapt it to OFBiz. In term of infrastructure the HTTP routes will be served by a basic Java Servlet. Of course like every initial plan it will have to be reevaluated while implementing it. Suggestions and comments welcome. > Implement a REST Servlet > > > Key: OFBIZ-4274 > URL: https://issues.apache.org/jira/browse/OFBIZ-4274 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: Adrian Crum >Priority: Minor > Labels: REST > Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, > rest-conf.xml > > > Implement a REST servlet that will map REST requests to OFBiz services. > Details are in the comments. > [here is the discussion which took place on the dev > ML|http://markmail.org/message/ai6q2fbksowaayn4] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10370) Migrate promotion condition and action rule
[
https://issues.apache.org/jira/browse/OFBIZ-10370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477710#comment-16477710
]
Jacques Le Roux commented on OFBIZ-10370:
-
Hi Nicolas,
Don't be sorry, vacations are good, I'm still working in the garden. I must say
this year was peculiar, many issues like trees falling, etc. I still enjoy it :D
> Migrate promotion condition and action rule
> ---
>
> Key: OFBIZ-10370
> URL: https://issues.apache.org/jira/browse/OFBIZ-10370
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Major
> Attachments: OFBIZ-10370.patch
>
>
> Currently promotion rule engine works with :
> * entities ProductPromoCond et ProductPromoAction
> * java linear function ProductPromoWorker.checkCondition()
> (ProductPromoWorker:910) and ProductPromoWorker.performAction
> (ProductPromoWorker:1423)
> * Enumeration list to indicate on java function what piece of code to
> activate the control or action
> The problem with this structure is when you want to create a new case of
> condition or action, you need to modify the framework code base.
> We propose an other way with convert the 2 big java leaner function to
> service representation with one service by case.
> To realize it we introduce a relation with CustomMethod :
> ProductPromoRule --> ProductPromoCond -> CustomMethod
> \-> ProductPromoAction -> CustomMethod
> Each functions's case are converted to service with a related CustomMethod.
> With this pattern now you can write your own condition rule and action rule
> on your plugin and link it on the promo engine
> When it's possible we associate a unit test to the service
> For backware compatibility current enumeration receive on enumCode the
> customMethodId to ensure that old data work fine with the new engine
> {code}
> customMethodTypeId="PRODUCT_PROMO_COND"
> customMethodName="productPromoCondProductAmount" description="Product
> amount"/>
> enumCode="PPC_PRODUCT_AMOUNT"/>
> {code}
> {code}
> //for backware compatibility resolve customMethodId from enumCode
> GenericValue condEnum =
> EntityQuery.use(delegator).from("Enumeration").where("enumId",
> inputParamEnumId).cache().queryOne();
> if (condEnum != null) {
> customMethod =
> EntityQuery.use(delegator).from("CustomMethod").where("customMethodId",
> condEnum.get("enumCode")).cache().queryOne();
> serviceName = customMethod.getString("customMethodName");
> }
> {code}
> Related dev [discussion
> |https://lists.apache.org/thread.html/47730b60c9d1bab875e77577c2b4f16b99ede6dcdf68030f5cfc1203@%3Cdev.ofbiz.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10370) Migrate promotion condition and action rule
[
https://issues.apache.org/jira/browse/OFBIZ-10370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477578#comment-16477578
]
Nicolas Malin commented on OFBIZ-10370:
---
Hello Jacques, sry for the latency, I took some vacation :)
Thanks for your review, I will report your remark and will commit the patch
We use groovy because the main idea was to create small and easily readable
service what I think we've done.
an other step for more flexibility ^^
> Migrate promotion condition and action rule
> ---
>
> Key: OFBIZ-10370
> URL: https://issues.apache.org/jira/browse/OFBIZ-10370
> Project: OFBiz
> Issue Type: Improvement
> Components: product
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Major
> Attachments: OFBIZ-10370.patch
>
>
> Currently promotion rule engine works with :
> * entities ProductPromoCond et ProductPromoAction
> * java linear function ProductPromoWorker.checkCondition()
> (ProductPromoWorker:910) and ProductPromoWorker.performAction
> (ProductPromoWorker:1423)
> * Enumeration list to indicate on java function what piece of code to
> activate the control or action
> The problem with this structure is when you want to create a new case of
> condition or action, you need to modify the framework code base.
> We propose an other way with convert the 2 big java leaner function to
> service representation with one service by case.
> To realize it we introduce a relation with CustomMethod :
> ProductPromoRule --> ProductPromoCond -> CustomMethod
> \-> ProductPromoAction -> CustomMethod
> Each functions's case are converted to service with a related CustomMethod.
> With this pattern now you can write your own condition rule and action rule
> on your plugin and link it on the promo engine
> When it's possible we associate a unit test to the service
> For backware compatibility current enumeration receive on enumCode the
> customMethodId to ensure that old data work fine with the new engine
> {code}
> customMethodTypeId="PRODUCT_PROMO_COND"
> customMethodName="productPromoCondProductAmount" description="Product
> amount"/>
> enumCode="PPC_PRODUCT_AMOUNT"/>
> {code}
> {code}
> //for backware compatibility resolve customMethodId from enumCode
> GenericValue condEnum =
> EntityQuery.use(delegator).from("Enumeration").where("enumId",
> inputParamEnumId).cache().queryOne();
> if (condEnum != null) {
> customMethod =
> EntityQuery.use(delegator).from("CustomMethod").where("customMethodId",
> condEnum.get("enumCode")).cache().queryOne();
> serviceName = customMethod.getString("customMethodName");
> }
> {code}
> Related dev [discussion
> |https://lists.apache.org/thread.html/47730b60c9d1bab875e77577c2b4f16b99ede6dcdf68030f5cfc1203@%3Cdev.ofbiz.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10407) create a docker image from the ofbiz system
[ https://issues.apache.org/jira/browse/OFBIZ-10407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477255#comment-16477255 ] Deepak Nigam commented on OFBIZ-10407: -- Hi [~hansbak], thanks for taking the step towards dockerization of OFbiz. I am able to setup OFBiz on my local machine by the running the docker command provided by you. I reviewed the docker.patch also. In this, Dockerfile and other scripts are looking good to me, but I didn't understand the utility of cache.properties and widget.properties files. It seems these are from an older version of OFBiz. Can you please provide some information about the utility of these properties in this dockerization effort? > create a docker image from the ofbiz system > --- > > Key: OFBIZ-10407 > URL: https://issues.apache.org/jira/browse/OFBIZ-10407 > Project: OFBiz > Issue Type: Improvement >Reporter: Hans Bakker >Priority: Minor > Attachments: docker.patch > > > Attached an initial docker version from OFBiz copied from our GrowERP > production system translated to svn repositories. > I propose to create a docker directory in the ofbiz framework root of which a > patch is attached. > The image result is stored in hub.docker.com under the name ofbiz/full-trunk. > It can be started in a docker environment with the following command: > docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk > and after about 30 seconds it can be show in the browser under: > [https://0.0.0.0/catalog/control/main] > > the image can be created by executing this command in the ofbiz root when the > patch is applied: > docker build -t ofbiz/full-trunk docker > the password to the ofbiz account at hub.docker.com will be supplied upon > request. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (OFBIZ-10407) create a docker image from the ofbiz system
Hans Bakker created OFBIZ-10407: --- Summary: create a docker image from the ofbiz system Key: OFBIZ-10407 URL: https://issues.apache.org/jira/browse/OFBIZ-10407 Project: OFBiz Issue Type: Improvement Reporter: Hans Bakker Attachments: docker.patch Attached an initial docker version from OFBiz copied from our GrowERP production system translated to svn repositories. I propose to create a docker directory in the ofbiz framework root of which a patch is attached. The image result is stored in hub.docker.com under the name ofbiz/full-trunk. It can be started in a docker environment with the following command: docker run -p 80:8080 -p 443:8443 ofbiz/full-trunk and after about 30 seconds it can be show in the browser under: [https://0.0.0.0/catalog/control/main] the image can be created by executing this command in the ofbiz root when the patch is applied: docker build -t ofbiz/full-trunk docker the password to the ofbiz account at hub.docker.com will be supplied upon request. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
