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

Cherry pick changes to drop Java pom.xml files unused for release. #17728

Merged
merged 3 commits into from
Aug 5, 2024

Commits on Aug 5, 2024

  1. Refactor java maven GHA test to use our generated jars.

    This allows us to test our maven setup without relying on static `pom.xml` files and clears the way to remove them in a subsequent CL.
    
    PiperOrigin-RevId: 658057911
    deannagarcia authored and zhangskz committed Aug 5, 2024
    Configuration menu
    Copy the full SHA
    671ef8b View commit details
    Browse the repository at this point in the history
  2. Set -ex in test_java.yml

    This will cause the script to fail if any command fails, which will make it easier to debug failures.
    
    PiperOrigin-RevId: 658878371
    deannagarcia authored and zhangskz committed Aug 5, 2024
    Configuration menu
    Copy the full SHA
    6a7e215 View commit details
    Browse the repository at this point in the history
  3. Remove unused pom.xml files.

    We mostly use generated pom files in our release currently, so we can delete all the files that aren't used and the tools to update them.
    
    Note, java/bom/pom.xml java/pom.xml and java/protoc/pom.xml are all still used at release and java/kotlin/pom.xml is used for documentation so all of those need to stay for now.
    
    PiperOrigin-RevId: 659664012
    deannagarcia authored and zhangskz committed Aug 5, 2024
    Configuration menu
    Copy the full SHA
    aaf5f79 View commit details
    Browse the repository at this point in the history