core-jgi/org.idempiere.ui.zk.selenium/build.properties

bin.includes = META-INF/,\
               OSGI-INF/fitfixturefactory.xml,\
               OSGI-INF/,\
               .
output.. = target/classes/
source.. = src/
IDEMPIERE-92 - Integrate Selenium. Implemented selenium and fitnesse integration using FitLibrary and FitLibraryWeb. Added FitLibrary and FitLibraryWeb documentation to fitnesse root. Added 2 example fitnesse test for zk. 2012-12-13 02:35:08 +07:00			`bin.includes = META-INF/,\`
			`OSGI-INF/fitfixturefactory.xml,\`
IDEMPIERE-3531:some plugin don't include class on output maven when export "bin.includes = ." is mandatory for maven build 2018-02-11 00:37:05 +07:00			`OSGI-INF/,\`
			`.`
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			`output.. = target/classes/`
			`source.. = src/`