xaviertalpe / gradle-release-plugin Goto Github PK

See http://plugins.gradle.org/submit

Currently only gradle.properties files will get updated/committed when updating the version property. Once we have an optimized approach to update the gradle.properties file, we might be able to make a similar change to update the build.gradle file.

Also see finalizer tasks:

• http://www.gradle.org/docs/current/userguide/more_about_tasks.html

• nextVersion
• username
• password

In case a project has a SNAPSHOT dependency, the release should be halted.

• Explain how to import the plugin into the project.
• Minimum Gradle version
• Provide a clear description of the various tasks
• Describe the current functionality

Currently only the gradle.properties file is supported. This should be extended to allow for a custom properties file, e.g. version.properties.

Pushing over SSH currently throws an exception because the USERAUTH failed (jGit).

Currently the commits to the SCM are using the system username/password.

It would be useful to allow users to explicitly specify the credentials to use:

release {
    scmUsername = 'user'
    scmPassword = 'password'
}

Both for prepareRelease, prepareNextRelease task.

When moving from a 1.2.0-SNAPSHOT to a 2.0.0-SNAPSHOT release, it can be useful if the user can pass in the 2.0.0-SNAPSHOT value from the command line (-PnextVersion=XXX). Otherwise, the user will have to manually change the 1.2.1-SNAPSHOT version in the gradle.properties file.

In the case of parameterized CI builds, the actual version to use for the release might also be used as input. We could probably use the existing -Pversion for that, but we need to test whether everything works correctly in that case.