A bit more debugging of the build file suggested that the ~/.gradle/gradle.properties file wasn't being used at all. Turns out my setup had the GRADLE_USER_HOME pointing to some other directory (I don't remember why I had set it up that way) and it was looking for the gradle.properties in that path instead of ~/.gradle folder.

I'll send a PR to the README.md of the project to add a note about this.


-Jaikiran

On Friday 09 September 2016 09:46 AM, Jaikiran Pai wrote:
I am trying to build Kafka 0.10 branch from source to get a SSL fix and use it for our internal tests. In order to use it internally in our application, we'll need these built artifacts to be published to our internal Maven repo (backed by Nexus). I build instructions in README.md says this:

### Publishing the jar for all version of Scala and for all projects to maven ###
    ./gradlew uploadArchivesAll

Please note for this to work you should create/update `~/.gradle/gradle.properties` and assign the following variables

    mavenUrl=
    mavenUsername=
    mavenPassword=
    signing.keyId=
    signing.password=
    signing.secretKeyRingFile=


I'm skipping signing of the artifacts and the command I use is:

./gradlew -PscalaVersion=2.11 uploadArchivesAll -x signArchives

My gradle.properties in ~/.gradle folder looks like:

mavenUrl=http://<IP>:<port>/content/repositories/snapshots
mavenUsername=name
mavenPassword=pass


This fails during the upload of archives during the build (the command that I pasted above):

.....
:kafka:core:uploadArchives FAILED
:uploadCoreArchives_2_10 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':core:uploadArchives'.
> Could not publish configuration 'archives'
> Failed to deploy artifacts/metadata: No connector available to access repository remote () of type default using the available factories WagonRepositoryConnectorFactory



Is my mavenUrl property wrong or is something else wrong? Could one of you who has successfully uploaded this, help me understand how to do it and what the mavenUrl should point to?


-Jaikiran


Reply via email to