Final Product Export Procedure

Since GenericFX uses AspectJ (See Note A), the export procedure is a two step approach:

1. Export everything using “Eclipse Product Export Wizard”
2. Export AspectJ-enabled plugins using “Deployable Plug-ins and fragments with AspectJ support” Export Wizard and use them to replace the relevent plugins generated by “Eclipse Product Export Wizard”

Make sure you use Java 1.4 compatibility for both source and .class file.

Note A: This procedure works because AJEER (http://ajeer.sourceforge.net) is used to weave aspects from different plugin together. The procedure will work without AJEER if all AspectJ code used are “intra-plugin” only, i.e., the AspectJ code is visible and used inside the declaring plugin only.

An explaination of the two-step process can be found in AspectJ code not working in RCP Program subsection at the BMUWiki.

For MacOSX export, it is necessary to edit camba.app/Contents/info.plist to include

  <string>-Dosgi.framework.extensions=org.eclipse.transformer</string>
  <string>-Dosgi.parentClassloader=fwk</string>

in the startup arguement, i.e., at the same level as <string>-vmargs</string>

I think MacOSX does not read camba.ini on startup.

Assuming you have a workingcamba in camba directory. On Command Line:

hdiutil create -srcfolder camba camba.dmg
hdiutil internet-enable -yes camba.dmg

Resources:

1. http://www.eclipse.org/swt/macosx/

Follow instruction for Developer:Application:Utilities:PackageMaker

Resources:

1. http://www.centerkey.com/mac/java/