* 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-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
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
Muhammad Eko
hengsin
hieplq
acanaveral