Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Gradle fails to replace versions


Recommended Posts

In the build.gradle file I can define some things about my mod(id, version...).

I watched the code in the gradle file, and found out it is trying to replace ${version} in my mcmod.info file. I thought, if I change back the version in my mcmod.info file to ${version}, than gradle will place the correct version informations into it. I was right, but then I encountered a problem:

Gradle replaces the major and minor version numbers, but places always a zero to the build number. What do I do wrong, or is this behaviour expected?

try {


}catch(Throwable t) {

    MagicAppErrorSolver.solveProblem(t, this);


//Programmers will lose work

Link to comment
Share on other sites

Gradle doesn't have a concept of major or minor version numbers it jsut has a 'version' string. So whatever you're putting in that is what it'll use elseware.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Patreon: http://www.patreon.com/lexmanos
Paypal: http://paypal.me/LexManos

BitCoin: 1Q8rWvUNMM2T1ZfDaFeeYQyVXtYoeT6tTn

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.