RE: [cdt-dev] Build version numbers

[Doug Schaefer <DSchaefer@xxxxxxx>]

They should be upversioned when a change happens. But being a manual
operation, I'm pretty sure we haven't got into the habit of doing that so
I'm not surprised that hasn't been done yet for some plug-ins. Luckily the
build adds on the timestamp as the qualifier in the fourth field of the
version and we're getting away with it.

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com

> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Vivian Kong
> Sent: Friday, October 26, 2007 1:03 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] Build version numbers
> 
> 
> Hi Doug,
> 
> When do I bring up the version number for a plugin?  I understand that
> generally we upversion all the plugins for each release but I was checking
> the 4.0.1 build and that's not the case (e.g. org.eclipse.cdt.doc.isv,
> org.eclipse.cdt.core.win32).  The generated site.xml file is assuming all
> plugins have the same build version.  Should I change the version numbers
> in site.xml or upversion the plugins themselves as well as their features?
> 
> Thanks,
> 
> Vivian Kong
> IBM Eclipse CDT
> IBM Canada Toronto Lab
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev