Community
Participate
Working Groups
The /downloads page contains a link in the text "You will need a Java runtime environment (JRE) to use Eclipse (Java 5 JRE recommended)." that takes you to a page (/downloads/moreinfo/jre.php) titled "Java Runtime Environment". This page uses the Phoenix skin, may be inaccurate, and contains links to information about packages that may not be entirely accurate. I'll update the JRE information. We need to decide what to do about the other "info" pages. They contain links to old tutorials that may still be useful. However, I think that we should probably just make them go away.
In retrospect, rather than attempt to duplicate information, maybe we should just change the /downloads page to include a link to the Eclipse project's plan document: http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_6.xml#target_environments They consistently name their project plans with the version information included. Thoughts?
Agreed!
Created attachment 184220 [details] Change the JRE link to link to the Eclipse 3.6 project plan.
Created attachment 184221 [details] mylyn/context/zip
So this should just be as easy as changing the link on /downloads/content/en_index.php (I've attached a patch). My concern, however, is that this link will become stale when 3.7 is released. We'll have to remember to update it. We could use http://www.eclipse.org/projects/project-plan.php?projectid=eclipse#target_environments instead, but that points to the current plan (which is 3.7 at this point in time). Is there any variable or other mechanism we can use to generate the URL more dynamically to avoid adding one more think to the list of stuff we have to remember to update with each release? Or am I thinking about this too much?
> Is there any variable or other mechanism we can use to generate the URL more > dynamically to avoid adding one more think to the list of stuff we have to > remember to update with each release? I already have this info hardcoded in download.php (see line 188 of file below) so I am not opposed to creating a separate file that you and I can just include(). Once place to edit. http://dev.eclipse.org/viewcvs/viewvc.cgi/www/downloads/download.php?view=markup&root=Eclipse_Website
(In reply to comment #6) > > Is there any variable or other mechanism we can use to generate the URL more > > dynamically to avoid adding one more think to the list of stuff we have to > > remember to update with each release? > > I already have this info hardcoded in download.php (see line 188 of file below) > so I am not opposed to creating a separate file that you and I can just > include(). Once place to edit. > > http://dev.eclipse.org/viewcvs/viewvc.cgi/www/downloads/download.php?view=markup&root=Eclipse_Website Agreed as i maintain the packages this is a large pain point for me. We already have a URL rewrite tool so could we start using this? http://eclipse.org/go/projectplan as long as we keep the pointer up to date it should work. I'm can't see there being a lot of work to do to make this happen technically.
Is there a common "constants" file where we can just create $jreUrl variables and such?
*** Bug 249063 has been marked as a duplicate of this bug. ***
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. -- The automated Eclipse Genie.
The JRE blurb now goes to a Wiki page, and the moreinfo pages were removed via another bug.
