Community
Participate
Working Groups
after once creating a new plug-in development project from the New project wizard, the Java Project item in the same dialog box disapear, making me unable to start a new java project. This bug happens on 3.0 M5 and M6. I'm running eclipse on Mac OSX Panther 10.3.2
From the newsgroup: It seems that this bug is NOT happening on Windows XP
andre, can you investigate?
Cannot reproduce problem in I20040113. Please provide more detailled steps so that I can reproduce the problem. In addition please attach any error messages and stack traces you find in the Eclipse .log file or on the Mac OS X Console. Thanks.
Ok, here is a detailed step on how to reproduce this bug. With a working Eclipse 3.0 M5 or M6 install, click on File -> New -> Project The dialog wizard appears and on the left part of the wizard you see: Java Project, Plug-In Development, Simple. Select Plug-In Development on the left and whatever you like on the right part of the wizzard, then click Next until you finish every steps of the wizzard. Now repeat the operation: Click on File -> New -> Project. You can now see that on the left part of the Wizard Java Project has disapeared. It's only possible to create Plug-In development project or simple project. Here is my build id: 200312182000 It seems that it is perefectly working with M5 on Windows XP, but I could reproduce it on 2 different machines with fresh M6 installations on Mac OSX Panther 10.3.2. Below the content of .log Thanks for your help !SESSION Jan 13, 2004 10:35:39.135 --------------------------------------------- java.version=1.4.1_01 java.vendor=Apple Computer, Inc. BootLoader constants: OS=macosx, ARCH=ppc, WS=carbon, NL=en_US Command-line arguments: -os macosx -ws carbon -arch ppc -showlocation !ENTRY org.eclipse.ui 4 4 Jan 13, 2004 10:35:39.138 !MESSAGE Exception creating editor: File does not exist !ENTRY org.eclipse.pde.core 2 1 Jan 13, 2004 10:36:02.620 !MESSAGE Problems while scanning external plug-ins !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.620 !MESSAGE Plug-in "org.eclipse.jem" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.emf.ecore.xmi". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.621 !MESSAGE Plug-in "org.eclipse.jem.proxy" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.jem". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.621 !MESSAGE Plug-in "org.eclipse.jem.beaninfo" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.jem.proxy". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.622 !MESSAGE Plug-in "org.eclipse.jem.beaninfo.ui" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.jem.beaninfo". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.623 !MESSAGE Plug-in "org.eclipse.ve.propertysheet" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.emf.common". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.623 !MESSAGE Plug-in "org.eclipse.ve.cde" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.ve.propertysheet". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.624 !MESSAGE Plug-in "org.eclipse.ve.java.core" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.ve.cde". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.624 !MESSAGE Plug-in "org.eclipse.ve.jfc" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.ve.java.core". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.632 !MESSAGE Plug-in "com.ibm.etools.emf.ecore.utilities" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.emf.ecore.xmi". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.634 !MESSAGE Plug-in "com.ibm.etools.emf.workbench" was disabled due to missing or disabled prerequisite plug-in "com.ibm.etools.emf.ecore.utilities". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.634 !MESSAGE Plug-in "com.ibm.etools.emf.event" was disabled due to missing or disabled prerequisite plug-in "org.eclipse.emf.ecore". !SUBENTRY 1 org.eclipse.core.runtime 2 1 Jan 13, 2004 10:36:02.635 !MESSAGE Unable to satisfy prerequisite constraint from "org.eclipse.jem.workbench" to "org.eclipse.jem".
Thanks for the info. When I opened the New wizard for the second time, the "Java" item was not visible because it was scrolled out of the view. Using the vertical scrollbar made it visible (and the scrollbar disappeared subsequently). Is this the effect you are seeing?
Shame on me. Yes that was it, sorry for the time lost. Olivier
No, don't blame yourself... It's still our bug that revealing the PDE item makes the Java item scroll out of view. (since there is enough space for all items). Greetings from Zurich ;-)
Renaming problem report to reflect real error.
I tried this on the Mac (10.3.3) and on Windows XP. The dialog on Windows is definitely larger. It is large enough to keep all the expanded items visible. However, this behaves differently on the Mac. One possible solution is to adjust the size of the dialog area on the Mac so that the tree is always visible even when all its items are epxanded.
We want to try and keep the dialog size consistent by default rather than making dialogs bigger in general. If you are running with a lower resolution and end up with a scroll bar then that is something we won't change (other Eclipse based products have this all of the time).
Dialog size is not (at all!) the problem here. The problem is that, even though there is enough space to display the entire tree (as in the new project wizard), the tree by default is scrolled down so that items above the currently selected item are "invisible". Of course, those items can be reached by scrolling up, but that is counter-intuitive, because you would expect a tree that would easily fits into the client area to be shown completely. This bug might seem trivial, but it's a real usability issue on the Mac. From my experience, you "subconciously" do not look for a scroll bar if the need to scroll (content exceeds client area) is not apparent, as in this case. You just think that the missing items are somehow gone (until you get used to this bug :-P). Please don't close a bug like this based on a single comment that does not reflect the actual nature of the problem. This issue is important for us Mac users.
The most important thing is that the selection is visible - if the selected items gets scrolled away then that is even worse. I will mark this for consideration in a future release if you believe it is that important.
There is already a bug filed for making the selected item visible for the wizard you are refering to (Bug 61951). This bug could be marked as a duplicate.
Reopening now that 3.0 has shipped
I am using 3.2 M3 to try to replicate this bug on Mac OS/X 10.3.8. This bug doesn't appear to exist any longer. Note that the wizard selection page has changed to be a tree now, rather then 2 lists.
