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

Bug 74880

Summary:	[workspace] PDE build does not use project class libraries
Product:	[Eclipse Project] PDE	Reporter:	Pierre Carlson <mpcarl>
Component:	Build	Assignee:	pde-build-inbox <pde-build-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	danschum, jeffmcaffer, timluke, wassim.melhem
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:
Bug Depends on:	106594
Bug Blocks:

Description Pierre Carlson

2004-09-23 19:05:16 EDT

When exporting a plug-in using the "Deployable plug-ins and fragments" option,
the PDE build compiles against the default JVM class libraries instead of those
specified in the project.

To reproduce the problem I installed and configured the IBM 131 JVM and the IBM
141 JVM.  I set the IBM 141 JVM as the default.  I then created a plug-in
project and removed the 141 class libraries and selected the 131 class
libraries.  Once the project was created I added this line to the start method:
  com.ibm.jvm.Dump.HeapDump();

The plug-in compiles correctly in the IDE.  I then exported this project using
the "Deployable plug-ins and fragments" option.  The export fails with the
following message in the log file:

----------
1. ERROR in
C:\eclipse\301GA\eclipse\workspace\HelloWorld131\src\HelloWorld131\HelloWorld131Plugin.java
(at line 36)
	com.ibm.jvm.Dump.HeapDump();
	^^^^^^^^^^^^^^^^
com.ibm.jvm.Dump cannot be resolved or is not a type
----------
1 problem (1 error)

Comment 1 Andrew Niefer

2007-03-28 16:59:24 EDT

There are no plans to make pde.build aware of workspace settings.

However, I believe that pde.ui is setting execution environment properties for the export.  In this case setting a Bundle-RequiredExecutionEnvironment for the bundle would achieve the desired results.

As well, it is possible to set the property "bootClasspath" in the plugin's build.properties file to explicitly point to the desired libraries.

CC'ing Wassim so he can correct me if I'm wrong about the Execution Environments.

Comment 2 Wassim Melhem

2007-03-28 17:12:41 EDT

>There are no plans to make pde.build aware of workspace settings.

Andrew, this statement seems a bit pessimistic in a terminal kind of way.

The workspace-awareness issue will not be resolved, not even in a Blue-Sky-kind of way?  It's one feature that people want a lot.

bug 106594 seems more optimistic at least.

Comment 3 Andrew Niefer

2007-03-28 17:29:20 EDT

Perhaps "LATER" would have been a better choice.  What I was really try to say was that the desired results can be achieved in some manner by what we have now.  This is not something that would get fixed on its own, but is rather something that would almost come for free as part of something larger like bug 106594