You mean using gradle-wrapper's source instead of gradle-wrapper.jar? I never seen any project using gradle in that way.
Can we just exclude these jar file in release tarball, since I can remove them in release script( https://dist.apache.org/repos/dist/dev/incubator/weex/build_artifacts.sh). These won't take much effect. Then in the 'build' script(going to create one as john said, come along with a HOW-TO-BUILD doc), use curl to put them back. Is this properly in apache release? Todos before next release: * HOW-TO-BUILD doc. * RUN-RAT/HOW-TO-RELEASE doc. * A build script to generate both android/ios/js binaries. * Fix android project setup, to use same gradle version. On Wed, May 3, 2017 at 9:03 AM, Niclas Hedhman <[email protected]> wrote: > When testing the tarball just now, I got > > niclas@devdesk: > ~/temp/apache-weex-incubating-0.12.0-src/apache-weex- > incubating-0.12.0-src/android/weex_debug$ > ./gradlew build > Downloading https://services.gradle.org/distributions/gradle-2.2.1-bin.zip > > > * The tarball content has an extra level in it. Unnecessary. > * Gradle 2.14.1 is used in the other two android/ directories. > > Other work needed before next release; > > * I have started to replace gradle.jar in Gradle, and hope to have a > single Java source file instead that is being compiled first. And because > of that, I am arguing to allow the gradle.jar in RC3 release. For next > release, gradle.jar must go. > > Cheers > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
