Packages uploaded via Gradle appear in the Group rather than the Project
Initially reported by a customer.
Maven packages (specifically snapshots) uploaded via Gradle appear under the parent Group's package listing via the UI, while the Project's package listing appears empty.
However, the package is shown within the project when listing packages via the Packages API.
Clicking on the package from the Group listing takes you to the package within the Project view.
This issue is not present when publishing a snapshot via Maven directly. When comparing the two uploaded snapshots in the
packages_packages table, it looks like the Gradle-uploaded package is not populating the
Steps to reproduce
Ensure gradle is installed and available on your system.
Fork the example project below into a group with a plan of Silver or above (optionally use the attached tar of the project)
valueparams within the
build.gradlefile to match your Project ID and personal access token respectively.
versiondefined in the
build.gradleis a snapshot - e.g.
gradle wrapperwithin the project's directory to generate the needed gradle wrapper files
Once the publish is completed successfully, check the available packages within your group and project.
What is the current bug behavior?
Packages do not appear in the UI via the Project's package listing, but instead the Group.
What is the expected correct behavior?
Packages appear within the Package's project listing.
Relevant logs and/or screenshots
See above screenshots.
Output of checks
This bug happens on GitLab.com.