Provide a 'New ALE Project' wizard

[echebbi]

Overview

Should close #98.

Provide a wizard that allows to create an ALE project with:

• either an existing or a new Ecore model
• a .ale file containing only behavior <name>;
• a .dsl file linking the .ecore and the .ale files
• (optional) a Sirius representation of the Ecore model
• (optional) the Java nature

Demo

[echebbi]

I finally managed to create a Sirius representation in the new projects! To be honest this was waaaay too cumbersome.

Next I'll clean the code so that it can be reviewed while I'll write the tests.

[echebbi]

I think I'm almost done, the only remaining issue is that the new UI test does not pass on Jenkins (but succeeds locally).

For what I can see:

• the New ALE Project wizard is not closed on finish, which might caused by missing dependencies,
• the generated model/ folder is empty, which may be caused by the previous issue.

@dvojtise would you have any idea to solve the issue? Otherwise I'll drop the UI test and merely test the WorkspaceAleProject class which is actually responsible of creating the project: I don't want to spend hours investigating this.

[echebbi]

Sooo. Actually I get issues even when testing directly the back-end (exception thrown when trying to create a minifsm project):

org.eclipse.core.runtime.CoreException: Parent of resource: /minifsm is marked as read-only.
	at org.eclipse.emf.ecoretools.ale.ide.helloworld.tests.WorkspaceAleProjectTest.testCreateNewStandaloneProject(WorkspaceAleProjectTest.java:75)
Caused by: java.nio.file.AccessDeniedException: /minifsm
	at org.eclipse.emf.ecoretools.ale.ide.helloworld.tests.WorkspaceAleProjectTest.testCreateNewStandaloneProject(WorkspaceAleProjectTest.java:75)

I already faced a similar exception in a personal project and did not managed to overcome it yet. Even if the workspace is marked as read-only UI tests are able to create new projects so there must be a way to fix this but to be honest I'm fed up with fighting Eclipse all the time.

@dvojtise would you, by any chance, know how to solve this? Otherwise I would suggest to merely discard the tests: we may lost way more time making them work instead of manually testing the wizard when we modify it.

[dvojtise]

no, sorry, I never have seen this msg in other test projects

[echebbi]

@dvojtise I ended up dropping the tests. Apart from that the code is ready for a review.

[echebbi]

@dvojtise any news on this? PR #116 and #117 are also ready to be merged. If you don't have the time for a code review, can I take the liberty to merge them?

[dvojtise]

yes, if the CI compiles and meaningful tests are OK (I agree to not spend too much time on UI tests and comment them if this makes sense) then go ;-)