This current approach has the following issues:
- it essentially requires Eclipse. I think our intent with ecore did not include making it Eclipse - specific
- It has special treatment to isolate source files outside of the normal source path, and special readme's to have the user include these in the source path, after they add ecore support jars from Eclipse, which they would have to obtain somehow.
A simpler approach would be to
- have no special treatment for the ecore examples
- ship (distribute) the needed ecore jars with the examples, in a /lib directory
This would allow stand-alone running of the ecore examples without Eclipse being installed or available.
The Jars in question are
- org/eclipse/emf/common-2.1.0.jar (134KB)
- org/eclipse/emf/ecore-2.1.0.jar (625 KB)
- org/eclipse/emf/ecore-xmi-2.1.0.jar (142KB)
These we can distribute in binary form only under "category b" license terms - we have to include things in the NOTICE/LICENSE files for this.
(Note that the maven build already gets these Jars from the maven repos and mvn eclipse:eclipse on the uimaj-examples project puts these jars into the generated classpath.)
Should we change things to this simpler approach but which requires us to ship the 3 ecore support Jars, or leave things the way they are?
I'm on the fence... in favor of simplicity, but not wanting to grow our bin distribution by 900KB. Other opinions?