[
https://issues.apache.org/jira/browse/BEAM-6436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismaël Mejía updated BEAM-6436:
-------------------------------
Description:
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' by create an external maven project that uses
the dependency. It will not detect the latest one.
was:
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.
> 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' 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)
