Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
EGF release for Kepler.
The functional scope EGF 1.1.0 is close to EGF 1.0.0. EGF Core has not evolved. EGF is still released with two portfolios (i.e., the Enhancement of the EMF Generation and Build EGF Portofolio) and default language tasks (i.e., Ant, Acceleo, ATL, Jet). Other language taks (i.e., Acceleo 2, Jython, JRuby) can be downloaded from EGF EclipseLabs.
The project leadership certifies that the APIs in this release are "Eclipse Quality".
The general architecture of EGF is: 1) the EGF Engine extended by Engine Extensions, 2) extended by a set of generation portfolios. The "development & reuse process" here displays how portfolios can be iteratively combined to create new factories and extensions. The "example of EGF Factory" here shows a factory component which combines invocations of heterogeneous languages (e.g., Java, Ant, Jython), tools (e.g., Jet, ATL), and factory component.
No security issue identified.
EGF intends to conform to the User Interface Guidelines.
No EGF component is deprecated so far.
EGF does not implement any standard.
EGF was presented at different conferences during 2011-2012 (EclipseDay Paris 2011, Modeling Symposium US, Neptune 2012). Statistics: about 1,800 downloads / month for EGF with Juno. IWG: EGF will be part of the Polarsys IDE Package 1.0.0. EGF provides two generation portfolios in order to examplify how develop one's portfolio. Tutorials are available on the EGF Wiki. An EGF EclipseLabs project was created for external contributions.