The purpose of adding that was so that plugin providers can add update wizards from version x to version y with relative ease via an extension point. <br><br>They can now do something like, from version 1.5.* to version
2.0.0.*, use <insert class> as a wizard page.<br><br>I probably just didn't see the versioning in the plugin.xml and hard-coded it. I suppose I figured that we'd have to change something, either in a plugin.xml, or text resource, or class file, and it didn't seem to matter much to me which we did. I realize changing that in two places is bad, so I just wasn't aware that it was already somewhere.
<br><br>So... ... ... where was the version stored previously? I can change it to just use that. <br><br>- Rob<br><br><div><span class="gmail_quote">On 9/13/06, <b class="gmail_sendername">Max Rydahl Andersen</b> <<a href="mailto:max.andersen@jboss.com">
max.andersen@jboss.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi guys,<br><br>I just noticed that CorePlugin now has a hard branded version id and
<br>custom version comparison in it ?<br><br>May I ask why ?<br><br>...and what is wrong with using the versioning in the plugin.xml etc.<br>instead of a new concept ?<br><br>If it is just to get a "release name" why not just put it in the resource
<br>bundle ?<br><br>--<br>--<br>Max Rydahl Andersen<br>callto://max.rydahl.andersen<br><br>Hibernate<br><a href="mailto:max@hibernate.org">max@hibernate.org</a><br><a href="http://hibernate.org">http://hibernate.org</a><br>
<br>JBoss a division of Red Hat<br><a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a><br>_______________________________________________<br>jbosside-dev mailing list<br><a href="mailto:jbosside-dev@lists.jboss.org">
jbosside-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/jbosside-dev">https://lists.jboss.org/mailman/listinfo/jbosside-dev</a><br></blockquote></div><br>