Hi,
I tried to follow the instructions set here
https://wiki.eclipse.org/Papyrus-RT/Developer_Guide/DevEnv_Neon , but the link to the setup file is wrong (file don’t found) it should be
https://www.eclipse.org/papyrus-rt/content/setup/papyrus-rt-developer.setup
rather than
https://www.eclipse.org/papyrus-rt/papyrus-rt-developer.setup
Asma
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn
Envoyé : jeudi 14 avril 2016 12:29
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Developer setup instructions on the wiki
I've looked at the updated instructions, and now they are a bit more clear. Some more feedback:
1) This about download and having your own copy of the setup file does not feel like a good proposal. Sure, we will eventually get the setup file published in the global Oomph project setup catalogue,
and at that point we can remove everything related to adding the setup yourself (since it will be available automatically). But as soon as we have gotten the setup file pushed to the website repo and published on the website, I would really recommend that
the setup file is directly referenced on the website using a URL, i.e. instead of drag-and-drop of your copy of the setup file, push the green + sign and paste in the URL (in the corresponding was as the end-user instructions currently describes). Then we
can avoid issues with outdated copies of the setup file.
2) The additional step about providing user name and password(step 18) can be avoided by already entering them in the Eclipse Installer (step 14). There is actually a minor flaw in the current
setup file which misses to provide the user-id and password for the query in Bugzilla (it works for the queries towards Gerrit and Hudson). See my comment on the Gerrit change
https://git.eclipse.org/r/#/c/70605/1 regarding this.
On 13 April 2016 at 22:12, Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:
I've updated the wiki page with the suggestions.
I don't know why you would be having trouble with the ANTLR download required by Xtext. It must have been some connectivity problem with whatever server ANTLR is obtained from.
I do find it rather clunky that Xtext asks you for that. Perhaps it should be included, although I haven't checked the licence. I assume that Xtext doesn't include it in its SDK because of licence issues, which then would also likely apply
to us, but I'm not sure.
Anyway, I've added instructions on what to do if the ANTLR download fails.
I have now tested the latest version of the setup-file (patch set 11) and now it works fine. I now continued testing to only import the XtUML-RT project, and followed the manual instructions
for generating the EMF and Xtext projects.
When generating the Xtext projects, the instructions was not completely clear. Since the project already had compile errors, you had to confirm to continue with "Generate Xtext Artifacts". Then
when generating, this question about downloading the ANTLR 3 parser generator popped up. I guess this should be mentioned in the instructions. I do know that there were some discussions on
https://bugs.eclipse.org/bugs/show_bug.cgi?id=489377 whether the downloaded file should be stored in the repo or not.
I am not sure what the problem is, but for me it failed in downloading it. I get a timeout, which I guess it could be related to that I am located behind a firewall, and that the download is
disregarding any proxy settings. When trying load it using my webbrowser it works fine, so it is not related to the itemis server being down. Apparently this is also a known issue: See https://bugs.eclipse.org/bugs/show_bug.cgi?id=329683
So I guess we need to clarify this, in case anyone else also bumps into this. And provide instructions how to download it manually, i.e. download
http://download.itemis.com/antlr-generator-3.2.0-patch.jar, renami it into .antlr-generator-3.2.0-patch.jar and place it in the root of org.eclipse.papyrusrt.xtumlrt.xtext.ide. When I did, I could regenerate the Xtext artifacts...
On 13 April 2016 at 15:16, Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:
Thanks for the tip, Camille! I tried updating the setup file to ensure the the Xtend SDK was installed when importing Codegen subproject. And now the issues went away. No empty xtend-gen directories,
and no compile errors also when importing the Codegen subproject.
I guess we need to make this update to the setup file. Not sure though if the Xtend SDK always shall be installed (add it as a requirement to a P2Task for the top level Papyrus-RT project) or
if it is sufficent to add it only to the Codegen subproject. I do know that the setup file for Papyrus, only installs the Xtend SDK in cas you import the Developer subproject (it is not installed if you only import the top level Papyrus project).
On 13 April 2016 at 14:57, LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx> wrote:
Hi,
XTend provides an Eclipse/PDE builder, but you need to install the XTend SDK (IDE). There is no “manual build” for XTend (AFAIK), so installing the SDK is mandatory
It’s different for e.g. XText and Ecore Metamodels, where the usual practice is to manually
trigger the generation
Regards,
Camille
De :
papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn
Envoyé : mercredi 13 avril 2016 14:10
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Developer setup instructions on the wiki
I tried this a little bit more and bump into some issue with missing xtend-gen folders when only importing the Codegen subproject. The
instructions don't mention anything about how to generate the Java code from the .xtend files. Is that supposed to happen automatically already now (builders already in place)? Or are the builders for these not in place either and some information are missing
for how to build these manually?
On 13 April 2016 at 10:33, Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:
I looked through the instructions and have some feedback:
The initial descriptions (which looks like a copy from the end-user installation instructions), probably should be tweaked a bit, since
the formulation is taken from a completely different context and it becomes a bit confusing. For example: Remove the blue box about "Windows", since I assume that there have been no reports yet and the link points to the manual installation for end-user, not
developers. Make the instructions more to the point that you need to switch to the Advanced mode.. The list shown in the simple mode is products, not projects. Remove this about adding external setup when the list of products in advanced mode is shown (that
was only applicable for the end-user install when you add a user defined product setup file, for the developer you add the user defined project setup file).
After step 14 when showing the variables, you should probably update this based on the latest setup since a new variable where the selection
of the repo-repo or the nightly-repo for codegen/runtime-builds is made. I guess this could be explained a bit in the instructions.
I've written instructions at
but the link to the setup file is broken because we cannot upload .setup files to the wiki.
I've tried pushing the setup file to the website's git repo but I'm also getting access errors. While we get Gerrit on the website, could anyone with access to the website (perhaps
Remi or Simon) upload the setup file there? (I've attached the latest one here).
Any feedback on the instructions is welcome.
Note that the instructions include, for now, explicit instructions to generate code from the EMF models and the Xtext artifacts. I'll leave them there until we have project builders
for these.
_______________________________________________
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
_______________________________________________
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
|