[
https://issues.apache.org/jira/browse/BEAM-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743279#comment-16743279
]
Kenneth Knowles commented on BEAM-6436:
---------------------------------------
This may be related: when we switched to gradle it looks like we stopped having
the version be at SNAPSHOT all the time, but had it be a fixed version and only
append SNAPSHOT sometimes. I hit this when I was testing my vendored Guava
changes. I'd say it is a bug. The code at master should be permanently
SNAPSHOT. I am not sure gradle has the same rules about publishing this. My
understanding was that it was at publish time that SNAPSHOT was replaced by the
timestamp.
> 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)
