Headless PDE Build and Java Compiler Compliance?

The manifest editor in PDE will help you set it to the correct value.

Thanks for the follow-up Konstantin! The bundles currently have this property set in the MANIFEST. MF file so that is already set.

I assumed by providing the default values of 1.5 for both the javacSource and javacTarget would cover any bundles that might have this property changed or not supplied (e.g. , future bundles). As far as setting the JavaSE-1.6 property, does this tell PDE to use the Java JDK/JRE 1.6 distribution? My utlimate goal is to have 1.6 be used when more than one version of the JRE/JDK exists on the same machine.

Would this be controlled only by the JAVA_HOME variable? – Michael Jul 12 at 17:17 PDE build determines the ideal Java version that a given plugin needs to be built with based on plugin metadata. Then it looks at your build.

Properties to find the matching JDK. If it doesn't find matching one, it searches for fall-back versions. Ideally, you should build with what's the plugin's minimum compatibility level.

That will not only set language level appropriately, but also catch accidental use of classes introduced in a newer version of Java. – Konstantin Komissarchik Jul 12 at 19:50.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.