[JAVA-4854] Update 3.12 Maven Text Created: 23/Jan/23 Updated: 28/Oct/23 Resolved: 03/Feb/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | 3.12.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ashni Mehta | Assignee: | Ross Lawley |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
The top-ranking Google result for "mongodb java driver maven" is mongo-java-driver on Maven (3.12.x). Unfortunately, there is no way for a user to deduce that 3.12.x is actually several versions behind the most recent release, as there is no link to mongodb-driver-sync. We've seen this happen with users in the past (see this community forums post as an example). Can we update the text on that page (right below the artifact name) to: "This artifact is not the most recent release of the MongoDB Java Driver. To use the most recent release of the MongoDB Java Driver, please use mongodb-driver-sync instead." If it is possible to update the last bit of text to link to mongodb-driver-sync, that would be ideal. We can also update the "pomName" to something like "MongoDB Legacy Java Driver" https://github.com/mongodb/mongo-java-driver/blob/3.12.x/mongo-java-driver/build.gradle#L19 |
| Comments |
| Comment by Githook User [ 03/Feb/23 ] |
|
Author: {'name': 'Ross Lawley', 'email': 'ross.lawley@gmail.com', 'username': 'rozza'}Message: Update the legacy uber packages pom.xml Update the name and description to indicate these are legacy
|
| Comment by Ross Lawley [ 01/Feb/23 ] |
Could not see any reason from the poms, so have contacted mvnrepository to get it categorized. Ross |
| Comment by Jeffrey Yemin [ 30/Jan/23 ] |
|
Why isn't https://mvnrepository.com/artifact/org.mongodb/mongodb-driver-reactivestreams even showing up as a "MongoDB Client"? |