ofbiz-notifications mailing list archives

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

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

Michael Brohl commented on OFBIZ-11205:
---------------------------------------

I wondered how it would work when you have all ressources (incl. Groovy scripts) build into
a single jar and deployed in an external appplication server to run it as it is planned for
the future and on the other hand want to use the continuous feature and be able to change
groovy scripts on-the-fly.

> 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
classes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message