RE: [cdt-dev] Build version numbers

[Doug Schaefer <DSchaefer@xxxxxxx>]

BTW, just to be clear, the feature and plug-in version numbers don't need to
match. The feature.xml lists all the plug-in versions and that's what the
update manager will use to find the plug-ins. The site.xml only lists the
features and the generated site.xml file does assume they are all the same
number. 

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 Doug Schaefer
> Sent: Friday, October 26, 2007 2:38 PM
> To: CDT General developers list.
> Subject: RE: [cdt-dev] Build version numbers
> 
> The site.xml assumes all features are 4.0.2. You definitely should
> upversion
> all the features whether they change or not. I forgot about that...
> 
> 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 2:35 PM
> > To: CDT General developers list.
> > Subject: RE: [cdt-dev] Build version numbers
> >
> > The problem I'm seeing is that some plugins are not showing up in update
> > manager (site.xml assumes all plugins are at 4.0.2).  The plugins are
> > physically in the master zip though.
> >
> > I believe the GDB Hardware Debugging plugin is not showing up in 4.0.1
> for
> > the same reason.
> >
> > I guess I should change the template buildsite.xml so it won't make an
> > assumption that all the plugins have the same version number?
> >
> > Regards,
> >
> > Vivian Kong
> > IBM Eclipse CDT
> > IBM Canada Toronto Lab
> > Phone: (905) 413-6067
> > Email: vivkong@xxxxxxxxxx
> >
> >
> > |------------>
> > | From:      |
> > |------------>
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> >   |Doug Schaefer <DSchaefer@xxxxxxx>
> > |
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> > |------------>
> > | To:        |
> > |------------>
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> >   |"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
> > |
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> > |------------>
> > | Date:      |
> > |------------>
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> >   |10/26/2007 01:13 PM
> > |
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> > |------------>
> > | Subject:   |
> > |------------>
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> >   |RE: [cdt-dev] Build version numbers
> > |
> >   >---------------------------------------------------------------------
> --
> > ------------------------------------------------------------------------
> --
> > -|
> >
> >
> >
> >
> >
> > 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
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> >
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev