On Wed, Mar 30, 2016 at 10:54 PM, 'George Simpson' via Jenkins Developers <[email protected]> wrote: > Does anyone know the reason plugins installed via 'upload' are treated > differently?
Because the upload feature is not frequently used, and no one ever bothered to implement automatic dependency handling for this case. There is no technical reason I know of why it would be difficult. (Obviously if you are uploading a custom plugin with a dependency on *another* custom plugin which you forgot to upload first, Jenkins could do no better than to report a helpful error message, since it would not be able to locate the dependency in the update center.) -- 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/CANfRfr37LbNcaMCW1_SbmiqLmEFkX9-kb1tJiD6KKBFnLctPBw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
