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

6 lines
115 B
Properties
Raw Normal View History

1) http://kenai.com/jira/browse/HENGSIN-6, RUN_setup.sh failure Use the static method getLogger instead of using a static logger variable. The logger is created as needed inside the getLogger method. 2)http://kenai.com/jira/browse/HENGSIN-3, properties file wrongly created Patch accepted. 3) http://kenai.com/jira/browse/HENGSIN-4, Cannot connect to http://localhost:8080/admin/adempiereMonitor Always set default level for root logger in CLogMgt initialization. 4) http://kenai.com/jira/browse/HENGSIN-5, Build fails by default requiring directory lib/plugins Modify utils_dev/build.xml to ensure the existence of the lib/plugins folder. 5) Module refactoring * Remove client bundle dependency from the zkwebui bundle. Common UI code of the 2 bundle is moved into the new uibase bundle. * Remove client bundle dependency from server side bundle. The swing specific jasper report code is moved into the new JasperReportsClient bundle. * Move most swing code that is still in the base bundle into the client bundle. Many swing client specific code in Env.java (base bundle) is move into the AEnv.java (client bundle). * Default handlers for 2Pack is moved into the new pipoHandlers bundle. All loading of 2pack handler is now done using the equinox extension mechanism. 6) Extension point * Added process, form and modelvalidator extension point base on the existing work done by Jorg Viola in the osgi1 branch. 7) The pipo bundle is move from plugins/pipo to /pipo ( relative to the workspace ) due to ant4eclipse have problem building the bundle using the previous layout. 8) New workflow editor and rendering implementation using netbeans visual library. The implementation is shared the by swing and zk client.
2010-08-20 15:05:06 +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/