midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
core-jgi/org.idempiere.hazelcast.ser.../.classpath

14 lines
618 B
Plaintext
Raw Normal View History

IDEMPIERE-491 Caching data can generate problem. Refactor the caching code, added distributed cache and cluster wide cache reset support.
2012-11-21 16:06:02 +07:00
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
IDEMPIERE-4249 Platform Refresh for 7.1z (#19) Upgrade to Tycho 1.7.0, Eclipse 2020-03, Zk 9.0.1 and Jetty 9.4.28
2020-04-30 21:01:19 +07:00
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-11">
IDEMPIERE-3798:Move iDempiere default branch to openjdk 10 change targetPlatform and classpath to JavaSE-10
2018-10-16 07:08:34 +07:00
<attributes>
<attribute name="module" value="true"/>
</attributes>
</classpathentry>
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
<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
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
<classpathentry kind="src" path="src/"/>
Merge with default
2018-03-19 19:50:01 +07:00
<classpathentry exported="true" kind="lib" path="lib/hazelcast-aws.jar"/>
IDEMPIERE-3531:standard lib folder on all project, put library into lib folder, so easy apply parametrize remove some unuse (don't see reference) library
2018-02-02 13:47:07 +07:00
<classpathentry exported="true" kind="lib" path="lib/hazelcast.jar"/>
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
<classpathentry kind="output" path="target/classes"/>
IDEMPIERE-491 Caching data can generate problem. Refactor the caching code, added distributed cache and cluster wide cache reset support.
2012-11-21 16:06:02 +07:00
</classpath>