midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
core-jgi/org.adempiere.report.jasper.../.classpath

18 lines
1.2 KiB
Plaintext
Raw Normal View History

Fixed Eclipse class paths for Multi-project setup.
2009-10-14 22:01:11 +07:00
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
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.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8"/>
<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>
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/castor-core.jar"/>
<classpathentry exported="true" kind="lib" path="lib/castor-xml.jar"/>
IDEMPIERE-3136 update jasper report to use P2 / enable DejaVu Sans and DejaVu Serif default jasper to render bold/italic properly at least with these two - same as 450fe05 but for dev/maven
2018-08-30 01:37:39 +07:00
<classpathentry exported="true" kind="lib" path="lib/jasperreports-fonts.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/jasperreports-chart-customizers.jar"/>
<classpathentry exported="true" kind="lib" path="lib/jasperreports-chart-themes.jar"/>
<classpathentry exported="true" kind="lib" path="lib/jasperreports-functions.jar"/>
<classpathentry exported="true" kind="lib" path="lib/olap4j.jar"/>
<classpathentry exported="true" kind="lib" path="lib/rhino.jar"/>
<classpathentry exported="true" kind="lib" path="lib/spring-beans.jar"/>
<classpathentry exported="true" kind="lib" path="lib/spring-core.jar"/>
<classpathentry exported="true" kind="lib" path="lib/xmpcore.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"/>
Fixed Eclipse class paths for Multi-project setup.
2009-10-14 22:01:11 +07:00
</classpath>