Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Relocate maven artifacts and continue to support old names. #1865

Closed
wants to merge 3 commits into from

Conversation

ttosta-google
Copy link
Collaborator

@ttosta-google ttosta-google commented Feb 26, 2024

We are renaming the Maven artifacts to establish a consistent and memorable naming convention for our libraries, making it easier for customers to remember and associate with our libraries.

Example:

<groupId>com.google.cloud</groupId>
<artifactId>cloud-sql-connector-jdbc-postgres</artifactId>

We will continue to publish artifacts with the old names that include a warning to change to the new artifact name. This way we won't leave any customers behind as part of this process.

Example:

[WARNING] The artifact com.google.cloud.sql:postgres-socket-factory:jar:1.17.0 has been relocated to com.google.cloud:cloud-sql-connector-jdbc-postgres:jar:1.17.0: Please use the new artifact.

Fixes #1728

@ttosta-google ttosta-google force-pushed the gh-1728-update-maven-artifacts branch 2 times, most recently from 8cf86f5 to b0a4eab Compare February 26, 2024 15:48
@ttosta-google ttosta-google force-pushed the gh-1728-update-maven-artifacts branch from b0a4eab to 84607e2 Compare February 27, 2024 01:43
@hessjcg hessjcg deleted the gh-1728-update-maven-artifacts branch August 16, 2024 15:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update Maven Artifact Names and Descriptions
1 participant