| Re: [epsilon-dev] EGL, Deplyo and Mailing list |
Hi Horacio, Thanks for the reply. I have now simplified this, so EGX and EGL have been separated as expected. The only breaking changes seemed to be at the DT level in EglLaunchConfigurationDelegate but I think (hope!) this has been fixed too. There is just one bug I’ve encountered: If you create a new run configuration for an EGX file and don’t change the module implementation to EGX before hitting apply, you will get NullPointerException until the run configuration is deleted. When I tested I couldn’t get the UI to default to EGX, not sure if it’s my setup / methodology or a genuine bug. Thanks, Sina From: arcanefoam@xxxxxxxxx Hi all, For some reason some of the last emails didn't make it to my inbox, nor spam, nor anything. So sorry for the late reply. @Sina: I do agree with you simplification. EGX is rule based so it is more reasonable that it exetnds ERL. I also agree on the separate contexts, also because this could eventually result in cross-contamination of the context. So I +1 on the changes. @Jon: Releases are a bit more troublesome because they need to be GPG signed and that bit can not be fully automated, principally cause no one wants to share their credentials on the CI configuration. I think Eclipse has some GPG signing facilities but not sure how it can be used (this is similar to signing Jars when creating updatesites, if memory serves me right). Cheers,
|