173697 – Product export does not satisfy the vm specified in the .product

Bug 173697 - Product export does not satisfy the vm specified in the .product

Summary: Product export does not satisfy the vm specified in the .product

Status:	ASSIGNED

Alias:	None

Product:	PDE
Classification:	Eclipse Project
Component:	Build (show other bugs)
Version:	3.3
Hardware:	PC Windows XP

Importance:	P3 normal with 1 vote (vote)
Target Milestone:	---
Assignee:	pde-build-inbox
QA Contact:

URL:
Whiteboard:	stalebug
Keywords:

Depends on:
Blocks:

Reported:	2007-02-09 16:24 EST by Pascal Rapicault
Modified:	2022-11-16 11:54 EST (History)
CC List:	1 user (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 Pascal Rapicault

2007-02-09 16:24:08 EST

The recent addition to specify vm in the product file is not supported by the PDE Build export operation.
One direction is to use the id specified as the property and this property would have to be defined in the builder build.properties by the user.
We should look at which property PDE UI sets in the feature build.properties and do the same.

Comment 1 Andrew Niefer

2007-02-09 16:38:30 EST

To clarify, I believe that PDE/UI sets root properties for the vm.  This means that the product export will work.

It is the headless build from .product file using productBuild.xml that won't work.

Comment 2 DJ Houghton

2007-04-18 14:27:57 EDT

Deferred.

Comment 3 Lars Vogel

2018-12-03 09:13:08 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 4 Lars Vogel

2018-12-03 09:13:32 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 5 Eclipse Genie

2020-11-25 11:49:59 EST

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.

--
The automated Eclipse Genie.

Comment 6 Eclipse Genie

2022-11-16 11:54:41 EST

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.

--
The automated Eclipse Genie.