6c76b7e4b8
IDEMPIERE-3808:collect info to move idempiere to jdk-11 (update lib j2ee take out from jdk)
...
this commit by auto adjust from eclipse (exclude server.product.launch)
== setup eclipse like bellow to get stable build ==
1. keep eclipse at Eclipse 2018-09 (https://www.eclipse.org/downloads/packages/release/2018-09/r )
2. install "java-11-support-eclipse" https://marketplace.eclipse.org/content/java-11-support-eclipse-2018-09-49
3. call update "help/check for update"
4. now that eclipse full support jdk-11 and build stable without any issue
ref:https://groups.google.com/d/msg/idempiere/At6xXFyEcGY/IJ1ETiohCwAJ
2018-12-28 15:11:11 +07:00
942800418e
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
0a010a526d
IDEMPIERE-3798:Move iDempiere default branch to openjdk 10 (update maven project)
...
run auto update maven projec (side effect from 15ccf00c09f5).
2018-10-24 08:56:57 +07:00
82c8c5b31d
IDEMPIERE-3798:Move iDempiere default branch to openjdk 10
...
change targetPlatform and classpath to JavaSE-10
2018-10-16 07:08:34 +07:00
31ad04d7ef
IDEMPIERE-3531:auto update by eclipse when import project to new workspace by choose import exists maven project
2018-02-18 23:41:09 +07:00
9482f02dec
IDEMPIERE-3531:add maven tycho configuration
2018-02-10 16:42:06 +07:00
857c099621
IDEMPIERE-3531:standard bundle version and build properties
...
corect some configurtion of build to compatible with maven
2018-02-03 13:25:48 +07:00
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
4ae72bb050
IDEMPIERE-3136:all stuff relate library of idempiere
...
because each project don't have partical build setting, so let control from workspace
2016-07-07 10:14:33 +07:00
0b2fbe27ae
IDEMPIERE-2245 Platform Upgrade for r3.
2014-10-13 11:05:19 +08:00
05c8df356b
IDEMPIERE-455 Discover and fix FindBugs problems / Eclipse warning.
2012-12-21 11:46:54 +08:00
f5b53b5678
IDEMPIERE-455 Discover and fix FindBugs problems / Eclipse warning.
2012-12-21 11:42:43 +08:00
7c305591ad
Update .project and .classpath using PDE tools.
...
(transplanted from 1970ec9a52c07a50ca732e8491a60c45ea633886)
2011-06-01 10:32:12 +08:00
cc5708c8d0
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 01:00:26 +08:00
hieplq
Heng Sin Low