[JIRA] (JENKINS-50475) Scope import / Maven BOM dependencies
Title: Message Title Maxime Michel commented on JENKINS-50475 Re: Scope import / Maven BOM dependencies Thanks for giving it a shot & sorry it took time to respond. The reason why you want to trigger downstream builds in case of changes of snapshot BOM is scenarios where you add/remove dependencies or change dependency version in the snapshot BOM, correct? Yes. If a BOM change doesn't trigger downstream builds, then a library version introducing problems might be merged and go unnoticed for some time. Making them harder to pinpoint when they're caught. If the BOM pulls a snapshot dependency and if the snapshot dependency gets redeployed, then withMaven would detect it and trigger the downstream job, correct? There are no SNAPSHOT dependencies in our BOM, they're all 3rd party dependencies (think commons-lang3 for instance). They don't appear as dependencies in any of our downstream jobs' Maven dashboards. Our feature request is that a SNAPSHOT BOM build should trigger another of our build that imports the BOM (with a scope `import`). We'll dedicate some time to try to take your branch further ASAP. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from
[JIRA] (JENKINS-50475) Scope import / Maven BOM dependencies
Title: Message Title Cyrille Le Clerc commented on JENKINS-50475 Re: Scope import / Maven BOM dependencies Maxime Michel few questions to better understand please: the role of a Maven BOM is to define some dependencies that are pulled and to define the version of some other dependencies. The reason why you want to trigger downstream builds in case of changes of snapshot BOM is scenarios where you add/remove dependencies or change dependency version in the snapshot BOM, correct? If the BOM pulls a snapshot dependency and if the snapshot dependency gets redeployed, then withMaven would detect it and trigger the downstream job, correct? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50475) Scope import / Maven BOM dependencies
Title: Message Title Cyrille Le Clerc stopped work on JENKINS-50475 Change By: Cyrille Le Clerc Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50475) Scope import / Maven BOM dependencies
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-50475 Re: Scope import / Maven BOM dependencies [~mmichel] few questions to better understand please: the role of a Maven BOM is to define some dependencies that are pulled and to define the version of some other dependencies.The reason why you want to trigger downstream builds in case of changes of snapshot BOM is scenarios where you add/remove dependencies or change dependency version in the snapshot BOM, correct?If the BOM pulls a snapshot dependency and if the snapshot dependency gets redeployed, then withMaven would detect it and trigger the downstream job, correct? Note: I "stopped progress" as I don't know yet how to solve this problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50475) Scope import / Maven BOM dependencies
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-50475 Scope import / Maven BOM dependencies Change By: Cyrille Le Clerc Summary: Scope import / Maven BOM dependencies Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
