Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 273579

Summary:	Product export wizard fails on HP-UX Itanium
Product:	[Eclipse Project] PDE	Reporter:	Matthew Dickie <m.dickie>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	major
Priority:	P3	CC:	aniefer, caniszczyk, curtis.windatt.public, darin.eclipse
Version:	3.4.2
Target Milestone:	---
Hardware:	Other
OS:	HP-UX
Whiteboard:	stalebug

Description Matthew Dickie

2009-04-24 08:08:03 EDT

Build ID: M20090211-1700

Steps To Reproduce:
On HP-UX Itanium:
1. In a new workspace, create a new plugin project, called 'foo.test'. Select one of the templates (I chose 'Hello, world!').
2. In the new plugin project, create a new product configuration with the file name called test.product
3. In the overview tab, where it says 'Specify the product identifier', click the 'New...' button. Enter the product ID as foo.test.product. Select the application org.eclipse.ui.ide.workbench.
4. Click the configuration tab. Add the plugin foo.test. Click the 'Add Required Plug-ins' button.
5. Go back to the overview tab. Under exporting, click on the 'Exclipse Product export wizard' link. Select the 'Archive file' radio button under 'Destination' and enter a filename. Ensure that 'Synchronize before exporting' is selected. Click 'Finish'.

The export process starts but after barely a second an error dialog appears, with the content 'Error. Reason: Problems during export'. Clicking the 'Details >>' button shows a text area with 4 identical errors, each reading:
'java.io.FileNotFoundException: <workspace dir>/.metadata/.plugins/org.eclipse.pde.core/temp/org.eclipse.pde.container.feature/build.xml (No such file or directory (errno:2))

More information:
It seems the export wizard is trying to run an ant build.xml that it should have created, but didn't.

Now, I notice that there are a number of places in the Product Configuration Editor where there are four tabs: 'windows', 'macosx', 'solaris' and 'linux'. This makes me suspect that perhaps the product configuration editor only supports these platforms, and not HP-UX. However, this is not mentioned in any documentation, and it seems strange that the PDE would only partially support some platforms (after all, what's so different between HP-UX and solaris). If the Product Configuration Editor is not intended to support HP-UX then I would expect this to be made more clear. For example, I would expect a 'unsupported platform' message to appear when I try export a product on HP-UX

Comment 1 Curtis Windatt

2009-04-24 10:03:37 EDT

Related to bug 269573 or maybe bug 271103?

Comment 2 Matthew Dickie

2009-04-24 10:14:24 EDT

Strangely, this problem is occurring in one of my workspaces and not others. I
was previously working on Linux with a
~/devel/eclipse-workspaces/acme-workspace. When I started working with HP-UX I
found that using the same workspace caused a problem as run configurations on
HP-UX need a -Dosgi.locking=none argument, so I created a workspace at
~/devel/eclipse-workspaces/hpux-itanium/acme-workspace for developing with
HP-UX. At both workspaces all the projects are imported (as existing projects,
and not copied into the workspace) from ~/devel/acme. This problems occurs at
the hpux-itanium/acme-workspace workspace, and at the temporary workspace I
created to demonstrate this problem for the bug report (as explained above),
but not at the  original acme-workspace workspace. I can't find any significant
difference between the workspaces that might explain this. They are both within
my home directory on the same drive.

I would like to look into this further today, but we have an imminent release, and I have other platforms to port to. I expect to have more time next week.

Comment 3 Andrew Niefer

2009-04-24 16:01:03 EDT

Export works for me using I20090421-0930 both with and without p2 metadata.  (Though I need to account for osgi.locking=none when doing p2 metadata, see bug 273640).

Both bug 269573 and bug 271103 are unrelated. 269573 simply means you can't customize the export with platform specific launching/jvm arguments.


org.eclipse.pde.container.feature/build.xml is a critical file during export.  If we had failed to generate it you should have gotten a "Cannot write script" error.

Compilation would not have occurred without this script.  In your newsgroup post you said this error comes "soon ater the packaging starts".

Comment 4 Darin Wright

2009-04-27 11:19:01 EDT

(In reply to comment #3)
> Export works for me using I20090421-0930 both with and without p2 metadata. 

Just a note that this bug was reported against 3.4.2. The claim (from Andrew) is that this is working in 3.5. Matthew, can you try using 3.5 to verify this is fixed?

Comment 5 Eclipse Webmaster

2019-09-06 16:03:41 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 6 Julian Honnen

2019-09-09 02:35:18 EDT

Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.