thank you for this awesome example. I really like the idea of e4-efxclipse on maven.
I am using this example to build my own application and everything works quite good at the moment. However, right now i have added a new fragment project to my own setup and this drastically increases the launch time of my application from maven. The fragment consist of a simple part with a controller. The part basically only contains an empty Tableview. This fragments adds the part to a partstack defined in the global Application.e4xmi. While all of this works, the launch time of my application increased to around 2 minutes, which makes it very hard to use this approach. Removing the fragment project immediately reduces the launch time again, so it must be related to the fragment.
Hi,
thank you for this awesome example. I really like the idea of e4-efxclipse on maven.
I am using this example to build my own application and everything works quite good at the moment. However, right now i have added a new fragment project to my own setup and this drastically increases the launch time of my application from maven. The fragment consist of a simple part with a controller. The part basically only contains an empty Tableview. This fragments adds the part to a partstack defined in the global Application.e4xmi. While all of this works, the launch time of my application increased to around 2 minutes, which makes it very hard to use this approach. Removing the fragment project immediately reduces the launch time again, so it must be related to the fragment.
Any ideas what could be the problem here?