Open muhlba91 opened 1 month ago
Thanks for opening the issue, @muhlba91.
I believe it would make sense to set most, if not all, of these properties that are currently hard-coded only for Pulumi published packages.
Agreed. In some cases we can infer them, such as with the package name. Others, may require additional Java-specific values in the Pulumi schema.
What happened?
When publishing to Sonatype, I cannot close the staging repository and publish to public because of a Pom error.
Looking at the generated
build.gradle
file, I see thatpom.name = ""
which should ideally be the package name as for Pulumi published packages.Example
Output of
pulumi about
N/A
Additional context
This is related to https://github.com/pulumi/pulumi-java/blob/main/pkg/codegen/java/templates_gradle.go#L129-L136 where the project name, as well as other properties like the inception year, are only set for Pulumi published packages. For third-party publishers this needs to be set as well accordingly. I believe it would make sense to set most, if not all, of these properties that are currently hard-coded only for Pulumi published packages.
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).