It seems to me that the groovy file could as easily be positioned in the
groovyScripts/facility/shipment folder in stead of creating a new folder
structure just for this, given that there are already lots of shipment
related groovy files in the aforementioned facility/shipment folder.
Met vriendelijke groet,
Pierre Smits
*Proud* *contributor** of* Apache OFBiz <
https://ofbiz.apache.org/> since
2008 (without privileges)
*Apache Trafodion <
https://trafodion.apache.org>, Vice President*
*Apache Directory <
https://directory.apache.org>, PMC Member*
Apache Incubator <
https://incubator.apache.org>, committer
Apache Steve <
https://steve.apache.org>, committer
On Tue, May 12, 2020 at 5:48 PM <
[hidden email]> wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> nmalin pushed a change to branch trunk
> in repository
https://gitbox.apache.org/repos/asf/ofbiz-framework.git.
>
>
> from 9eb6ba5 Improved: Converted all CustRequestItem related CRUD
> services from simple to entity-auto (#118)
> add 7fcde49 Improved: Convert ShipmentServices.xml mini lang to
> groovy (OFBIZ-11462)
>
> No new revisions were added by this update.
>
> Summary of changes:
> .../shipment/shipment/ShipmentServices.groovy | 1586
> +++++++++++++++++
> .../shipment/shipment/ShipmentServices.xml | 1840
> --------------------
> .../product/servicedef/services_shipment.xml | 116 +-
> 3 files changed, 1644 insertions(+), 1898 deletions(-)
> create mode 100644
> applications/product/groovyScripts/shipment/shipment/ShipmentServices.groovy
> delete mode 100644
> applications/product/minilang/shipment/shipment/ShipmentServices.xml
>
>