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

Bug 322773

Summary: Clarify "There is no 'jre.compilation.profile' build entry and the project has Java compliance preferences set"
Product: [Eclipse Project] PDE Reporter: Markus Keller <markus.kell.r>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: b.michael, daniel_megert, stefan.dimov
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Markus Keller CLA 2010-08-16 06:15:44 EDT 
I20100810-0800

I've changed the EE of org.eclipse.jdt.junit on the classpath from J2SE-1.4 to J2SE-1.5 and updated the project-specific compiler compliance settings, but I forgot to update the Bundle-RequiredExecutionEnvironment in the MANIFEST.MF.

After that, I got the following warning on build.properties: "There is no 'jre.compilation.profile' build entry and the project has Java compliance preferences set".

Problems:

- The warning did not appear before (when compliance matched the BREE's compliance)
  => Warning should tell about the mismatch, e.g.: "There is no 'jre.compilation.profile' build entry and the project has Java compliance preferences set that don't match the Bundle-RequiredExecutionEnvironment".

- The problem should have a quick fix that fixes the BREE in the MANIFEST.MF.
Comment 1 Stefan Dimov CLA 2010-08-31 10:10:04 EDT 

*** This bug has been marked as a duplicate of bug 322771 ***
Comment 2 Stefan Dimov CLA 2010-08-31 10:16:58 EDT 
Sorry for closing this bug. It was a mistake ... I'll reopen it
Comment 3 Eclipse Genie CLA 2018-10-28 12:47:30 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.
Comment 4 Lars Vogel CLA 2019-09-02 15:07:24 EDT 
This bug was marked as stalebug a while ago. Marking as worksforme.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
Comment 5 Lars Vogel CLA 2019-09-02 15:08:34 EDT 
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.