Hello,
I tested the updated version of the setup file ! it works perfectly : EMF code is well generated, xtext generation (after
y press on the console to download the ANTLR jar) is performed automatically. I even did not need to clear all projects as we do before.
However I get 3 errors (disappeared after cleaning the specific project) dealing with the defaultLanguage implementation
(see figure bellow) and 2 empty working sets: Common Test and C++ Test. I did not follow all news in the defaultlanguage implementation, but I expect that it is not yet finished and those working set will soon be full ;)
Asma
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Ernesto Posse
Envoyé : mardi 31 mai 2016 15:27
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Developer setup model now complete
Yes, that problem would still happen, so I'll leave those instructions in the Wiki.
This ANTLR issue is quite annoying but the IP issues here seem a bit murky. I have asked in the Xtext forum but I got no replies. My question there may have been too involved, so I'll ask again a simpler question to see
if I get an answer.
Nevertheless, it looks that at least one other project (Xsemantics) does use the Itemis update site [1], so I wonder if there really is an issue with using that update site.
I have not had the time to test the setup from scratch again, but I assume that the issue I bumped into earlier regarding the download of the ANTLr component when sitting behind
a firewall with a proxy configuration which the download does not respect (I've checked the code and the code that download this additional ANTLr component assumes that you have a direction connection) and that you have to download it manyally still is valid.
So I guess that little section in the guide regarding the manual download needs to remain.
On 31 May 2016 at 00:55, Christian Damus <give.a.damus@xxxxxxxxx> wrote:
Hi, Team,
Thanks to some excellent work by Ernesto in wrangling the Oomph setup model to run EMF code generation and Xtext builds on several of the textual modeling and codegen related source projects, the setup model now can provision a fully compiled
and ready workspace for new developers without any compilation errors, missing source folders, or complicated extra manual steps. Even when creating a fresh new clone of the git repository!
There is an important note about a single point of user intervention in the setup process: the
org.eclipse.papyrusrt.xtumlrt.xtext project (the main Xtext project for the textual UML-RT syntax) will prompt in the Console view for download of an extra ANTLr-related
JAR that the Xtext builder wants, but which is not distributed with Xtext. For the same reasons that it isn’t distributed with Xtext, it isn’t baked into the setup model. But, you can simply hit the
Y key and
Enter in the console to proceed with the Xtext generation. Apart from that, the setup is now fully automated.
This should really help individuals in the adopter community to get started building solutions on Papyrus-RT and to encourage contributions. Thanks, Ernesto!
Christian
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
