Hi Pierre, this is not what I said, please read what I wrote carefully: the release package (a source release) will not contain binary jars; the required jars (external dependencies) will be downloaded at build time by the user; in this process source files for the external dependencies are not required.
Jacopo On Thu, Jul 21, 2016 at 9:05 AM, Pierre Smits <[email protected]> wrote: > Jacopo, > > Are we talking binary releases (the convenient downloads) for our adopters? > > Because, according to conventions of the ASF, external libraries are not > allowed in our source release branches. And that is why we use the Gradle > solution and have download definitions. So that we don't have that > (external libraries) when we cut a release. > > Best regards,. > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ > > On Thu, Jul 21, 2016 at 8:17 AM, Jacopo Cappellato < > [email protected]> wrote: > > > This is very useful for development, thanks for sharing the tip Taher. > > However, it would be nice if we could configure this behavior in order to > > download only the required jars when a release is built: we should > explore > > this option as well. > > > > Jacopo > > > > On Thu, Jul 21, 2016 at 8:05 AM, Taher Alkhateeb < > > [email protected] > > > wrote: > > > > > Hi Everyone, > > > > > > One of the very nice things I discovered a while back is that Gradle > > > automatically downloads The Source libraries for the jar dependencies > for > > > almost all of the libraries. > > > > > > This means that you can ctrl-click with your IDE to navigate the source > > > code of these external libraries which I find very helpful for > debugging. > > > > > > So just wanted to share that for anyone who might want to take > advantage > > of > > > this > > > > > > Taher Alkhateeb > > > > > >
