Community
Participate
Working Groups
I believe for Helios we need to add Windows 64 bit support for all the EPP packages.
Created attachment 153695 [details] error of eclipse-jee in win it doesnot work in win x64.
WHEN WILL RELEASE THE NEXT VERSION SUPPORTING WIN X64????
This bug's intention is to get feedback from the community that will lead to a discussion (and in the end to a decision) whether we want&&can&&need deliver 64 bit versions of the EPP packages for the Helios release next Summer. To answer to your question in small letters: Don't expect a release of it before June 2010. In the screenshot that you attached to the bug it is not really clear to me what kind of JVM you are using - is it a Sun, etc.? Is it a 32 bit or a 64 bit JVM? What version? Did you try the 64 bit version of the Eclipse Classic?
(In reply to comment #3) > This bug's intention is to get feedback from the community that will lead to a > discussion (and in the end to a decision) whether we want&&can&&need deliver 64 > bit versions of the EPP packages for the Helios release next Summer. To answer > to your question in small letters: Don't expect a release of it before June > 2010. > In the screenshot that you attached to the bug it is not really clear to me > what kind of JVM you are using - is it a Sun, etc.? Is it a 32 bit or a 64 bit > JVM? What version? Did you try the 64 bit version of the Eclipse Classic? i use sun java_ee_sdk-5_08-jdk-6u17-windows.exe and jre-6u17-windows-x64.exe.
FWIW, the 64 bit version of the Classic SDK is available now at http://download.eclipse.org/eclipse/downloads/drops/R-3.5.1-200909170800/index.php As Markus mentioned this bug is to discuss having the EPP packages support 64 bit Windows.
To stimulate the discussion, I'll re-iterate what Ed Burnette wrote in bug 248494, comment 4 : someone who has 64-bit Windows and installs the JVM/JDK from Sun's web site will get the 64-bit JVM unless they explicitly look for and install the 32-bit version. Then they'll download Eclipse, which will fail in an ungraceful manner. In other words, the experience for a user who just chooses the defaults all the way through is not good at all. Ed's comment is more eloquent; Ed I'm copying you since you originally made the request a year ago in bug 248494
(In reply to comment #6) > To stimulate the discussion, I'll re-iterate what Ed Burnette wrote in bug > 248494, comment 4 Bugzilla documentation says that should have produced a link right to the comment. <sigh>* Here's the link to bug bug 248494 * When is Bugzilla going to offer either a preview feature or the ability to edit your own comments after posting them...we're stuck in the dark ages here...
(In reply to comment #6) > To stimulate the discussion, I'll re-iterate what Ed Burnette wrote in bug > 248494, comment 4 : someone who has 64-bit Windows and installs the JVM/JDK > from Sun's web site will get the 64-bit JVM unless they explicitly look for and > install the 32-bit version. Then they'll download Eclipse, which will fail in > an ungraceful manner. In other words, the experience for a user who just > chooses the defaults all the way through is not good at all. > Ed's comment is more eloquent; Ed I'm copying you since you originally made the > request a year ago in bug 248494 Thanks for re-iterating the use case. I agree this is not ideal and I hope we can address it in Helios.
My experience is that I'm using 64-bit Eclipse platform and 64-bit JRE since Ganymede. However, I consider myself an experienced Eclipse user, so I often prefer to install all the plugins I need (WTP, TPTP, JDT, Mylyn, etc.) on top of a bare Platform runtime, so I'm happy with what is already available. However I think that the absence of EPP packages for Windows 64-bit can actually be a problem for an Eclipse new bie and I can't hardly understand why there's none, while there are both Linux and Mac 64-bit bundles already available...
i download eclipse-SDK-3.5.1-win32-x86_64.zip. and the eclipse can work in win7 x64. meantime many feature doesnot have, so i have to add . but where is the websit to install new software?
(In reply to comment #10) > > but where is the websit to install new software? It is built in to what you installed, see the "available software sites". It is the one that ends with /releases/galileo.
(In reply to comment #11) > (In reply to comment #10) > > > > but where is the websit to install new software? > It is built in to what you installed, see the "available software sites". It is > the one that ends with /releases/galileo. is Eclipse Java EE Developer Tools 3.1.1.v200908101600-... for eclipse-jee i need???
(In reply to comment #12) > (In reply to comment #11) > > (In reply to comment #10) > > is Eclipse Java EE Developer Tools 3.1.1.v200908101600-... > for eclipse-jee i need??? Good guess. Feel free to experiment, explore ...
thank you all so much. i have a try . to explore . i believe i can get what i wanna. finally i hope the pure x64 eclipse in win 64 will be released soon .
(In reply to comment #14) > i believe i can get what i wanna. > finally i hope the pure x64 eclipse in win 64 will be released soon . I'm wondering ... just my curiosity ... why you want a 64 bit version? You know the 32 bit version will also run on a 64 bit machine, right? Usually people need a 64 bit version if they have absolutely huge amounts of memory required. And it is pretty rare than one IDE would need more than 4 Gig of memory. I know I have a 64 bit machine (just recently) and it was fun to play with the 64 bit version and write test programs to force it to use lots of memory ... but, in real life, I often have 3 or 4 different IDEs running (with different worspaces, different streams) and each of them are maybe using a gig or two ... so, yes, all together they use more than 4 Gig (and that's what is so great about having a 64 bit machine and operating systems) ... but, my individual Java EE IDEs are still quite happy being 32 bit. So, I'm just curious why the 64 bit version is so important to you. I would like to educate myself. Thanks,
In my opinion, this problem needs to be addressed right away, and not delayed until Summer 2010. 1. If you buy a new computer today it will almost certainly come pre-installed with a 64-bit operating system. For example if you go to dell.com and select the cheapest notebook they have (Inspiron 15), the only operating system option is Windows 7 Home Premium 64-bit. A quick search around the 'net did not reveal anyone who was willing to sell you a new computer with a 32-bit operating system on it. 2. Now let's say you use your new computer to go to http://java.sun.com looking for a download for Java. I tried to think of the path a regular user would take through the site to get Java. There's a link for "Downloads" that looks promising so you click on it. Then you click on "Top Downloads". The first two downloads are "Java Runtime Environment (JRE) 6" and "Java SE Development Kit (JDK) 6". Clicking on either one gets you to this page: http://java.sun.com/javase/downloads/index.jsp . A big orange button next to "JDK 6 Update 17" grabs your eyes and you click on it. That gets you to this page: http://java.sun.com/javase/downloads/widget/jdk6.jsp . There's a drop-down list for the Platform. Options include: - Windows - Windows x64 If you select "Windows" Eclipse will work. That's the default, and most people select that. But a lot of people, wanting to get the "latest and greatest" or "the most out of their system", select "Windows x64". If they do that, Eclipse will not work. Not only will it not work, but the error message is very strange and confusing to a new user and they'll have no hope of figuring it out. You could argue that the user didn't really need the 64-bit version of Java. That's probably true. However savy users will attempt to make sure all their software matches. If they have a 64-bit machine then it's only natural that they will believe a 64-bit JVM will work best on it. 3. I'm seeing this problem more and more as I try to teach people how to use Eclipse to develop for Android. Confusion is not limited to the Windows version but it's wost there. Here are a few examples of users struggling with the 32-bit/64-bit issue: http://forums.pragprog.com/forums/138/topics/3741 http://forums.pragprog.com/forums/138/topics/3639 http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg25556.html http://lingpipe-blog.com/2009/03/05/eclipse-ide-for-64-bit-windows-and-64-bit-java/ http://www.64bitjungle.com/tech/64-bit-eclipse-linux-installation-including-pdt-wtp-wst-atf-and-mysql-sql-explorer-plugin/ http://www.eclipse.org/forums/index.php?t=msg&th=156521&start=0 I would like to see the following changes done in the short, medium, and long term: 0. In the short term, on the download page, http://eclipse.org/downloads/, when you just click on the package name, for example "Eclipse IDE for Java EE Developers (189MB)", instead of going to http://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/galileo/SR1/eclipse-jee-galileo-SR1-win32.zip go to a page that explains to the user that the 32-bit version they are about to download WILL NOT WORK on 64-bit Java. (If you want to get fancy, detect what version of Java they have to see if it's compatible.) 1. In the short to medium term, change the code to add a little error checking so that if the user attempts to run an x-bit version of Eclipse on a y-bit version of Java, Eclipse will detect that and print a nice error message instead of a cryptic Java crash. 2. In the medium term (for Helios) add 64-bit EPP packages for Windows, and change the web page as appropriate. 3. In the longer term, if it's technically possible, simply make all packages and downloads of Eclipse work on both 32-bit and 64-bit JVM's. Or at least make the 32-bit Eclipse work on 32- and 64-bit Java. I think the only problem is the native bits in eclipse.exe and SWT.
(In reply to comment #15) > So, I'm just curious why the 64 bit version is so important to you. I would > like to educate myself. I can reply for myself. I'm a software dev working on an enterprise application that actually can require the host system to have 4 GB or more of memory (do you know that on a 32-bit Windows XP environment, if you even succeed on installing 4 GB of RAM, at least 2 of them are "reserved" for the OS and are not usable by Java VM?). So, I have a 64-bit JRE installed and Tomcat runs on it. I know I can launch a 64-bit JRE from Eclipse 32-bit, but given that we are in 2009 (almost 2010...) I would consider this a "plus" rather than a "standard" situation to my every day work in Java development. Having a complete 64-bit solution not only enables my IDE to use more than 4 GB or RAM if needed, but also: - it doesn't force me to install a 32-bit JRE just to run my IDE (given that I wouldn't need it for other things) - it doesn't make my IDE run in an "emulated" environment (WOW64, Windows-On-Windows64 emulation layer); this, together with the use of the extra registers available when running 64-bit code, may mean a little more performance (at least in some use cases), especially if using the new -XX:+UseCompressedOops Sun JVM argument Yes, I know these reasons are not enough to say that the lack of 64-bit EPP packages is blocking, anyway given that Eclipse Platform Runtime for Windows x64 is available since Ganymede I think preparing the EPP packages should not be so problematic...
(In reply to comment #17) > Yes, I know these reasons are not enough to say that the lack of 64-bit EPP > packages is blocking, anyway given that Eclipse Platform Runtime for Windows > x64 is available since Ganymede I think preparing the EPP packages should not > be so problematic... As Markus stated in bug 248494 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=248494#c3 ), the issue is the limited resources (people) available for EPP to test all the combinations of packages and platforms. The way I read it is that we could get Win64 packages if some people will step up and commit to test and report bugs. Then there is the issue of screen real-estate on the main EPP downloads page; it's getting a bit crowded with all the options. But I'm sure the website team could come up with an elegant solution to that.
(In reply to comment #18) > As Markus stated in bug 248494 > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=248494#c3 ), the issue is the > limited resources (people) available for EPP to test all the combinations of > packages and platforms. The way I read it is that we could get Win64 packages > if some people will step up and commit to test and report bugs. I don't know how the whole thing about EPP works, however since Eclipse for Windows x64 works perfectly with all the plugins included in the standard EPP packages (once you install them "from scratch" on a 64-bit Platform Runtime/SDK), I thought it were just a matter of creating an "all-in-one" package to be published on the "Downloads" section of Eclipse website. > Then there is the issue of screen real-estate on the main EPP downloads page; > it's getting a bit crowded with all the options. But I'm sure the website team > could come up with an elegant solution to that. A simple solution could be to add two links (32bit and 64bit) beside "Windows", just like the two links for Mac Cocoa and Linux.
(In reply to comment #18) > (In reply to comment #17) > Then there is the issue of screen real-estate on the main EPP downloads page; > it's getting a bit crowded with all the options. But I'm sure the website team > could come up with an elegant solution to that. I am confident we can figure out a solution for the download page.
I'm commenting re: the blog post here: http://bewarethepenguin.blogspot.com/2009/12/looking-for-easy-way-to-contribute-to.html I'm running 64-bit Windows 7 and would be glad to help test EPP builds... I'll watch this bug to see when testable builds are ready. Thanks, chris
I would happily commit to testing and running these windows 64 bit builds. If this happens, count me in.
I am using Windows Server 2008 64 bit! I would also be happy to help testing new Eclipse versions like mentioned on this blog (http://bewarethepenguin.blogspot.com/2009/12/looking-for-easy-way-to-contribute-to.html)... Just contact me :-)! Christian Voller
(In reply to comment #15) now i have 4 GB memory for a few days . 64x os is more powerful (the speed) . it is a fact .
*** Bug 281274 has been marked as a duplicate of this bug. ***
Look at the latest nightly Helios builds - there you'll find something that needs testing: http://www.eclipse.org/epp/download.php. I am unable to test these new 64-bit Windows packages.
(In reply to comment #26) > Look at the latest nightly Helios builds - there you'll find something that > needs testing: http://www.eclipse.org/epp/download.php. I am unable to test > these new 64-bit Windows packages. Good news ... they work! :) I did see one odd thing, but wouldn't prevent declaring it as M5. Good thing we're starting now. :) See bug 301702 for details, but I think the server team should investigate first.
I believe we can count this as fixed now? Thanks all.
yes, fixed.
