You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: INTERNAL.md
-25Lines changed: 0 additions & 25 deletions
Original file line number
Diff line number
Diff line change
@@ -10,33 +10,8 @@ The following properties should be set locally in the `local.properties` file in
10
10
| ---------------------- | ----- |
11
11
| gradle.publish.key | Gradle API key. Required when publishing to the Gradle Plugin Portal using the `plugin-publish` plugin. |
12
12
| gradle.publish.secret | Gradle API secret. Required when publishing to the Gradle Plugin Portal using the `plugin-publish` plugin. |
13
-
| maven.repo.username | Maven repository username. Required when publishing to Maven repository using the `maven-publish` plugin. |
14
-
| maven.repo.password | Maven repository password. Required when publishing to Maven repository using the `maven-publish` plugin. |
15
-
| maven.signing.key | ASCII armored secret key. Required to sign the artifact using the `maven-publish` plugin. |
16
-
| maven.signing.password | Passphrase of the secret key. Required to sign the artifact using the `maven-publish` plugin. |
17
13
18
14
# Publishing
19
15
20
16
To publish a new version of the plugin to the plugin repositories, bump the `version` property in `build.gradle.kts` and run:
21
17
-`publishPlugins` to upload the plugin to Gradle Plugin Repository,
22
-
-`publishPluginPublicationToMavenRepository` to upload the plugin to Maven Central Repository.
23
-
24
-
# Pre-release tests
25
-
26
-
Testing changes before publishing built artifacts to the repositories can be done by uploading a snapshot version of the plugin.
27
-
To do so, add `-SNAPSHOT` suffix to the next release version and upload it to Maven repository with the `publishPluginPublicationToMavenRepository` Gradle task.
28
-
29
-
In the test project, configure the plugin using the legacy `apply` method as shown below:
0 commit comments