This is a guide on how to use Eclipse IDE to create a new plugin for your legacy ADempiere work or modules. We use 2Pack to Packout the DB changes and then PackIn back for a new instance. Movies on this are also linked below.
1. Launch a new iDempiere java client and apply your migration scripts that has your own customized model.
2. Packout the new module (see movie below)
3. Develop a new plugin in Eclipse IDE with iDempiere source and place your code packages in the plugin (see movie below)
4. PackIn using the ADempiereActivator with 2Pack.zip attached to META-INF of your new plugin (see movie below)
The new plugin can also be deployed to work in a binary iDempiere client but will be shown in a future show about the new Eclipse P2 upgrade process.
I was missing only one thing: How to make the 2Pack when we have personalizations on the standard tables. On LBR project we have some fields added to standard ADempiere tables, like C_Invoice, AD_Org, C_bpartner and many others. This way we can make an OSGi plugin based on the LBR extensions!
Another thing I didn't get well was how the updates on the plugin can be made, adding new tables, new fields, and etc. But I think that this is subject for another topic.
It is very simple. Just Pack Out those windows that has your new changes or additional tabs or fields to them. During Pack In in iDempiere it merely updates back the same windows if they exist and add those fields that do not. Notice how i did it for AssetMeter and MeterLog, which are two new tabs in the same Asset Window.
On your second matter, if you change anything to such AD, again, Pack Out that very window it sits in. If it does not work, give me the screenshot of your Pack Out item.
There are more new tutorials in PDF format i done from other projects which has more tips and secrets i learned and i put them as an index of links for convenient reference by developers and potential contributors alike.
1. Migration of Libero HR Payroll and how to use Libero Payroll demystifying its inner secrets properly for the first time.
2. Migration of SF Android that includes creating new Web-Services plugin and including some of the Android mobile side operations.
In recent times, I have evolved the best practice in developing on iDempiere. There is a way to do things elegantly and save the destruction of the core engine over the long term. Read http://www.red1.org/BlackPaper.pdf
I am also making a killer plugin that can reduce all AD and module creation work to a mere minute to minute affair instead of long days into winter. See my new forum posting on this viewtopic.php?f=45&t=1831