From b8512f073c1a75f1bf709a9fdf7cf4cbcdb82bfc Mon Sep 17 00:00:00 2001 From: Cedric Beust Date: Fri, 8 Jan 2016 23:39:12 +0400 Subject: [PATCH] JCenter -> Bintray. --- documentation/index.html | 6 +++--- home/index.html | 4 ++-- plug-ins/index.html | 18 +++++++++--------- ten-minutes/index.html | 26 +++++++++++++------------- 4 files changed, 27 insertions(+), 27 deletions(-) diff --git a/documentation/index.html b/documentation/index.html index e840e2c..f598ddd 100644 --- a/documentation/index.html +++ b/documentation/index.html @@ -294,7 +294,7 @@ $ ./kobaltw --tasks ===== publish ===== generatePom Generate the .pom file - uploadJcenter Upload the artifacts to JCenter + uploadBintray Upload the artifacts to Bintray ===== packaging ===== assemble Package the artifacts @@ -320,7 +320,7 @@ $ ./kobaltw --tasks ===== publish ===== generatePom Generate the .pom file - uploadJcenter Upload the artifacts to JCenter + uploadBintray Upload the artifacts to Bintray ===== kobalt-example-plugin ===== coverage Run coverage @@ -457,7 +457,7 @@ New versions found:

Publishing

-Kobalt supports JCenter natively so you can upload your project and make it available on JCenter very easily. +Kobalt supports Bintray/JCenter natively so making your projects available there is very easy.

diff --git a/home/index.html b/home/index.html index a679845..28d7d43 100644 --- a/home/index.html +++ b/home/index.html @@ -96,14 +96,14 @@ val jcommander = javaProject { } } - jcenter { + bintray { publish = false } }

- This build file also includes a directive to upload your artifacts to JCenter automatically. + This build file also includes a directive to upload your artifacts to Bintray automatically.

Design goals

diff --git a/plug-ins/index.html b/plug-ins/index.html index bae4b45..983933b 100644 --- a/plug-ins/index.html +++ b/plug-ins/index.html @@ -388,10 +388,10 @@ assemble {

Publishing

- The Publishing plug-in lets you upload files to JCenter and Github. These files can be either generic ones (e.g. a zip file, a README, etc...) or a Maven-compatible form of your project. + The Publishing plug-in lets you upload files to Bintray and Github. These files can be either generic ones (e.g. a zip file, a README, etc...) or a Maven-compatible form of your project.

-

JCenter

+

Bintray / JCenter

Before you can upload, you need to create a file local.properties in the root directory of your project with the following keys:

@@ -414,11 +414,11 @@ you are ready to do your first upload.

- You define what to upload with the jcenter directive: + You define what to upload with the bintray directive: 

-jcenter {
+bintray {
   publish = true
   file("${kobalt.buildDirectory}/libs/${kobalt.name}-${kobalt.version}.zip",
        "${kobalt.name}/${kobalt.version}/${kobalt.name}-${kobalt.version}.zip")
@@ -431,15 +431,15 @@ jcenter {
   mavenJars {}

- This directive is described here and is a shortcut to upload all the files that are required in a Maven repo (jar file, javadocs, source files and POM file). You can take a look at this build file for a full example of how to package and publish a project to JCenter. + This directive is described here and is a shortcut to upload all the files that are required in a Maven repo (jar file, javadocs, source files and POM file). You can take a look at this build file for a full example of how to package and publish a project to Bintray / JCenter.

- The jcenter directive accepts the following parameters: + The bintray directive accepts the following parameters:

publish (false)
-
If true, the uploaded file will be published in your personal space (e.g. https://dl.bintray.com/cbeust/maven). Once the file is uploaded there, it can be automatically synchronized to JCenter by linking your project to JCenter on the bintray web site. By default, files are not published. +
If true, the uploaded file will be published in your personal space (e.g. https://dl.bintray.com/cbeust/maven). Once the file is uploaded there, it can be automatically synchronized to JCenter by linking your project to JCenter on the Bintray web site. By default, files are not published.
sign (false)
If true, sign the files with GPG. This is only required if you plan to later synchronize these files from JCenter to Maven Central. Keep this to falseif you are only interested in uploading to JCenter.
@@ -448,9 +448,9 @@ jcenter { 
-$ ./kobaltw uploadJcenter
+$ ./kobaltw uploadBintray
 ...
-========== kobalt-line-count:uploadJcenter
+========== kobalt-line-count:uploadBintray
   kobalt-line-count: Found 2 artifacts to upload
   All artifacts successfully uploaded
diff --git a/ten-minutes/index.html b/ten-minutes/index.html index 7c1e488..6a40309 100644 --- a/ten-minutes/index.html +++ b/ten-minutes/index.html @@ -152,9 +152,9 @@ public class Main : BasePlugin() { 

-$ ./kobaltw uploadJcenter
+$ ./kobaltw uploadBintray
 ...
-========== kobalt-line-count:uploadJcenter
+========== kobalt-line-count:uploadBintray
   Found 12 artifacts to upload:
     Uploading 12 / 12 |............|
 BUILD SUCCESSFUL (15 seconds)
@@ -165,7 +165,7 @@ BUILD SUCCESSFUL (15 seconds)
 

 
 
-jcenter {
+bintray {
     publish = true
 }
 

@@ -206,19 +206,19 @@ public class Main : BasePlugin() {

- Let's bump our version to 0.2 (since version 0.1 is already uploaded and JCenter won't allow us to overwrite it) and upload our new plug-in: + Let's bump our version to 0.2 (since version 0.1 is already uploaded and Bintray won't allow us to overwrite it) and upload our new plug-in: 

-$ ./kobaltw uploadJcenter
+$ ./kobaltw uploadBintray
 ...
 kobalt-line-count: Compilation succeeded
 ========== kobalt-line-count:assemble
 Created /Users/beust/kotlin/kobalt-line-count/kobaltBuild/libs/kobalt-line-count-0.2.jar
 ========== kobalt-line-count:generatePom
  Wrote /Users/beust/kotlin/kobalt-line-count/kobaltBuild/libs/kobalt-line-count-0.2.pom
-========== kobalt-line-count:uploadJcenter
+========== kobalt-line-count:uploadBintray
   Found 12 artifacts to upload:
     Uploading 12 / 12 |............|
 BUILD SUCCESSFUL (15 seconds)
@@ -259,7 +259,7 @@ Found 4972 lines in 65 files

- And that's it! You can now iterate on your plug-in and upload it with additional ./kobaltw uploadJcenter. This plug-in is available on github. Note that the plug-in in the repo + And that's it! You can now iterate on your plug-in and upload it with additional ./kobaltw uploadBintray. This plug-in is available on github. Note that the plug-in in the repo illustrates a few other concepts not discussed here, such as adding dynamic tasks, so I encourage you take a look at its source.

@@ -295,12 +295,12 @@ public class Main : BasePlugin() { Now you can simply create a launch configuration for your main class, which will invoke Kobalt.

-

- The next step is to have Kobalt invoke your plug-in, so you will have to modify your build file - to call it. As long as you haven't deployed your plug-in to JCenter, you might want to use the - file() directive to declare your dependency, so that Kobalt will use the jar file - on your file system: -

+

+ The next step is to have Kobalt invoke your plug-in, so you will have to modify your build file + to call it. As long as you haven't deployed your plug-in to Bintray, you might want to use the + file() directive to declare your dependency, so that Kobalt will use the jar file + on your file system: +

 val p = plugins(