Community
Participate
Working Groups
The product export wizard is missing the option to export a product to multiple platforms. There was a checkbox in 3.2 M4 which, when checked, added another page to the wizard which allowed to export the product for multiple platforms. This checkbo is missing in 3.2 M5. I have the RCP delta pack installed and the product configuration is showing the right versions of fragments provided by the RCP delta pack.
Created attachment 34991 [details] Screenshot of the export wizard in 3.2 M4
Created attachment 34992 [details] Screenshot of the export wizard in 3.2 M5
I hope the option did not go somewhere else, but I tried to find it in the *.product file but did not find it there.
I see that option just fine using 3.2M5 on Windows, but I haven't verified on Linux. Does it happen to you on Windows too?
(In reply to comment #4) > I see that option just fine using 3.2M5 on Windows, but I haven't verified on > Linux. Does it happen to you on Windows too? > yes, happens on my brand new Windows installation as well, but the plugins and features I'm using were created with 3.2 M4. I'll try to create a new project and test it with that one.
This also happens with new plugins created with 3.2 M%, both on windows and linux. Could it be that I haven't properly installed the delta pack? The plugins of the delta pack are showing fine in the configuration details (next attachment)
Created attachment 35012 [details] Configuration Details of my 3.2 M5 installation
From you configuration, it does not appear that the delta pack is installed correctly. how did you do it? When we decide whether to show/hide the checkbox, we look for a feature called org.eclipse.platform.launchers in your target platform. You do not have it.
Hi, I took a look at the RCP delta pack zip I downloaded and the feature is included. Then I looked at the features directory of my installation, here it is: wei-fieg@nono applications $ ls eclipse/features/ org.eclipse.jdt.source_3.2.0.v20060215-1200-0cq-cuim1y org.eclipse.jdt_3.2.0.v20060215-1200-0cq-cuim1y org.eclipse.pde.source_3.2.0.v20060210--qSWJzJJez org.eclipse.pde_3.2.0.v20060210--qSWJzJJez org.eclipse.platform.launchers_3.1.0 org.eclipse.platform.source_3.2.0.v20060215-6arkIf-1sI org.eclipse.platform_3.2.0.v20060215-6arkIf-1sI org.eclipse.rcp.source_3.2.0.v20060210-3BlARRhN5X org.eclipse.rcp_3.2.0.v20060210-3BlARRhN5X org.eclipse.sdk_3.2.0.v20060210--hQXJzJJez The contents of the org.eclipse.platform.launchers_3.1.0 directory are: wei-fieg@nono applications $ ls eclipse/features/org.eclipse.platform.launchers_3.1.0/ bin and that directory contains: wei-fieg@nono applications $ ls eclipse/features/org.eclipse.platform.launchers_3.1.0/bin startup.jar This matches the contents of the RCP Delta pack I had downloaded. I see that the org.eclipse.platform.launchers_3.1.0 feature contained a lot more in my eclipse 3.2 M4 installation. I'll try to download once more and tell you the outcome. (My download was from germany, universiy of applied siences esslingen)
So, I did the download again (from the same server, the others were too slow). The MD5 checksum is OK: wei-fieg@nono applications $ md5sum -c eclipse-RCP-3.2M5-delta-pack.zip.md5 eclipse-RCP-3.2M5-delta-pack.zip: OK but the contents of the delta pack zip are the same, the feature only contains the bin directory with the startup.jar
at then end of the day, do you have a feature directory called org.eclipse.platform.launchers_xxxxxx in your features/ directory of the Eclipse install?
(In reply to comment #11) > at then end of the day, do you have a feature directory called > org.eclipse.platform.launchers_xxxxxx in your features/ directory of the > Eclipse install? > yes, but the contents are wrong. It seems that the feature was not correctly packed into the RCP delta pack zip. (see comments #9 and #10)
(In reply to comment #12) > (In reply to comment #11) > > at then end of the day, do you have a feature directory called > > org.eclipse.platform.launchers_xxxxxx in your features/ directory of the > > Eclipse install? > > > > yes, but the contents are wrong. It seems that the feature was not correctly > packed into the RCP delta pack zip. (see comments #9 and #10) > when I copy the contents of the delta pack I had downloaded and installed for 3.2 M4 into my 3.2 M5 installation, everything works out fine. Please check the delta pack that is provided for download with M5, that pack is broken
then we're fine from a PDE standpoint. moving to Platform/Releng to see if the zips are generated correctly.
*** Bug 128648 has been marked as a duplicate of this bug. ***
The launcher feature was recently changed to use a qualifier. The packaging scripts that build the delta pack pointed to a specific version of the launcher feature. This has been fixed to be more generic for builds >= N20060223-0010 and I am in the process of recreating the M5 delta pack by hand.
had to revert these changes, found other issues in a test build. Will try another solution tomorrow.
Okay, there was a problem in the custom build script for the platform launchers feature that has been fixed for builds > N20060225 that I have confirmed with a test build.
Thanks, what do you suggest then ? Using 3.2 M5 with the delta pack of N20060225 or eclipse plateform N20060225 with delta pack N20060225 ? Thanks
Ok saw too late. There is a 3.2 M5a version of eclipse, rcp and delta pack, so I suppose it is this one you should use. Thanks
no. M5a is not correct. The changes for M5a are detailed here. Nothing else was fixed. http://dev.eclipse.org/mhonarc/lists/eclipse-dev/msg07430.html I'll regenerate the delta pack for M5a. Or you can use the one from tonight's build.
Ok used the N20060225 delta pack along with the RCP-SDK N20060225 as target. The "export to multiple plateform" possibility is now correctly displayed but if I try to export to another plateform than the one I'm using (Mac OS X), it will display this error message: "Problem during export. Reason: Unable to find plugin-in: ch.medclipse.application_0.0.0. Please check the error log for more details.". The error log doesn't show anything about the export. My plugin version is 1.0.0 and not 0.0.0. If I export into Mac OS X, I don't receive this message.
Same problem with the N20060228 release. Does someone else have this problem ? Thanks
*** Bug 130054 has been marked as a duplicate of this bug. ***
I just pushed a hand crafted delta pack for m5a to eclipse.org.
We have the same problem as in Comment #22 with N20060302-0010-delta-pack. The error says: Problem during export. Reason: Unable to find plugin-in: ch.medclipse.application_0.0.0. Please check the error log for more details.". We are trying to export Win32 based app from unix-gtk I just cleaned a log and the only entry in there is this one and I am not even sure if it is realated? !ENTRY org.eclipse.ui 4 4 2006-03-02 15:47:00.868 !MESSAGE Plugin org.eclipse.ui.ide, extension org.eclipse.ui.propertyPages Unknown extension tag found: enablement
Hello, Still the same problem with the new delta pack for 3.2M5a (m5b). This happens also on a windows xp machine trying to export in other plateforms. It is related to exporting from one plateform to different on. Exporting to the same plateform than the one used is working.
Hello, Is someone looking at this issue or should we open a new bug as it differs a little bit from the original title ? Thanks Dominique
Sorry for the delay, I was away last week. I just replaced the startup jar and the new delta pack is being pushed to eclipse.org.
*** Bug 131231 has been marked as a duplicate of this bug. ***
Hello. Thanks for the new version. I downloaded Delta Pack 3.2M5c and installed over RCP SDK 3.2M5a, but I still got the same error when exporting to another plateform than the one used... Problem during export. Reason: Unable to find plugin-in: ch.medclipse.application_0.0.0. Please check the error log for more details." Error log doesn't show anything...
The content of the m5a delta pack is now correct. I have replicated the problem. If you create a sample rcp app and product configuration, you cannot export to platforms other than the one you are running. Also, the page the presents the list of available platforms looks strange. I'll attach a screenshot.
Created attachment 36275 [details] screen shot of platforms to select for export notice that it shows win32/CVS in addition to win32/x86. Quite strange.
I stil have this "Unable to find plugin-in: ch.medclipse.application_0.0.0." Is someone looking into this annoying bug ?
I fixed the problem in comment 33. It is an artefact of self-hosting though and is not related to the issue here. When collecting the list of available ws/os/arch, PDE goes through the directories under the bin/ directory in the org.eclipse.platform.launchers feature. In this case, the feature was checked out from CVS, so we read the CVS folder among the others. The problem with building plug-ins across multiple platforms is certainly there, but it's a PDE/Build issue. I will move to that component Note that the RCP delta packs produced this week are bogus, as they are missing features (bug 133450) I reproduced the problem with I-20050327-1600 as my host and 3.2M5a + 3.2M5c RCP as my target.
(In reply to comment #34) > I stil have this "Unable to find plugin-in: ch.medclipse.application_0.0.0." > Is someone looking into this annoying bug ? I'm having the same problem as comment_34. I'm probably not helping at all but here's what I've noticed: When I run ProductExportJob through debugger, and run export feature for multiple platforms, every platform other than the one I'm running on (i.e. TargetPlatform.getState() --native) creates it's own state via fStateCopy = main.getFactory().createState(main); All these newly creative states contain BundleDescriptions that are slightly different from what the original (native state) in that stateBits in BundleDescriptionImpl are slightly different. In my native Windows XP state for instance these bits are set to 203 whereas in Mac OS state these bits are set to 202. This causes the PDEState.getResolvedBundle call to fail on every bundle in question because it's respective isResolved call is failing, hence the bundle gets default version of 0.0.0, which in turn throws a CoreException in FeatureBuildScriptGenerator: if (model == null) { .... throw new CoreException(new Status(IStatus.ERROR, PI_PDEBUILD, EXCEPTION_PLUGIN_MISSING, message, null)); } Once again, I apologize if this info is completely useless, <--- first time poster here :(. I hope someone can fix this for the 3.2 release.
Dominik, the initial problem was a UI problem, now it ends up in the PDE build bucket but I can succesfully export product from within the ide. Could you give precise steps or examples to reproduce the problem?
To Pascal Rapicault Hello, To reproduce this bug, please follow these instructions: Download Ecplise 3.2M5a, RCP SDK 3.2M5a and the RCP Delta Pack 3.2M5c from this page http://download.eclipse.org/eclipse/downloads/drops/S-3.2M5a-200602231656/index.php Create a target folder with RCP SDK and the Delta Pack. Create a new rcp plugin project using mail template. Make it use the just created target via "Preferences" --> "Plug-in Development" --> "Target Plateform". Then create a "Product Configuration" for your project and open it. Click on "Eclipse Product export wizard" under "Exporting". Choose "Export for multiple platforms", check at least one other plateform you are using. Click on "Finish" This is it...
Moving to PDE/UI
The cross-platform builds are failing because we are passing pde/build a bad state. This problem was introduced after PDE started setting multiple environment dictionaries on its state. When we copy the state during cross-platform export, we were only copying one dictionary only. The dictionary contained the JRE1.1 EE profile, so this resulted in many bundles being unresolved, so PDE/Build was choking. Fixed.
