5 Commits

Author	SHA1	Message	Date
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
hieplq	b6d9886732	IDEMPIERE-3531:standard lib folder ... on all project, put library into lib folder, so easy apply parametrize remove some unuse (don't see reference) library	2018-02-02 13:47:07 +07:00
Heng Sin Low	816e27a8e2	IDEMPIERE-2245 Platform Upgrade for r3. Fix Jenkin build error ( Patch from Carlos ). Fix login page show wrong version info.	2014-10-16 14:34:12 +08:00
Heng Sin Low	0b2fbe27ae	IDEMPIERE-2245 Platform Upgrade for r3.	2014-10-13 11:05:19 +08:00
Heng Sin Low	83715fa436	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