[JAVA-3242] Embedded Android driver is picking up release candidates of org.mongodb:embedded-android Created: 20/Mar/19 Updated: 01/Apr/19 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Build, Embedded |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Consider using the technique described in https://stackoverflow.com/questions/24995517/how-to-use-gradles-dynamic-versions-and-avoid-betas#25029337 to work around the fact that Gradle is picking up releases like 4.0.7.-rc1. |
| Comments |
| Comment by Ross Lawley [ 21/Mar/19 ] |
|
I don't think this approach will work as well as we want, as the dependency is declared in the pom - so consumers of the dependency (either directly or indirectly) will consume the pom and rc's will be included. So the users of the library would need to express the dependency explicitly in their gradle to override our supplied range. Or we use something like this and it would set a single version as the dependency in the pom. Possibly requiring a release per downstream dependency release. |