-
Type:
Improvement
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: Trunk
-
Fix Version/s: Upcoming Branch
-
Component/s: ALL COMPONENTS
-
Labels:None
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 sourcesetsSo, 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.
Paul Foxworthy added
This will encourage and accelerate moving Java services to Groovy, I think.
And [~gil portenseigne]:
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.
- is depended upon by
-
OFBIZ-10226 Adds groovyScripts in the Gradle sourceSets
-
- Reopened
-