Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 79494 - Ant Properties not set if Separate JRE used
Summary: Ant Properties not set if Separate JRE used
Status: RESOLVED DUPLICATE of bug 78298
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.0.1   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-25 10:34 EST by Tim Roberts CLA
Modified: 2004-11-25 14:35 EST (History)
0 users

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 Tim Roberts CLA 2004-11-25 10:34:16 EST 
When running an Ant buildfile, via the External Tools Ant Build configuration, 
the properties specified in the Properties tab (I'm just using the global 
properties via the checkbox) are not passed through to Ant if you specify a 
separate JRE on the JRE tab. You also don't have visibility of the 
JDTCompilerAdapter class so maybe the classpath settings don't work either.
Comment 1 Darin Swanson CLA 2004-11-25 12:22:08 EST 
Which properties? Likely a duplicate of bug 78298.

When running in a separate JRE you will not have the Eclipse 
workspace "context" for the build. Therefore to use the JDTCompilerAdapter you 
will need to add the appropriate JDT Core JARs to the Ant runtime classpath.
Comment 2 Tim Roberts CLA 2004-11-25 14:35:11 EST 
The reported bug regarding properties is the same as bug 78298 (i searched for 
existing bugs containing properties so didn't see that one). I will close this 
bug and follow up on 78298.

I've just noticed that the classpath entries change when you switch between 
JRE's which explains the absence of the JDTCompilerAdapter class.

*** This bug has been marked as a duplicate of 78298 ***