Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-21 Thread Pierre Smits
Thanks, I have adjusted https://issues.apache.org/jira/browse/OFBIZ-5464 accordingly. Best regards, Pierre Smits ORRTIZ.COM OFBiz based solutions & services OFBiz Extensions Marketplace http://oem.ofbizci.net/oci-2/ On Tue, Jun 21, 2016 at 7:13 AM, Jacopo Cappellato <

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Jacopo Cappellato
Hi Pierre, in order to avoid as much as possible to break the momentum of the work in the framework, I think we should follow the approach #1: migrate to Ivy only the three branches and let Taher and the community to complete the migration of the trunk to Gradle. Jacopo On Mon, Jun 20, 2016 at

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Pierre Smits
Jacopo, How do envision we approach this endeavour: - work on 3 separate integration paths for resp. 13.x, 14.x and 15.x, or - work on 1 integration path (on trunk) before the gradle approach will be brought in, then backport to the abovementioned branches, and subsequently phase out

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Jacopo Cappellato
Agreed, this is the plan we should follow; we should also port it to 15.12. Jacopo On Mon, Jun 20, 2016 at 5:07 PM, Pierre Smits wrote: > I suggest that we apply the IVY approach to the r14. branch as well, as > this is getting pushed further and further into the

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Pierre Smits
I suggest that we apply the IVY approach to the r14. branch as well, as this is getting pushed further and further into the future, with every new critical finding we happen to stumble upon and make a release from that branch available shortly after we have fixed the 13.x branch. Best regards,

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Pierre Smits
I will reopen that JIRA issue and set the applicable version to the r13.07 branch. Best regards, Pierre On Monday, June 20, 2016, Jacopo Cappellato < jacopo.cappell...@hotwaxsystems.com> wrote: > Yes, essentially we are proposing to implement in the currently active > release branches exactly

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Jacopo Cappellato
Yes, essentially we are proposing to implement in the currently active release branches exactly what you had already proposed in that Jira ticket. It took time but we ended up agreeing with your proposal :-) Jacopo On Mon, Jun 20, 2016 at 2:42 PM, Pierre Smits wrote: >

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Jacopo Cappellato
Great. I have also done some work in this direction that I am willing to contribute: https://github.com/jacopoc/ofbiz/tree/ivy I did this experiment on the trunk but I will be more than happy to migrate it to the 13.07 branch (since in the trunk is not needed if we move to Gradle); as you can

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Pierre Smits
Given that I have executed a full-fledged IVY integration as part of a PoC in relation to OFBiz-5464, I can revitalize that dev archive to help speed up the new release in the 13.07 branch. Best regards, Pierre On Monday, June 20, 2016, Pierre Smits wrote: > In order

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Pierre Smits
In order to help contributors to be well-informed I quote the appropriate section from previous mentioned thread here: *Re: maintainability* Over the past year several add-ons have been included in Ant build functions to use Apache Ivy as the engine to download jars required by specific

Re: Important Changes to Release 13.07 and Use of Ivy

2016-06-20 Thread Pierre Smits
Like I already suggested in my posting of Jan 5th in 2014 (see section 'Re: Maintainablity' in thread 'OFBiz in 2014 ( http://ofbiz.135035.n4.nabble.com/OFBiz-In-2014-tt4646641.html#a4646776). And for which I provided the JIRA issue , see https://issues.apache.org/jira/browse/OFBIZ-5464. Are we