* IDEMPIERE-5448 Can't launch unit test with Eclipse 2022-09
- upgrade to tycho 3.1.0-SNAPSHOT
- set maven compiler source and target level to 11
- upgrade to junit 5.9.1
* IDEMPIERE-5448 Can't launch unit test with Eclipse 2022-09
- Change tycho version to 3.0.3
* IDEMPIERE-5448 2023 June Platform Update
* IDEMPIERE-5448 2023 June Platform Update
- Explicitly set target, source and release level to JavaSE 11
* IDEMPIERE-5448 2023 June Platform Update
- Use 3.0.5-SNAPSHOT to fix stack overflow error.
* IDEMPIERE-5448 2023 June Platform Update
- Change source, target and release level to JDK 17
- Update target platform name to idempiere-230620
* IDEMPIERE-5448 2023 June Platform Update
- Fix LogFactory ClassNotFound exception with Eclipse 2023-06
* IDEMPIERE-4586 Update translation of Client to Tenant
* Exclude AD_Ref_List.Name from the update as it impacts too many constants generated in X_ classes
* * update the Updated column too so that it is easier to trace back which records have been updated (as suggested by Heng Sin)
* * Update some additional messages that becomes duplicated (as reported by Nicolas)
* * Add updates to AD_Tab.CommitWarning (as reported by Nicolas)
* iIDEMPIERE-4214 Javadoc: correct warnings on newest java version / fix problem to generate javadoc again
* IDEMPIERE-4214 Javadoc: correct warnings on newest java version / Fix javadoc warnings
* IDEMPIERE-4488 Remove .classpath from repository
* IDEMPIERE-4488 Remove .classpath from repository
add ignore for .classpath
* IDEMPIERE-4488 Remove .classpath from repository
remove ".settings/org.eclipse.jdt.core.prefs"
* IDEMPIERE-4488 Remove .classpath from repository
fix false status report for /bin and .project
* IDEMPIERE-4251 Constant definition for all Env Context
replace "#Date" with Env.DATE
* IDEMPIERE-4251 Constant definition for all Env Context
replace "#.." with constant at Env
* IDEMPIERE-4251 Constant definition for all Env Context
Merge patch from Carlos
* IDEMPIERE-4298: remove Bundle-RequiredExecutionEnvironment
when build by tycho value of Bundle-RequiredExecutionEnvironment and jdt need to compatibility
in case we use Bundle-RequiredExecutionEnvironment = 11 then can't build by jdk != 11
so stick on fix value isn't good
eclipse now also support Require-Capability, so don't need Bundle-RequiredExecutionEnvironment anymore
* IDEMPIERE-4298:support update jdk (jdk 12 13 14)
default environment still jdk-11 but you can build for any jdk by below command
export JAVA_HOME=path to jdk
mvn verify -Djdk.version=11
in case on JAVA_HOME is jdk 14 then can set jdk.version for 11, 12, 13, 14 and same for other jdk
at moment java 14 just support on eclipse 2020-03 with install plugin
Java 14 Support for Eclipse 2020-03 (4.15)
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
luzpaz
Carlos Ruiz
hengsin
hieplq