-
Notifications
You must be signed in to change notification settings - Fork 354
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
feat: Support graphql-kotlin-bom #2022
Conversation
url.set("https://github.com/ExpediaGroup/graphql-kotlin") | ||
licenses { | ||
license { | ||
name.set("The Apache Software License, Version 2.0") | ||
url.set("http://www.apache.org/licenses/LICENSE-2.0.txt") | ||
} | ||
} | ||
organization { | ||
name.set("Expedia Group") | ||
name.set("https://www.expediagroup.com/") | ||
} | ||
developers { | ||
developer { | ||
name.set("Expedia Group Committers") | ||
email.set("[email protected]") | ||
organization.set("Expedia Group") | ||
organizationUrl.set("https://www.expediagroup.com/") | ||
} | ||
} | ||
scm { | ||
connection.set("scm:git:git://github.com/ExpediaGroup/graphql-kotlin.git") | ||
developerConnection.set("scm:git:git://github.com/ExpediaGroup/graphql-kotlin.git") | ||
url.set("https://github.com/ExpediaGroup/graphql-kotlin") | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are defined in com.expediagroup.graphql.conventions.gradle.kts and other java modules are using id("com.expediagroup.graphql.conventions")
plugin. But that plugin is for java libraries, not applicable for this BOM. copy-create with pom
packaging.
Whats the point/value of the platform jar/bom for this OSS project?
|
@dariuszkuc Applications may need multiple modules. For instance, GraphQL server apps, at least at EG, use server, client for integration test and maven-plugin to generate SDL in common. Also if a team develops a parent POM for other devs, then for instance, server parent POM may include both ktor and spring, and client parent POM may include ktor, spring, serialization or jackson so that app developers can choose whichever server/client module they want. These can be wrapped up in the parent POM but BOM seems to be a better place. Also I thought it's a good practice to provide a BOM in general when there are many modules in the project, 20+ modules here. |
If you are keen on creating the platform/bom then I'd suggest to also make it more useful to also specify some required dependency versions (e.g. *also a side note -> BOMs won't help with plugin management |
It seems that the usage of |
📝 Description
Adding a support on
graphql-kotlin-bom
Generated BOM looks like this:
🔗 Related Issues