Community
Participate
Working Groups
It is easy to forget, as I have done numerous times when regenerating one of the many Ecore/UML models in Papyrus, to clean up the MANIFEST.MF that has dependency re-exports generated. It should not be difficult to create a custom template that does not use re-exports in the MANIFEST.MF and to update all genmodels to use it via the "Dynamic Templates" capability of EMF code generation. The Toolsmiths APIs even provide for calculation of the version ranges to emit, which the base EMF template does not. One possible drawback of this solution is that it will be necessary to keep this custom template in sync with changes as they are made in the default template in EMF. But this is mitigated by the expectation that such changes will be rare.