With the use of tycho and Maven, we should let the Eclipse Maven integration tool generate .classpath instead of storing it as part of the git repository. As it is, with .classpath as part of the repository, it tends to create false changes when we move to a newer release of Eclipse. With Eclispe 2020-09, false changes (change the ordering of some elements) have been created for org.adempiere.ui.zk/.classpath and org.idempiere.webservices/.classpath).
Hit the following road block:
can’t find a way to auto include <attribute name="add-exports" value="java.naming/com.sun.jndi.ldap=ALL-UNNAMED"/> to .classpath generated by m2e
can’t find a way to atuo include <attribute name="add-exports" value="java.base/sun.security.tools.keytool=ALL-UNNAMED"/> and <accessrule kind="accessible" pattern="sun/security/tools/*"/> to .classpath generated by m2e
maybe we add a script to adjust .classpath
so workflow for setup environment become
1. run mvn validate to download lib
2. import exist maven project to generate .classpath
3. run script
I think the prefer solution is to remove the need of the 2 classpath attributes above. The less dependency on private jdk classes, the better.