midsuit
/
core-jgi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
core-jgi/org.adempiere.install/build.properties

6 lines
115 B
Properties
Raw Normal View History

Turned install into an equinox plugin providing an eclipse application Modified build script to deploy the equinox container https://sourceforge.net/tracker/?func=detail&aid=2700937&group_id=176962&atid=879334
2010-04-29 03:59:00 +07:00
bin.includes = META-INF/,\
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
plugin.xml,\
.
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/
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
source.. = src/