[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue with publishing maven artefacts locally

I'm inclined to undo a particular modification I made in my PR and re-duplicate the repositories declaration between the Gradle plugin and the new BOM module. Scott, what do you think?

On Wed, Dec 12, 2018 at 11:00 AM Scott Wegner <scott@xxxxxxxxxx> wrote:
Thanks for pointing this out Alexy. This seems like we unintentionally broke something in PR#7197 [1]

+Garrett Jones, who authored the change. Garrett can you help investigate? 

I went to check to see if we have any existing Jenkins jobs that would've caught this break. It seems the beam_Release_Gradle_NightlySnapshot job [2] has been failing for the last 10 days. Has anybody looked into this?

On Wed, Dec 12, 2018 at 5:57 AM Alexey Romanenko <> wrote:
Hi all,

I used to publish maven artefacts into local repository using this kind of command for example:

./gradlew -Ppublishing --no-parallel -PdistMgmtSnapshotsUrl=file:///path/to/.m2/repository/ -p sdks/java/io/kafka/ publish

It worked fine till today. Seems like (according to "git bisect”) this recent commit [1] introduced new functionality and now it fails with an error:

* What went wrong:
A problem occurred configuring project ':beam-sdks-java-io-kafka'.
> Exception thrown while executing model rule: PublishingPluginRules#publishing(ExtensionContainer)
   > Cannot set the value of read-only property 'repositories' for object of type org.gradle.api.publish.internal.DeferredConfigurablePublishingExtension.

Does anyone know if this is a bug or I should use another command for the same purposes?