Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 399766 - clickthroughs don't work on renamed builds (with 3 parts)
Summary: clickthroughs don't work on renamed builds (with 3 parts)
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.2.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-01 17:58 EST by David Williams CLA
Modified: 2020-05-19 13:24 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2013-02-01 17:58:03 EST
I noticed on our M5 site, that "clickthroughs", such as for aix ppc64 are not displayed ... goes straight to eclipse mirrors. 

I'm guessing this has to do with the "renaming" of the I build to an S build -- either too much being changed or not enough.
Comment 1 David Williams CLA 2013-02-01 19:24:50 EST
It appears its not so much the renaming process, as it is that there is part of "download.php" file that assumes the "buildname" is either 1 or 2 parts, but our S and R builds have three parts. 

array(3) { [0]=> string(1) "S" [1]=> string(5) "4.3M5" [2]=> string(12) "201301302000" } parts2:

buildName: S-4.3M5

So doesn't "compute" the buildname correctly and thus later finds no "clickthrough file under .../S-4.3M5/clickthroughs/... 

This has been a problem for a long time ... makes me wonder if worth fixing ... since no one has noticed? 

But, I'll admit my bias ... I've never liked the "clickthroughs", since you have to see them each time you download ... a better fix/improvement, IMHO, would be to have another "footnote" type link that would pop up the clickthough information if a user clicked it.
Comment 2 Eclipse Genie CLA 2020-05-19 13:24:35 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.