midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
core-jgi/org.adempiere.eclipse.equin.../.settings/org.eclipse.jdt.core.prefs

9 lines
441 B
Plaintext
Raw Normal View History

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-3808:collect info to move idempiere to jdk-11 (zk8.6.0.1, eclipse-1812, java11, tycho 1.3) still use local repository for maven.to.p2 to continue update library
2018-12-22 15:49:50 +07:00
org.eclipse.jdt.core.compiler.codegen.methodParameters=do not generate
org.eclipse.jdt.core.compiler.codegen.unusedLocal=preserve
org.eclipse.jdt.core.compiler.debug.lineNumber=generate
org.eclipse.jdt.core.compiler.debug.localVariable=generate
org.eclipse.jdt.core.compiler.debug.sourceFile=generate
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