midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
12,338 Commits 1 Branch 0 Tags 397 MiB
Commit Graph

7 Commits

Author SHA1 Message Date
hieplq 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
hieplq 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
hieplq 9482f02dec IDEMPIERE-3531:add maven tycho configuration 2018-02-10 16:42:06 +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
hieplq 84d5b6c734 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 11:00:02 +07:00
Heng Sin Low 0b2fbe27ae IDEMPIERE-2245 Platform Upgrade for r3. 2014-10-13 11:05:19 +08:00
Heng Sin Low 39cf26d40c IDEMPIERE-206 Integrate fitnesse with iDempiere 2012-11-27 16:29:04 +08:00