> > I would be pleased to start a page called Maven Enforcer FAQs and do my best > to put in an explanation.
I think starting a wiki page would be a good idea, this is something that happens quite often now. It would be good if we can provide some patterns on how to solve such a problem. E.g., what should one do if there is such an error in two depending plugins (or libraries) (and not in your own code)? Define an exclusion in the dependencies? Or add an exclusion in requireUpperBoundDeps of the enforcer? > Or, is there a better approach? I'd be glad to do something to help out the > next person who is stuck. > > Mike > > > On 2018-01-06 01:33 AM, Daniel Beck wrote: >>> On 6. Jan 2018, at 03:20, Mike Caspar <[email protected]> wrote: >>> >>> Any ideas or a direction (or samples) to go to next? >>> >> Define an explicit dependency on the higher of the two versions. >> > > -- > 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/b1839845-1d63-2b1c-033f-864119b26d58%40caspar.com. > For more options, visit https://groups.google.com/d/optout. -- 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/85BF84BC-A9F7-4AAF-9D95-2D53121FCC67%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP
