Bugzilla – Full Text Bug Listing
| Summary: | Version of org.eclipse.jdt.junit.runtime not increased since Helios | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | John Arthorne <john.arthorne> | ||||
| Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> | ||||
| Status: | RESOLVED WORKSFORME | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert, markus.kell.r | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
John Arthorne
Did you look at the latest M-build? We accidentally changed it but it got reverted to the one we had in 3.6. The latest tag I see for org.eclipse.jdt.junit.runtime is v20100824-0800. This indicates a date after the Helios release, but the version number is unchanged. Is it just being manually tagged but its contents are the same as Helios? >The latest tag I see for org.eclipse.jdt.junit.runtime is v20100824-0800.
Sorry, but I have no clue where you are looking. Please take a look at the attached picture.
Created attachment 177309 [details]
Image showing latest M-build content
Maybe you are looking in an older Helios build? If not, then the builder for Helios is not picking up the latest M-build. (In reply to comment #2) > The latest tag I see for org.eclipse.jdt.junit.runtime is v20100824-0800. This > indicates a date after the Helios release, but the version number is unchanged. > Is it just being manually tagged but its contents are the same as Helios? Yes, we always tag all our plug-ins for I-build inputs. That's why the plug-in got a new tag, although nothing changed in the plug-in between R3_6 and HEAD. In R3_6_maintenance, I've accidentally tagged the plug-in with r361_v20100714-0800, but this has been reverted to the 3.6 version (v20100526-0800) and will show up like this in tomorrow's M-build. > ... and will show up like this in tomorrow's M-build.
It's actually already in M20100818-0800, as Dani showed.
(In reply to comment #6) > Yes, we always tag all our plug-ins for I-build inputs. That's why the plug-in > got a new tag, although nothing changed in the plug-in between R3_6 and HEAD. This is what I was noticing. I'm looking at the I-builds, not the M-builds. I thought you would be using the releng tools, which only tags the bundles that have changed since the contents in the map file. Otherwise, you are forcing clients to upgrade to the "new" contents every build even when they are the same, which is an unnecessary download. So, since the qualifier (tag) has changed after helios, it looked like the plugin had actually been changed but the three part version number was unchanged. >I thought you would be using the releng tools, 100% correct. We always do. > which only tags the bundles that have changed since the contents Not true. This depends on whether that option is selected. We've discussed this again, and we will change our build input process to only release changed projects in the future. Having all projects tagged was sometimes handy because you always knew from which build a plug-in came from, but we buy the argument about unnecessary updates. Sounds good. I know it's a bit more work, but you can always figure out what version is in a given build by looking at the map file revision for that build. Since the maps are tagged with the build number for every build, we can always use that to know what was in that build. |