core-jgi/org.adempiere.report.jasper.../.classpath

<?xml version="1.0" encoding="UTF-8"?>
<classpath>
	<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"/>
	<classpathentry kind="src" path="src/"/>
	<classpathentry kind="output" path="target/classes"/>
</classpath>
* committed to osgi bundle. * remove ejb, created md5 filter to provide http way of retrieving md5 for report file 2010-07-14 10:41:52 +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"/>`
Update .project and .classpath using PDE tools. (transplanted from 1970ec9a52c07a50ca732e8491a60c45ea633886) 2011-06-01 09:32:12 +07:00			`<classpathentry kind="con" path="org.eclipse.pde.core.requiredPlugins"/>`
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="src" path="src/"/>`
			`<classpathentry kind="output" path="target/classes"/>`
* committed to osgi bundle. * remove ejb, created md5 filter to provide http way of retrieving md5 for report file 2010-07-14 10:41:52 +07:00			`</classpath>`