Difference between revisions of "Equinox Integration 2/Tutorial Plugin"
From ADempiere
This Wiki is read-only for reference purposes to avoid broken links.
(→= Activation) |
|||
| Line 9: | Line 9: | ||
** regarding versioning: I found the default versioning scheme using a qualifier (which is replaced by a timestamp at deployment time) quite annoying, because bundles are never overridden - but maybe I missed something here | ** regarding versioning: I found the default versioning scheme using a qualifier (which is replaced by a timestamp at deployment time) quite annoying, because bundles are never overridden - but maybe I missed something here | ||
| − | + | = Activation = | |
* If you need action to be done, specify an activator in the manifest. | * If you need action to be done, specify an activator in the manifest. | ||
* Certainly you may implement the plain BundleActivator, but preferrably use org.adempiere.plugin.utils.AdempiereActivator | * Certainly you may implement the plain BundleActivator, but preferrably use org.adempiere.plugin.utils.AdempiereActivator | ||
Revision as of 12:08, 12 March 2010
If you want to change existing functionality in ADempiere, write a plugin. It is simple!
Create Plugin Project
- In Eclipse, chose New/Plugin Development/Plugin Project
- as a convention, choose a folder under adempiereTrunk/plugins
- The manifest editor opens, fill in appropriate attributes
- regarding versioning: I found the default versioning scheme using a qualifier (which is replaced by a timestamp at deployment time) quite annoying, because bundles are never overridden - but maybe I missed something here
Activation
- If you need action to be done, specify an activator in the manifest.
- Certainly you may implement the plain BundleActivator, but preferrably use org.adempiere.plugin.utils.AdempiereActivator
- You have to import this package in the bundle manifest - it is provided by pluginUtils
Extension Points
Return to ADempiere/Equinox Integration 2
