Community
Participate
Working Groups
Build 20020918 Linux-GTK The "Completing the install" splash screen is shown everytime I launch Eclipse, not just the first time.
Jared, The GTK launcher has just been rewritten - it is not in the last integration build but it appears in the nightly build from 20020918. Which build are you referring to in this PR? Kevin, Is the new GTK launcher handling the "Completing the install" case correctly?
I was using the integration build. I get the same behavior on the 20020920 MOTIF integration build.
It looks like the problem is caused by launching a 2.0 stream build pointing to a 2.1 stream workspace. I've been using the same workspace with the 2.0.2 stream builds and the 2.1 stream builds.
The launcher has no knowledge of the "Completing the Install" mechanism. All the "main" launcher knows about is the special "restart" exit code. The sequence for the first time launch of Eclipse is as follows: 1. Use starts eclipse.exe (the main launcher). 2. The main launcher starts the JVM with the appropriate arguments. 3. Eclipse examines the workspace (which does not exist) and starts a second instance of the launcher (the splash launcher) with the "Completing the Install" bitmap file. 4. After initializing the workspace, Eclipse terminates the splash launcher and then exits with the "restart" exit code. 5. The main launcher detect the exit code and restarts the JVM with the exact same arguments as in step 2. 6. Eclipse examines the workspace and the command line arguments and determines the appropriate "feature" splash.bmp file. It then starts a new instance of the splash launcher again but with the feature's BMP file this time. 7. After the main window is created, the splash luancher is terminated by Eclipse, and everything is ready to go. (The main launcher is still running, waiting for the JVM to exit.) In my experience with eclipse, I have also seen that "Completing the Install" splash window on subsequent Eclipse sessions. The logic in Eclipse that determines the appropriate feature bitmap seems to get confused sometimes, especially if new plug-ins are added or removed directly from the product area. (e.g., not usig the extension link mechanism). Also, if you start Eclipse with the -feature <featureName> switch where the <featureName> does not exist, you will see that "Completing the Install" splash window. Thus, using a new version of Eclipse with an old workspace has the same effect as adding/removing plug-ins.
Dejan - This looks like an update problem. Please move this defect to update if it is.
We fixed a bug in 2.0.1 stream that had the exact symptoms. can you try to get a 2.0.1 stream and point to a 2.1 or 2.0.2 workspace instead of using 2.0 ? The bug had to do with replacing the eclipse by another version in the same directory... Is that your scenario ? do you have multiples eclipse(s) pointing to the same workspace ?
Christophe, I'm not sure what you're asking. I said above: "I've been using the same workspace with the 2.0.2 stream builds and the 2.1 stream builds." If this doesn't answer your question, can you please rephrase?
Jared, ok, I just wanted to confirm to were using the same workspace with different stream as a host (not the code you load in the workspace). ok, you said: "It looks like the problem is caused by launching a 2.0 stream build pointing to a 2.1 stream workspace. I've been using the same workspace with the 2.0.2 stream builds and the 2.1 stream builds." to use the same sematic/dictionnary we will call the 'host' the eclipse you start (eclise.exe) and the 'runtime' (cannot find a better name) the eclipse you launch from the host. your problem occurs when you start a 2.0 host pointing to the 2.1 (or common) workspace, but you do not see the problem with 2.0.2 host not 2.1 host ? If this is the case, it may be a bug we fixed in 2.0.1... 1) tell me where the hosts are installed (dir) 2) tell me where the worspace is installed 3) attach your .metadata/.config/platform.cfg Txs
I think I may be mincing terms here. :) When I said "2.0 stream build" I mean the "2.0 maintenance stream". I was referring to the 2.0.2 build. For future reference, I'll call that the "2.0.x stream." My host and "runtime" (we call that the "target") are always in the same directories: $HOME/host/eclipse and $HOME/target respectively. What I did (accidentally): 1. 2.1 stream host (20020917) pointing to workspace A 2. 2.0.2 stream host (20020918) pointing to workspace A
ok, IC let's summarize(sp?) 1) do you still experience the problem ? 2) can you confirm the problem occured when you had 2.0.2 host and doesn't occur when you replaced by 2.1 host ? 3) how does your platform.cfg look like If this is teh case I will try the following: a) install 2.1 b) start pointing to a -data workspace c) remove 2.1 d) install 2.0.2 inteh same directory as 2.1 e) start pointing to the same 2.1 workspace That was what you did right ?
Yep, that's what I did. I just created a new workspace to workaround the problem so I don't see it anymore. I don't have my platform.cfg either, but the problem is easy to reproduce.
reproduced, works with 2.0.1, regression, P1 for 2.0.2
202 feature still includes 201 feature in feature.xml They should include 202 the problem is that the reconciler was attempting to reconcile 201 feature and failed, thus not writting any new platform.log
I have updated the org.eclipse.platform.source-feature and its plugin to 2.0.2 This will be incorporated into nexts Wednesday's build
based on 2.0.2 build (and tests) it seems some feature are referenced but not present in the build... on the other side, Eclipse should start properly and the reconciler should not choke. I am changing the code right now so the reconciler will not choke, I tested it with the latest 2.0.2 build and got the following status (attached as gif file)
Confirmed fixed on 2.0.2 candidate build
Verified on 2.0.2 Candidate build
Closed
