[forge-dev] Plugin Backwards Compatibility
pmuir at redhat.com
Mon Mar 25 05:51:54 EDT 2013
Is there a way to automatically indicate that a command or option is deprecated e.g. you annotate the method or parameter with @Deprecated and Forge automatically prints out a warning message?
On 25 Mar 2013, at 09:03, Vineet Reynolds Pereira <vpereira at redhat.com> wrote:
> 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 at redhat.com>
>> To: "forge-dev List" <forge-dev at lists.jboss.org>
>> 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
>>> 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 :)
>>> James R. Perkins
>>> JBoss by Red Hat
>>> forge-dev mailing list
>>> forge-dev at lists.jboss.org
>> forge-dev mailing list
>> forge-dev at lists.jboss.org
> forge-dev mailing list
> forge-dev at lists.jboss.org
More information about the forge-dev