Bug 542810 - apt is not using runtime from the java project (its using the runtime eclipse runs with)
Summary: apt is not using runtime from the java project (its using the runtime eclipse...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: APT (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Generic inbox for the JDT-APT component CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-14 10:34 EST by Michael Seele CLA
Modified: 2023-04-30 06:05 EDT (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 Michael Seele CLA 2018-12-14 10:34:12 EST 
When i configure apt with project specific settings, i want apt to use the project runtime (e.g. java 1.8).
But what apt is using, is the eclipse runtime (e.g. java 11). 

This is illogical and causes us great problems because we some classes that are available in java 8 are not available in java 11 and therefor we need to run eclipse with the same runtime we use in the project.
Comment 1 Eclipse Genie CLA 2020-12-04 16:14:04 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 2 Michael Seele CLA 2020-12-07 01:12:37 EST 
Problem has not been solved and should remain open
Comment 3 Eclipse Genie CLA 2023-04-30 06:05:49 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.

--
The automated Eclipse Genie.