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

Use project configured groupId in generated output artifact names #7095

Merged

Conversation

SamCarlberg
Copy link
Member

Instead of hardcoding to use the project name after edu_wpi_first_, which broke epilogue publishing. Both projects publish to the edu.wpi.first.epilogue group ID, instead of the edu.wpi.first.epilogue-processor/runtime group IDs that were computed by the build script.

This bug did not affect local maven publishing, since those tasks do not use those specially named and configured artifacts

Instead of hardcoding to use the project name after edu_wpi_first, which broke epilogue publishing

This did not affect local maven publishing, since it does not use those specially named and configured artifacts
@SamCarlberg SamCarlberg added the build Monorepo organization, gradle/cmake, upstream_utils, etc label Sep 19, 2024
@SamCarlberg SamCarlberg requested a review from a team as a code owner September 19, 2024 02:16
@ThadHouse
Copy link
Member

Theoretically, this should work. Defintiely make sure the full combine task runs in the PR first.

ThadHouse
ThadHouse previously approved these changes Sep 19, 2024
@PeterJohnson PeterJohnson merged commit f1dde88 into wpilibsuite:main Sep 19, 2024
54 of 61 checks passed
@SamCarlberg SamCarlberg deleted the use-configured-group-id-in-outputs branch September 19, 2024 04:10
pjreiniger added a commit to bzlmodRio/allwpilib that referenced this pull request Sep 21, 2024
* Try to use composite action

* Try again

* Try with inputs

* Again

* Whoops

* [build] Update vendordeps frcyear to 2025 (wpilibsuite#7087)

* [build] Use project configured groupId in generated output artifact names (wpilibsuite#7095)

Instead of hardcoding to use the project name after edu_wpi_first, which broke epilogue publishing

This did not affect local maven publishing, since it does not use those specially named and configured artifacts

* Undo deletion

* Redo one delete

---------

Co-authored-by: sciencewhiz <[email protected]>
Co-authored-by: Sam Carlberg <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Monorepo organization, gradle/cmake, upstream_utils, etc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants