|Maybe my answer is not 100% relevant to initial topic (sorry for that in advance) but it took me quite a time to find out how to properly install artefacts into local maven repository with gradle.|
Finally, I came to this command (additional flags are skipped for the sake of simplicity).
For example,I used this command to publish KinesisIO artifacts on local maven to test my changes against external Beam-based application:
Not sure, if this way is fully correct, but, at least, it's worked for me =)
I think it has to be -PisRelease=false (otherwise the publish task isn't activated).
I'm now looking for a good way to allow skipping gpg (when the version isn't -SNAPSHOT). Currently, it will run whenever the isRelease property is present.
On Wed, Aug 15, 2018 at 4:42 AM Jean-Baptiste Onofré <jb@xxxxxxxxxxxx
yes, I did on a local Nexus repository.
Did you try with -DisRelease=false ?
On 15/08/2018 07:54, Thomas Weise wrote:
> I wanted to see if anyone has used the Gradle build to publish the
> release/snapshot artifacts to custom repo?
> So far I found the following (attempting to publish a particular Maven
> ./gradlew :beam-runners-flink_2.11-job-server:publish -Ppublishing
> --no-parallel --no-daemon
> It gets to the point of attempting deploy to the remote repo, but fails
> due to hardcoded server IDs:
> When the version isn't -SNAPSHOT, then I guess it would instead be
> -PisRelease, the build will fail because it expects gpg to run, which I
> don't need for what I'm trying to do.
> Have others attempted third party builds for the Python SDK or Docker
> images? Any gotchas to share?
Talend - http://www.talend.com