diff --git a/plugins/index.html b/plugins/index.html index eaf1491..49f92ef 100644 --- a/plugins/index.html +++ b/plugins/index.html @@ -182,11 +182,75 @@ val a = assemble(kobalt) { +
+ The war
directive generates a war file suitable to be deployed into a servlet container.
+
+ The mavenJars
directive generates several jar files (binary, source, javadoc) which are required by Maven repositories. It's basically a shortcut that saves you the trouble from having to assemble these jar files manually in your build file. It allows you to specify Manifest attributes, just like the jar
directive.
+
+ The Publishing plug-in lets you upload files to JCenter. These files can be either generic ones (e.g. a zip file, a README, etc...) or a Maven-compatible form of your project.
+
+ Before you can upload, you need to create a file local.properties
in the root directory of your project with the following keys:
+
+bintray.user=... +bintray.apikey=... ++ +
+The values for the user
and apikey
keys can be found in your bintray profile, as described here. Add this file to your .gitignore
file and make sure you never upload it to your source contro.
+
+Before you can upload, you also need to create the package in bintray, as explained here. Once this is done, +you are ready to do your first upload. +
+ +
+ You define what to upload with the jcenter
directive:
+
+val jc = jcenter(kobalt) { + publish = true + file("${kobalt.buildDirectory}/libs/${kobalt.name}-${kobalt.version}.zip", + "${kobalt.name}/${kobalt.version}/${kobalt.name}-${kobalt.version}.zip") +} ++ +
+ The jcenter
directive accepts the following parameters:
+
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.
+ +$ ./kobaltw uploadJcenter +... +========== kobalt-line-count:uploadJcenter + kobalt-line-count: Found 2 artifacts to upload + All artifacts successfully uploaded ++ +