4 Commits

Author	SHA1	Message	Date
hieplq	b8caaa1549	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
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
Heng Sin Low	0a66bfb4d5	IDEMPIERE-491 Caching data can generate problem. Fixed fragment build configuration.	2012-12-04 22:03:23 +08:00
Heng Sin Low	a7d41c111c	IDEMPIERE-491 Caching data can generate problem. Improve startup of hazelcast service. Added fragment to allow modification of hazelcast service configuration.	2012-11-27 22:29:02 +08:00