[forge-dev] Plugin Backwards Compatibility

[James R. Perkins]

Thanks all for the feedback. I'll keep it backwards compatible. So far I 
only have one part I think is different and that's having a default 
download location. I'll just use a temporary resource and that should 
solve the issue.


On 03/24/2013 03:15 PM, Lincoln Baxter, III wrote:
> Script backwards compatability is important for most of the core and 
> built-in plugins. For the AS7 plugin, since it is used in some of the 
> JDF quickstarts, you may want to make sure that things stay backwards 
> compatible with those.
>
> https://github.com/jboss-jdf/jboss-as-quickstart/tree/master/forge-from-scratch
>
> /cc Pete.
>
>
> On Fri, Mar 22, 2013 at 9:09 PM, James R. Perkins <jperkins at redhat.com 
> <mailto:jperkins at redhat.com>> 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.
>
>     --
>     James R. Perkins
>     JBoss by Red Hat
>
>     _______________________________________________
>     forge-dev mailing list
>     forge-dev at lists.jboss.org <mailto:forge-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
>
>
> -- 
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

-- 
James R. Perkins
JBoss by Red Hat

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20130325/8d34a2a8/attachment.html