core-jgi/org.adempiere.pipo.handlers/.settings/org.eclipse.jdt.core.prefs

eclipse.preferences.version=1
org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled
org.eclipse.jdt.core.compiler.release=enabled
IDEMPIERE-3531:setting output build, jdk follow project convert from pure plugin to maven a mavent project convert from plugin have flow default rule 1. maven project prefer setting JRE to Execution environment, so .classpath is updated 2. java class compliment to target/classes/, so build.propertie is updated 3. JDK compliance configuration setting per project (only this option), so .settings/org.eclipse.jdt.core.prefs is created extra setting about warning done manual to resolved https://bugs.eclipse.org/bugs/show_bug.cgi?id=367431 it happend on bundle use non-standard java package org.adempiere.base/.settings/org.eclipse.jdt.core.prefs org.adempiere.ui.swing/.settings/org.eclipse.jdt.core.prefs on org.adempiere.server, old method add accessrules to classpathentry don't work for maven build. so change to warning method make it consitent with other org.adempiere.server/.settings/org.eclipse.jdt.core.prefs 2018-02-03 01:39:47 +07:00			`eclipse.preferences.version=1`
			`org.eclipse.jdt.core.compiler.codegen.inlineJsrBytecode=enabled`
IDEMPIERE-3798:Move iDempiere default branch to openjdk 10 change targetPlatform and classpath to JavaSE-10 2018-10-16 07:08:34 +07:00			`org.eclipse.jdt.core.compiler.release=enabled`