[forge-dev] Plugin Backwards Compatibility

[Vineet Reynolds Pereira]

My bad. Zimbra swallowed a portion of the previous response when I hit 'send'. Forge would display something like this in 1.2.3:

[example-project] example-project $ example-plugin oldcommand 
***WARNING*** The command (oldcommand) is deprecated and may be removed in future versions
Executed named command without args.

There is also a related item in JIRA: FORGE-828, but from what I've noticed, this is not wired up to display deprecated options/commands as striked out text.


----- Original Message -----
> From: "Vineet Reynolds Pereira" <vpereira at redhat.com>
> To: "forge-dev List" <forge-dev at lists.jboss.org>
> Sent: Monday, March 25, 2013 5:06:53 PM
> Subject: Re: [forge-dev] Plugin Backwards Compatibility
> 
> Yes, George worked on this feature:
> https://issues.jboss.org/browse/FORGE-826 . I just tested it, and it
> works:
> 
> 
> 
> 
> ----- Original Message -----
> > From: "Pete Muir" <pmuir at redhat.com>
> > To: "forge-dev List" <forge-dev at lists.jboss.org>
> > Sent: Monday, March 25, 2013 3:21:54 PM
> > Subject: Re: [forge-dev] Plugin Backwards Compatibility
> > 
> > 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
> > >>> 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 at lists.jboss.org
> > >>> https://lists.jboss.org/mailman/listinfo/forge-dev
> > >> _______________________________________________
> > >> forge-dev mailing list
> > >> forge-dev at lists.jboss.org
> > >> https://lists.jboss.org/mailman/listinfo/forge-dev
> > >> 
> > > _______________________________________________
> > > forge-dev mailing list
> > > forge-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > 
> > 
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> > 
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
>