core-jgi/org.adempiere.pipo
hieplq 31ad04d7ef IDEMPIERE-3531:auto update by eclipse when import project to new workspace by choose import exists maven project 2018-02-18 23:41:09 +07:00
..
.settings IDEMPIERE-3531:auto update by eclipse when import project to new workspace by choose import exists maven project 2018-02-18 23:41:09 +07:00
META-INF IDEMPIERE-3531:some plugin don't include class on output maven when export 2018-02-11 00:37:05 +07:00
OSGI-INF IDEMPIERE-1223 Use ClassName as Name of OSGi component. 2013-07-31 16:30:15 +08:00
schema Updated extension point documentation formatting. Remove the use of osgi: prefix for form, modelvalidator and process to ease migration, the framework will now always check whether an implementation exists in the extension registry before checking the java classpath. Rename org.adempiere.osgi in swing to org.adempiere.ui.swing.factory and drop the incomplete IMenuAction extension in swing ( will come back to this later ). 2010-12-20 10:46:25 +08:00
src/org/adempiere IDEMPIERE-3551 1008086 - External (non-plugin) 2Pack automation 2017-11-08 18:29:30 +01:00
.classpath IDEMPIERE-3531:setting output build, jdk follow project convert from pure plugin to maven 2018-02-03 01:39:47 +07:00
.project IDEMPIERE-3531:add maven tycho configuration 2018-02-10 16:42:06 +07:00
build.properties IDEMPIERE-3531:some plugin don't include class on output maven when export 2018-02-11 00:37:05 +07:00
plugin.xml IDEMPIERE-359 Add OSGi Service support for existing extension point. 1) Separate osgi service and equinox extension locator API. Service.locator() for OSGi service and EquinoxExtensionLocator.instance() for equinox extension. 2) Use OSGi service for all singleton component ( all factories and most services ) and equinox extension for others ( UI object, Process instance and PIPO handlers). 2013-02-13 16:15:43 +08:00
pom.xml IDEMPIERE-3531:add maven tycho configuration 2018-02-10 16:42:06 +07:00