You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2019/01/15 16:02:00 UTC
[jira] [Commented] (BEAM-6436) Gradle local SNAPSHOT publication is
not detected correctly by maven
[ https://issues.apache.org/jira/browse/BEAM-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743172#comment-16743172 ]
Ismaël Mejía commented on BEAM-6436:
------------------------------------
[~swegner] assigned to you since Luke is out at the moment.
> 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 these
> ./gradlew publishToMavenLocal -PisRelease --no-parallel -x test -p sdks/java/io/amazon-web-services
> 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' by create an external maven project that uses the dependency. It will not detect the latest one.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)