core-jgi/org.adempiere.eclipse.equin.../build.properties

bin.includes = META-INF/,\
               plugin.properties,\
               .
javacErrors.. = -assertIdentifier,-enumIdentifier
output.. = target/classes/
source.. = src/
Added patch equinox servlet bridge: 1) Filter support from http://angelozerr.wordpress.com/2010/09/08/osgi-equinox-in-a-servlet-container-step4/ 2) Modify to work with OSGi web container ( geminiweb ) instead of normal servlet container 2011-01-11 00:00:26 +07:00			`bin.includes = META-INF/,\`
IDEMPIERE-3531:some plugin don't include class on output maven when export "bin.includes = ." is mandatory for maven build 2018-02-11 00:37:05 +07:00			`plugin.properties,\`
			`.`
IDEMPIERE-455 Discover and fix FindBugs problems / Eclipse warning -> build 2012-12-21 22:05:17 +07:00			`javacErrors.. = -assertIdentifier,-enumIdentifier`
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			`output.. = target/classes/`
IDEMPIERE-3531:some plugin don't include class on output maven when export "bin.includes = ." is mandatory for maven build 2018-02-11 00:37:05 +07:00			`source.. = src/`