@DanielBeck: I like that option as it will allow me to drop the soap-related stuff while still reusing the existing code.
I'd like to migrate to jenkins credentials at the same time and drop the input fields for user/pass. Or maybe there is a recommended way of migrating plugins from user/pass input fields to the credentials plugin? On Sat, Mar 29, 2014 at 12:03 AM, Daniel Beck <[email protected]> wrote: > > On 28.03.2014, at 22:48, Stefan Thurnherr <[email protected]> > wrote: > > > feels like quite a big change, which I believe makes it justifiable to > create a new plugin > > If necessary (no additional option 'Use SOAP'/'Use REST' feasible) you > could keep as much as possible from the existing plugin, and make this a > Jira plugin 2.0 instead. > > IIRC there's a way to mark releases as incompatible in update center, so > users will be made aware of the big difference before installing. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/j1gcydeNiUI/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > 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]. For more options, visit https://groups.google.com/d/optout.
