AllowClobber should write a warning about command collisions

[Jaykul]

Can we please have Install-Module with -AllowClobber write a warning about command collisions, so that we still get notified about them as we install?

Personally, I think that should be the default behavior. I mean, hypothetically a user can always cancel or uninstall if it gets in the way, but so far I have never not installed a module because of the command-collision error, so I'm just annoyed at having to run Install-Module commands two or three times.

[kilasuit]

Nice Idea Joel and I agree that it should be the default behaviour too!

[ebekker]

Also, be sure to take into account if the DefaultCommandPrefix of the module is set and evaluate if the final resolved cmdlet is in fact in conflict as per PowerShell/PowerShellGetv2#45.

In fact if the fully resolved name is not already being evaluated, this opens up a security hole, for example if I define a cmdlet Get-ificate and the module manifest has a DefaultCommandPrefix of Cert then the naked cmdlet name won't be in conflict, but the fully resolved name will be.

[alerickson]

Addressed with release of 3.0.0-beta2