Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332143

Summary:	Archive version not updated on update site "build"
Product:	[Eclipse Project] PDE	Reporter:	Andrey Loskutov <loskutov>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:	stalebug

Description Andrey Loskutov

2010-12-08 11:02:30 EST

Build Identifier: 3.5 - 3.6 any

Please follow the steps from the wiki here:
http://code.google.com/a/eclipselabs.org/p/mercurialeclipse/wiki/UpdateSiteMaintenance

Reproducible: Always

Steps to Reproduce:
1 Import the wiki as projects into Eclipse workspace (use the repo url below) 
2 Open site.xml in Eclipse Update Site editor 
3 In the code view, "feature" entry, change "version" attribute to "1.7.1.qualifier" (it will be replaced by the automatically generated feature version) 
4 Select existing MercurialEclipse feature entry in the left pane 
5 Click on "Build" button 
6 Check the /plugins and /features folder: there are new files now 
7 Upload generated com.vectrace.MercurialEclipse_x.y.z.jar from /plugins folder to project download section 
8 Update the "archive" section in the site.xml with the proper jar file version (2 places, should match generated plugin version)

Step 8 is the actual bug: although the feature version was updated after the build, corresponding archive version was not updated. As all 4 places contain exact the same version string before the build, they shouldn't differ aft er the build too.

Comment 1 Eclipse Webmaster

2019-09-06 15:30:44 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 2 Julian Honnen

2019-09-09 02:38:47 EDT

Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.