Re: [forge-dev] Plugin Backwards Compatibility

We ran into the same problem with the scaffold plugin. I wanted some @Option-annotated method parameters and @Command-annotated methods to be removed or deprecated, but didn't so, due to the reasons Max and Lincoln have outlined. I would suggest retaining the existing options and commands for backward compatibility, and introduce new ones if you can make them work with the existing ones. ----- Original Message ----- > From: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; > To: "forge-dev List" <forge-dev(a)lists.jboss.org&gt; > Sent: Monday, March 25, 2013 10:33:56 AM > Subject: Re: [forge-dev] Plugin Backwards Compatibility > > On Fri, Mar 22, 2013 at 06:09:56PM -0700, James R. Perkins wrote: >> What are the rules for plugin backward compatibility? I've done >> quite a >> bit of work cleaning up the JBoss AS 7 plugin, but I changed some >> prompts and some behavior. I haven't completely finished testing >> yet, >> but since Forge allows scripts I was wondering if backwards >> compatibility is important. > > Yes, it is important since tutorials and eclipse plugins calling > these commands > will have to be updated. > > Especially if your plugin is used in ticketmonster :) > > /max > >> -- >> James R. Perkins >> JBoss by Red Hat >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev