That's all good, thanks Taher!
I'd really want to close all the remaining tasks related to our migration from Ant to Gradle and to close the parent task OFBIZ-7534 "Migrate OFBiz
from Apache Ant to Gradle build system"
After transforming OFBIZ-7963 "Create a Gradle Sonar task" from a OFBIZ-7534
subtask to a main task, remain 2 subtasks
"Migrate the patch management Ant targets
<https://issues.apache.org/jira/browse/OFBIZ-7962>"
and
Update documentation with respect to implementation of gradle as a replacement of ant
<https://issues.apache.org/jira/browse/OFBIZ-7677>
The last depends on the 1st because we both need to fix the createComponent
task and then complete the related documentation at
https://cwiki.apache.org/confluence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz#AddressingCustomRequirementsInOFBiz-PatchManagementUsingGradleTargets
I think it's time to take some decisions and get rid of the past when it
becomes useless.
For that though, I'd like to have the community opinions.
Mine is the 4 targets, to create/apply/reapply/revert patches can be abandoned.
We did not migrate them to Gradle and nobody complained.
Same for the specialpurpose\plugin\patches and subdir created by the
createPlugin task. They are useless w/o the 4 targets above and could be
confusing.
So also the related documentation in wiki can be pruned.
I'm a bit more reluctant for the 4 deployment targets I created in 2014 to supersede the above 4 targets. Those are still existing in the R15.12
branch and we can ever call Ant from Gradle.
So I'll simply document in the page above how to retrieve and use them in
R16.11.01 and future releases based on the R15.12 branch
There is also the runtime\patches dir and its README file. I'll keep them and actually create the documentation I just spoke about using a README.MD
file as we do at
https://cwiki.apache.org/confluence/display/OFBIZ/From+Ant+to+Gradle
I'll then close the 2 subtasks and OFBIZ-7534
Jacques
Le 30/12/2016 à 10:47, Taher Alkhateeb a écrit :
Thank you folks for your feedback.
Gradle upgraded to version 3.2.1 in r1776532 under issue
https://issues.apache.org/jira/browse/OFBIZ-9160. Next we need to upgrade
buildbot gradle version
On Wed, Dec 28, 2016 at 12:02 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
Le 27/12/2016 à 21:45, Taher Alkhateeb a écrit :
Hello everyone,
I've upgraded gradle to version 3.2.1 on my machine and tested most
functionality which seems to be operating well. The experience is pleasant
because by default version 3+ automatically starts the gradle daemon which
makes the build system much faster among other things. They deprecated the
shift operator "<<" but it still works and we can refactor that later.
We might need some work on buildbot to upgrade the version, but other than
that it seems to be a smooth experience.
What do you think? Is it a good time to upgrade?
Taher Alkhateeb
+1 since it's possible to not start the Gradle daemon (proved to be an
issue with demos) with |--no-daemon |option
https://docs.gradle.org/current/userguide/troubleshooting.html
For Builbot we just need to ask the infra team to upgrade Gradle, we did
thathttps://issues.apache.org/jira/browse/INFRA-12235
Jacques
