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 <pierre.sm...@gmail.com> 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 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, > > > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ > > On Mon, Jun 20, 2016 at 4:22 PM, Pierre Smits <pierre.sm...@gmail.com> > wrote: > > > 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 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 <pierre.sm...@gmail.com> > >> wrote: > >> > >> > 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 going to revisit that? > >> > > >> > Best regards, > >> > > >> > > >> > Pierre Smits > >> > > >> > ORRTIZ.COM <http://www.orrtiz.com> > >> > OFBiz based solutions & services > >> > > >> > OFBiz Extensions Marketplace > >> > http://oem.ofbizci.net/oci-2/ > >> > > >> > On Mon, Jun 20, 2016 at 2:06 PM, Sharan Foga <sharan.f...@gmail.com> > >> > wrote: > >> > > >> > > Hi Everyone > >> > > > >> > > There has been a bit of work going on in the background regarding > how > >> our > >> > > releases need to handle external dependencies. This is the first of > >> two > >> > > emails to let everyone know what has been happening and also to get > >> > > community feedback. > >> > > > >> > > While working on re-factoring the trunk dependencies we realised > that > >> our > >> > > current 13.07 release didn't meet the ASF guidelines for handling > >> > > dependencies. Essentially releases must only contain source code and > >> > should > >> > > not include external dependencies such as jar files. > >> > > > >> > > To resolve this as quickly and simply as possible, the PMC decided > to > >> use > >> > > Ivy (a dependency management tool) that is already included in OFBiz > >> to > >> > > manage the dependencies. > >> > > > >> > > So what will change? > >> > > > >> > > - When you download the OFBIz 13.07 release, it will only contain > >> source > >> > > code > >> > > - You will need to run a script to download the external OFBiz > >> dependent > >> > > files (e.g. jar files) > >> > > - You compile OFBiz as normal > >> > > > >> > > These changes will also need to be done in all our active release > >> > branches > >> > > (e.g. 14.12 and 15.12). > >> > > > >> > > We will also be communicating this change to our user mailing list > and > >> > > will be adding specific documentation to ensure that the everyone > >> > > understands how downloading and building OFBiz has changed. > >> > > > >> > > The next steps will be to implement this change and to get our next > >> 13.07 > >> > > release update out as soon as possible. > >> > > > >> > > Thanks > >> > > Sharan > >> > > > >> > > >> > > > > > > -- > > Pierre Smits > > > > ORRTIZ.COM <http://www.orrtiz.com> > > OFBiz based solutions & services > > > > OFBiz Extensions Marketplace > > http://oem.ofbizci.net/oci-2/ > > > > >
