hieplq d7808da56a 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
..
.settings	IDEMPIERE-3531:setting output build, jdk follow project convert from pure plugin to maven	2018-02-03 01:39:47 +07:00
META-INF	New version	2017-10-31 23:12:29 +01:00
src/org/adempiere/plugin/utils	IDEMPIERE-3551 1008086 - External (non-plugin) 2Pack automation	2017-11-08 18:29:30 +01:00
.classpath	IDEMPIERE-3531:setting output build, jdk follow project convert from pure plugin to maven	2018-02-03 01:39:47 +07:00
.project	Refactoring to make project and folder name the same as the bundle symbolic name. Migrate to use eclipse feature and product configuration ( build is broken, to fix later )	2010-09-29 15:25:34 +08:00
build.properties	IDEMPIERE-3531:setting output build, jdk follow project convert from pure plugin to maven	2018-02-03 01:39:47 +07:00