ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (Jira)" <j...@apache.org>
Subject [jira] [Created] (OFBIZ-11205) Move Groovy scripts from /groovyScripts/ to /src/main/groovy/
Date Fri, 20 Sep 2019 14:13:00 GMT
Jacques Le Roux created OFBIZ-11205:

             Summary: 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
             Fix For: Upcoming Branch

As mentioned in this discussion: https://markmail.org/message/2grqu63yvfpvxzz6

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.

[~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