[ https://issues.apache.org/jira/browse/BEAM-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744062#comment-16744062 ]
Ismaël Mejía commented on BEAM-6436: ------------------------------------ Thanks for the pointer to publishing, I will add this to the wiki documentation once fixed. Maybe [https://blog.packagecloud.io/eng/2017/03/09/how-does-a-maven-repository-work/] can shine some light on something we are doing wrong. Probably the SNAPSHOT -> Metadata section. > Gradle local SNAPSHOT publication is not detected correctly by maven > -------------------------------------------------------------------- > > Key: BEAM-6436 > URL: https://issues.apache.org/jira/browse/BEAM-6436 > Project: Beam > Issue Type: Sub-task > Components: build-system > Reporter: Ismaël Mejía > Assignee: Scott Wegner > Priority: Minor > > If you publish some Beam artifact locally e.g. like this: > ./gradlew publishToMavenLocal -PisRelease --no-parallel -x test -p > sdks/java/io/cassandra > It should publish a new artifact than should be detected correctly by maven. > However maven keeps detecting the latest artifact as the one published in > maven central. It seems gradle is missing some files or timestamp so it gets > detected correctly. > This can be reproduced 'easily' creating an external maven project that uses > the dependency. It will not detect the latest one published with gradle in > ~/.m2. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)