> > if people think we do need to rename `org.jenkins-ci.main:jenkins-bom` > to `org.jenkins-ci.main:core-bom` then hving a consensus by 6th janurary > would be helpful,
For me plugin BOM artifactId is more confusing. I do not mind it being called "BOM", but the name is definitely confusing. On the other hand, we could include Core BOM dependencies into the "BOM" definition, so it would be less of a concern for end users On Tuesday, December 24, 2019 at 5:46:58 PM UTC+1, James Nord wrote: > > I'm not going to be working on this until the new year so if people think > we do need to rename `org.jenkins-ci.main:jenkins-bom` to ` > org.jenkins-ci.main:core-bom` then hving a consensus by 6th janurary > would be helpful, > > I do not think the plugin-bom should actually have "bom" in its name given > that it is not a bill of materials given nothing is every shipped with that > set of components, thus if renaming just changing that to something non bom > should remove the confusion. Happy holidays! > > /James > > On Monday, 23 December 2019 14:29:11 UTC, Oleg Nenashev wrote: >> >> Fine with me. >> Probably we should think about renaming components to "core-bom" and >> "plugin-bom" to stop creating confusion >> >> On Monday, December 23, 2019 at 1:50:19 PM UTC+1, James Nord wrote: >>> >>> Created >>> https://github.com/jenkins-infra/repository-permissions-updater/pull/1377 >>> <https://github.com/jenkins-infra/repository-permissions-updater/pull/1377/files> >>> >>> >>> On Wednesday, October 30, 2019 at 11:54:55 PM UTC, Mark Waite wrote: >>>> >>>> I definitely like the idea of retroactively available core BOM's >>>> >>>> On Wed, Oct 30, 2019 at 4:35 PM James Nord <[email protected]> wrote: >>>> >>>>> So I shall take silence as create a PR and be damned :) >>>>> >>>>> On Monday, October 21, 2019 at 7:04:37 PM UTC+1, Jesse Glick wrote: >>>>>> >>>>>> On Mon, Oct 21, 2019 at 7:51 AM Daniel Beck <[email protected]> >>>>>> wrote: >>>>>> > Isn't this what >>>>>> https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/ is for? >>>>>> >>>>>> No, James is discussing the core BOM which defines things like >>>>>> libraries that are dependencies of `jenkins-core`. `jenkinsci/bom` is >>>>>> complementary but focused on managing dependencies for use from >>>>>> plugins, especially dependencies on other plugins. >>>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Jenkins Developers" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/a1dd0ca9-f6dd-4110-979b-56972749522b%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/a1dd0ca9-f6dd-4110-979b-56972749522b%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> >>>> >>>> -- >>>> Thanks! >>>> Mark Waite >>>> >>> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/83120588-fac4-436f-9fac-b1e548f61850%40googlegroups.com.
