[ https://issues.apache.org/jira/browse/BEAM-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743436#comment-16743436 ]
Kenneth Knowles edited comment on BEAM-6436 at 1/15/19 10:06 PM: ----------------------------------------------------------------- I have been in this code a little bit. You should not pass the {{ -P isRelease}} flag. I'm not sure we should even have this flag. You can pass {{ -P publishing}} to enable the publishing plugin without triggering all the {{isRelease}} logic. I don't think you need {{--no-parallel}} any more. was (Author: kenn): I have been in this code a little bit. You should not pass the {{-P isRelease}} flag. I'm not sure we should even have this flag. You can pass {{-P publishing}} to enable the publishing plugin without triggering all the {{isRelease}} logic. I don't think you need {{--no-parallel}} any more. > 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)