ysb33r / bintray Goto Github PK

Currently packages need to be created by hand on Bintray before uploading a version. It would be nice to be automatially do this. Adding an optional property autoCreatePackage would be good, but it needs to default to false for backwards compatility.

There is an issue whereby signing of packages happen before packages are uploaded.

Need to be able to support the new maven-publish plugin.

Add an option to Maven/Ivy & Generic Uploads to auto-sign upon upload.

See https://bintray.com/docs/api.html#_signing for REST API

Hi there,
I'm having the following problem trying to use the uploadArchives task:

What went wrong:
Execution failed for task ':XYZ-services:uploadArchives'.
Could not find property 'bintray' on task ':XYZ-services:uploadArchives'.

classpath 'org.ysb33r.gradle:bintray:1.3'

Relevant code:

import org.ysb33r.gradle.bintray.BintrayGenericUpload

apply plugin: 'java'
apply plugin : 'bintray-publish'

task uploadArchives (type: BintrayGenericUpload) {
    username    'username'
    apiKey      'somekey'
    repoOwner   'someOrg'
    repoName    'binaries'
    packageName 'my-package'
    version      '0.9.2'
    // 'sources' can be called more than once
    sources "${buildDir}/libs/${project.name}.jar"
}

if I use org.ysb33r.gradle:bintray:1.2 I don't have this error (I cannot upload either...). Looking at the code, I'm not seeing where the bintray variable/property is declared in the code:
https://github.com/ysb33r/bintray/blob/master/gradle-plugin/src/main/groovy/org/ysb33r/gradle/bintray/BintrayGenericUpload.groovy#L140

Can you check it please?
Thank you!

Package creation fails due to

• Caused by: java.lang.IllegalArgumentException: argument type mismatch
• Caused by: groovy.lang.MissingPropertyException: No such property: vsUrl for class: org.ysb33r.gradle.bintray.BintrayAPI

https://bintray.com/docs/api/#_entitlements

This library is great. Would like to be able to get and create entitlements and download keys with it.

Ability to upload snaphots to oss.jfrog.

Currently this needs to be done via manually crafting tasks and using Artifactory.

Curretnly the package directory has to be created manually on the Bintray website before versioned packages can be uploaded.

Currenly one has to setup special Artiectory tasks to do this. It will be nice it it can be set up more transparently by extending bintrayMavenDeployer i.e.

bintrayMavenDeployer {
  username    'someBintrayUser'
  apiKey      'SomeBintrayUsersApiKey'
  repoOwner   'ysb33r'
  repoName    'grysb33r'
  packageName 'someNewPackageToBePublished'
  description 'This is an example to simplifying bintray publishing'
  descUrl     'https://github.com/ysb33r/Gradle/blob/master/bintray/README.md'
  tags        'gradle','bintray'
  // Adding this property which will default to false (for backwards compatibility)
  publishSnapshotsToOssJFrog true
  // Adding an optional key which will default to 'oss-snapshot-local'
  // Will be ignored if publishSnapshotsToOssJFrog is false
  snapshotKey 'oss-snapshot-local'
 }```

Needs to be able to support ivy-publish plugin.

Have the option of calculating and uploading MD5s as part of the Generic Repository upload process.

A md5 property is recommended, defaulting to true

Also adding sha1 and sha256, defaulting to false would be good.

Similar to what has been done for Maven repositories in 1.4.

Currenlt one has to go to Bintray to publish artefacts after they have been upload. there is definite a quality benefit in this manual step, but it would still be nice if it was possible to auto-publish under certain circumstances.

Adding an optional autoPublish property would be great, but it should default to false for backwards compatibility.

Change id from bintray-publish to org.ysb33r.bintray

I inherited a project that is using your bintray client. All of the groovy code written is using log4j loggers that are created when the class is instantiated. Is there a way to capture the bintray client and httpbuilder logging into this same log? My end goal is that the logging is setup in my jar when deployed to a remote system. That system is having issues but I cannot get any of the log details from the client currently.