Build Your own Groovy 2.3.8 release package from the source code

Source: Internet
Author: User


Today, in order to learn how to use groovy to write groovy's test code, we downloaded groovy 2.3.8 's source code package to Http://groovy.codehaus.org/Download.

Groovy uses Gradle as the building tool. First look at my local Gradle of the relevant environment:


>gradle-v------------------------------------------------------------gradle 2.2----------------------------- -------------------------------Build time:2014-11-10 13:31:44 utcbuild number:nonerevision: Aab8521f1fd9a3484cac18123a72bcfdeb7006ecgroovy:2.3.6ant:apache Ant (TM) version 1.9.3 compiled on December 2013jvm:1 .8.0_25 (Oracle Corporation 25.25-b02) os:windows 7 6.1 AMD64

Then I enter Gradle tasks in the source root directory after compression,

Gradle started downloading the required jar packages from Jcenter,

And then start compiling,

Finally, this error occurs:

Detected development environmentdeployment Environment set to Bintrayfailure:build failed with an exception.* Where:Scrip T ' H:\TDDownload\groovy-src-2.3.8\groovy-2.3.8\gradle\pomconfigurer.gradle ' line:10* what went wrong:a problem occurred evaluating script.> Could not the Find property ' groovy ' on the configuration container.* Try:run with--stacktrace op tion to get the stack trace. Run with--info or--debug option to get more log output. BUILD failedtotal time:5 mins 7.403 secs

I then ran again with the Gradle Tasks--info command, or the following error occurred:

Detected development environmentdeployment Environment set to Bintrayfailure:build failed with an exception.* Where:Scrip T ' H:\TDDownload\groovy-src-2.3.8\groovy-2.3.8\gradle\pomconfigurer.gradle ' line:10* what went wrong:a problem occurred evaluating script.> Could not the Find property ' groovy ' on the configuration container.* Try:run with--stacktrace op tion to get the stack trace. Run with--DEBUG option to get more log output. BUILD failedtotal time:7.911 secsstopped 0 Compiler daemon (s). Received result Daemoncommandresult[type=commandfailure, value=org.gradle.launcher.exec.reportedexception: Org.gradle.internal.exceptions.LocationAwareException:Script ' H:\TDDownload\groovy-src-2.3.8\groovy-2.3.8\ Gradle\pomconfigurer.gradle ' line:10a problem occurred evaluating script.] From Daemon daemoninfo{pid=7252, address=[65f71eaa-6377-4a8a-9370-d90fced0f265 port:50883, addresses:[/127.0.0.1,/ 0:0:0:0:0:0:0:1]], Idle=false, context=defaultdaemoncontext[uid=581b3403-93ac-4a93-bcd9-d5374bbb9a86, javahome=h:\programfiles\java\jdk1.8.0_25,daemonregistrydir=c:\users\chenjo\.gradle\daemon,pid=7252, idletimeout=120000,daemonopts=-xx:maxpermsize=196m,-xx:+cmsclassunloadingenabled,-xx:+ Cmspermgensweepingenabled,-xmx640m,-dfile.encoding=gbk,-duser.country=cn,-duser.language=zh,-duser.variant]}.

How to get around this mistake? Is it my Gradle version of the problem?


So I opened the file H:\TDDownload\groovy-src-2.3.8\groovy-2.3.8\README.adoc,

Found inside said:

To build everything using Gradle (the command below would download Gradle automatically, you don't need to download it fir ST).    . /gradlew Clean Dist

So I opened the command Line window to the source directory, type: Gradlew Clean Dist

I found that this command would first download a gradle-1.12-all to the local

C:\Users\chenjo\.gradle\wrapper\dists\gradle-1.12-all

Then compress and then download the jar package with that version and compile it, summarizing .... Although there were some warnings in the middle, or the network was blocked when I downloaded the jar, I interrupted the command several times and the last build succeeded.

Applying Javadoc fix tool (see HTTP://WWW.KB.CERT.ORG/VULS/ID/225657) to H:\TDDownload\groovy-src-2.3.8\ groovy-2.3.8\target\alljavadoc:doc:distdoc:distsrc:groovydoc:javadocapplying Javadoc Fix tool (see HTTP// www.kb.cert.org/vuls/id/225657) into H:\tddownload\groovy-src-2.3.8\groovy-2.3.8\target\docs\javadoc:syncdoc: Distbuild successfultotal time:18 mins 2.66 secs

Then I saw that the target folder was generated with more than 500 M bytes.

Under Project directory \target\distributions\, like the following generated publish file:

Groovy-binary-2.3.8.zip

Groovy-docs-2.3.8.zip

Groovy-sdk-2.3.8.zip

Groovy-src-2.3.8.zip


Build Your own Groovy 2.3.8 release package from the source code

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.