ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Smits (Jira)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-11205) Move Groovy scripts from /groovyScripts/ to /src/main/groovy/
Date Sun, 02 Feb 2020 14:51:00 GMT

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

Pierre Smits commented on OFBIZ-11205:

The latest comment by Mathieu highlights the differences between:
 # what is good for the project and its contributors
 # what is good for developers working for adopters
 # what is good for adopters regarding their OFBiz production infrastructure.

It is clear that while doing development (aspect 1 & 2) the parties involved do not want
to wait on compilation cycles. Hence the advantages of being able to see the effects of changes
in groovy scripts immediately (e.g. in the log or the browser).

On the other hand, adopters (the business using OFBiz as a strategic tool for their sustainability)
often have strict policies and procedures regarding running, deploying into and upgrading
the production environment. 
There aspects like performance and reliability are key, and drive who can perform specific

> Move Groovy scripts from /groovyScripts/ to /src/main/groovy/ 
> --------------------------------------------------------------
>                 Key: OFBIZ-11205
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11205
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>             Fix For: Upcoming Branch
> As mentioned in this discussion: https://markmail.org/message/2grqu63yvfpvxzz6
> {quote}
> Here is the (simple) plan:
> 1. We move all Groovy scripts from /groovyScripts/ to /src/main/groovy/
> 2. We add the necessary packages names
> 3. Devs can then open "gradlew --continuous" in a terminal and let it like that. It will
continuously build on any changes in Gradle sourcesets 
> So, if you modify a Groovy scripts while running an OFBiz instance, the changes will
be reflected in the instance and you can check possible syntax or alike issues in the terminal
running the continuous build. It's very fast since only changes have an impact on the build.
> I'm sure there are other benefits to follow "the common convention of putting groovy
compiled sources in ${COMPONENT}/src/main/groovy.", as suggested Mathieu.
> {quote}
> [~paulfoxworthy] added
> bq.  This will encourage and accelerate moving Java services to Groovy, I think.
> And [~gil portenseigne]:
> bq. The main advantage I see is, beside compilation, the integration in your IDE, that
was not optimum, and the possibility to re-use methods from these script migrated to explicit

This message was sent by Atlassian Jira

View raw message