<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I'll do it :-)<div><br></div><div><br><div><div>On Mar 8, 2012, at 15:57 , Lincoln Baxter, III wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I completely agree :) never fear! This mechanism was mostly put in place to prevent horrific crash and burn scenarios where Forge would refuse to boot (failing with a terrible exception message) when a plugin was API incompatible.<br>
<br>I'd love to get a full plugin version system up and running. I think allowing users to select from a list is a good first step. We'll also need to enhance the loading functionality itself, slightly, in order to support loading from a version that is not an exact match, but is within the same minor version. (e.g. 1.n.x, but not 2.n.x)<br>
<br>Any volunteers? I think this would be a great one for someone who's interested to work on!<br><br>~Lincoln<br><br><div class="gmail_quote">On Thu, Mar 8, 2012 at 9:50 AM, Rodney Russ <span dir="ltr"><<a href="mailto:rruss@redhat.com">rruss@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would tend to prefer giving users options over "magic" and would assume that there would be a default version selected for the users that don't want to think when installing. How would that default be chosen?<br>
<br>
-Rodney<br>
<br>
----- "Paul Bakker" <<a href="mailto:paul.bakker.nl@gmail.com">paul.bakker.nl@gmail.com</a>> wrote:<br>
<br>
> From: "Paul Bakker" <<a href="mailto:paul.bakker.nl@gmail.com">paul.bakker.nl@gmail.com</a>><br>
> To: "forge-dev List" <<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a>><br>
> Sent: Thursday, March 8, 2012 12:50:56 AM GMT -07:00 US/Canada Mountain<br>
> Subject: [forge-dev] plugin versioning<br>
<div class="HOEnZb"><div class="h5">><br>
> Hi all,<br>
><br>
> Yesterday during the meeting we talked about plugin versioning.<br>
> Currently Forge checks if there is a tag/branch of the plugin that<br>
> matches the Forge API version while installing. We discussed if we can<br>
> test on compatibility of plugins on a CI server.<br>
><br>
> I started thinking about this again and actually think we should<br>
> re-think the version checking mechanism. Now that Forge is final, the<br>
> APIs should be stable. They should be stable until we go for a 2.0.0<br>
> version, which means plugins are not supposed to break on API changes<br>
> for 1.0.1, 1.1.0 etc. If we do that correctly, it's also not necessary<br>
> to upgrade plugins each time there is a new release (or be back at<br>
> building to snapshots which is dangerous). Instead I suggest prompting<br>
> available versions of plugins during plugin installation (still<br>
> looking at tags for that), so that a user can choose to use a stable<br>
> version, some beta or maybe a snapshot. This also gives us the<br>
> freedom to do minor Forge releases more often without the hazzle of<br>
> upgrading all plugins once again…<br>
><br>
> Thoughts?<br>
><br>
> Paul<br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com/">http://ocpsoft.com</a><br><a href="http://scrumshark.com/">http://scrumshark.com</a><br>"Keep it Simple"<br>
_______________________________________________<br>forge-dev mailing list<br><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/forge-dev<br></blockquote></div><br></div></body></html>