I'm not trying to make this a plug-in version number, but rather a JBoss IDE release.

The wizard wont be used to upgrade from Hibernate tools x.y.c to Hibernate Tools x.y.z, but rather from one version of JBoss IDE (as an entire product) to another.

I really didn't want to make it go for each plugin based on plugin version, because obviously some parts of the IDE (like yours) have multiple plug-ins, and that could get hairy...

Of course further input is always welcomed.

(And no... I know you guys have mentioned several times the versioning of plug-ins is very strict but I never really had to deal with it personally so it all seemed kind of abstract to me)

- Rob

On 9/13/06, Max Rydahl Andersen <max.andersen@jboss.com> wrote:

> So... ... ... where was the version stored previously? I can change it to
> just use that.

eh ? You do know that eclipse has a very strict system with versioning
right ? :)

Just use the plugin version number...how you get I actually don't know but
the updatemanager
must be getting it from somewhere.

/max

>
> - Rob
>
> On 9/13/06, Max Rydahl Andersen <max.andersen@jboss.com> wrote:
>>
>> Hi guys,
>>
>> I just noticed that CorePlugin now has a hard branded version id and
>> custom version comparison in it ?
>>
>> May I ask why ?
>>
>> ...and what is wrong with using the versioning in the plugin.xml etc.
>> instead of a new concept ?
>>
>> If it is just to get a "release name" why not just put it in the
>> resource
>> bundle ?
>>
>> --
>> --
>> Max Rydahl Andersen
>> callto://max.rydahl.andersen
>>
>> Hibernate
>> max@hibernate.org
>> http://hibernate.org
>>
>> JBoss a division of Red Hat
>> max.andersen@jboss.com
>> _______________________________________________
>> jbosside-dev mailing list
>> jbosside-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosside-dev
>>



--
--
Max Rydahl Andersen
callto://max.rydahl.andersen

Hibernate
max@hibernate.org
http://hibernate.org

JBoss a division of Red Hat
max.andersen@jboss.com