Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 316944 - Launcher plugin exported as a jar file
Summary: Launcher plugin exported as a jar file
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: Build (show other bugs)
Version: 3.5.2   Edit
Hardware: Other other
: P3 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: pde-build-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-15 12:29 EDT by Stephen McCants CLA
Modified: 2018-12-03 09:13 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen McCants CLA 2010-06-15 12:29:38 EDT 
Build Identifier: 20100218-1602

While exporting a plugin, the export code makes the following plugin:

org.eclipse.equinox.launcher.motif.aix.ppc_1.0.201.R35x_v20091211

a jar file when it should be a folder.  It does not apparently matter the OS.  See this discussion for problems with it on Windows and Linux:

http://dev.eclipse.org/newslists/news.eclipse.platform/msg64826.html

When it is a jar file, the product will not start, but instead gives the error message:

        0509-022 Cannot load module plugins.
        0509-026 System error: A file or directory in the path name does not exist.
Eclipse:
The Eclipse executable launcher was unable to locate its
companion shared library.


Reproducible: Always

Steps to Reproduce:
1. Create a product to export
2. Export the product using the export wizard
3. Export for multiple platforms and make sure the following is unchecked:
-- Generate metadata repository
-- Allow for binary cycles in target platform
Comment 1 Thomas Watson CLA 2010-06-15 13:28:26 EDT 
Moving to PDE build.  I assume that is where this is going wrong.
Comment 2 Andrew Niefer CLA 2010-06-15 15:52:33 EDT 
This works for me, I need more details. The newsgroup post indicates we have never been able to reproduce this problem.

- Is the product feature based or plugin based?
- does the product explicitly include the org.eclipse.equinox.launcher.* fragments?
- do you have the delta pack?
- what does your target platform look like?  do you have the launcher fragments around anywhere in jar form?

Attaching example project that reproduces the problem would help.
Comment 3 Stephen McCants CLA 2010-06-15 16:33:22 EDT 
-- Plugin based product.
-- No.
-- Not sure how to tell.  We do support builds for multiple platforms that each use special fragments (swt, launcher, filesystem, etc).
- Custom target platform - Eclipse 3.5.2 based with lots of other things like EMF, etc.
Comment 4 Hannes Erven CLA 2017-02-12 17:21:03 EST 
Sorry to comment on an "ancient" issue, but it seems I'm also running into this as of Neon 4.6.2 .

I have a .product definition from which I run the "Eclipse Product export wizard". The complete product export generates about 300 artifacts, with 11 of them necessarily as flat folders (like org.eclipse.equinox.launcher.win32).

About 1 out of 5 export runs, the generated artifacts are ALL jar-files, and the product won't start (cannot locate companion shared library).

This is on win32. I haven't been able to spot any related messages in the Eclipse log.


I'd be glad to help to track down the issue, but where (how) to start?
Comment 5 Lars Vogel CLA 2018-12-03 09:10:24 EST 
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.
Comment 6 Lars Vogel CLA 2018-12-03 09:13:42 EST 
Currently we are not actively enhancing PDE build anymore. Therefore, I close this bug as WONTFIX. 

Please reopen, if you plan to provide a fix.