[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] WTP feature/plugin versioning

Hi Max,

I agree in principle that the version number (perhapes, the 4th digit) should be updated between milestone builds. Unfortunately, I can only think of two ways to do this:

1. Update all feature/plug-in version numbers and commit them into CVS. This approach is not viable because it introduces too much noise to the build team and the dev teams.

2. PDE/org.eclipse.releng.basebuilder supports an automated way to insert 4th digit version numbers into features/plug-ins fetched out of CVS. We do not have such support right now, but I know that the Eclipse releng team will investigate this in the 3.2 timeframe.

Let's say we did increment the version number between milestone builds, wouldn't you run into the same problem with prereqs? I'm pretty sure Eclipse, VE and GEF do not provide version updates between milestone builds (EMF does). So, even if WTP did update the version numbers, you probably have to go through the same pain of managing the version numbers of the prereqs.

An alternative way to tackle this problem is to insert the 4th digit version number when you build your update site. Eclipse has a (unsupported) tool that helps you do this. If you want to take a look at this tool, let me know, I'll send it to you. But then again, we still have to deal with the prereqs, which have not updated their versions.


Jeffrey Liu
IBM Rational Software - Performance Analyst
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/R8V/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920

"Max Rydahl Andersen" <max.andersen@xxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

06/10/2005 08:27 AM

Please respond to
"General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Re: [wtp-dev] WTP feature/plugin versioning

It is also not just an update site issue, it is also a major
pain to identify library conflicts if users upgrade/install
via a normal download.

And its also a major issue to sync up projects that uses WTP plugins -
no way to see what version they are using by manual inspection, trial and  

If the minor version number were incremented (which in my view make sense
since something really has changed and been released) then these  
issues will be alot less painfull - and WTP would get adapted quicker.


> It seems that version numbers aren't being updated for major milestones,  
> and this is causing a major problem for our update site (where we have  
> multiple plugins dependant on multiple milestones of webtools).
> Is there any hope of getting correct version numbering for upcoming  
> milestone builds?
> We've opened a bug here:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=99338

wtp-dev mailing list