Eclipse Community Forums: Papyrus » Compile the papyrus source code

Home » Modeling » Papyrus » Compile the papyrus source code(Based on papyrus source development, want to compile papyrus source code)

Compile the papyrus source code [message #1858562]

Fri, 07 April 2023 05:22

Eclipse User

Hello, everyone!
Recently, I wanted to do a project based on the papyrus source code, but after downloading the source code, I found that it could not compile properly. After importing eclipse, after downloading the related dependencies, it still could not compile properly, and there were some errors. According to the official documents, it could not be solved, and found that the official documents are outdated and inconsistent with the java version and git address required by the new version. When I imported the eclipse IDE, I had the following problems:
1.In many plugins under the plugins package, the Export-Package parameter in the MANIFEST.MF file under the META-INF will report an error. The package under the src does, and I haven't touched the source code yet;
2.In the features package, <feature id="" version=""> <plugin id=""/> prompts version modification problems in almost all feature.xml. Roughly content for "plug-in reference 'org. Eclipse. Papyrus. Example. Core. Lifecycleevents' has had changed from 1.2.0 the to2.0.0",But almost all version numbers in feature.xml are 0.0.0. I don't know if I can understand this description, actually I should post a picture, but the forum can't do it directly;
3.Found an org.eclipse.cbi.p2repo dependency missing from some java classes, but not found in the dependency library
I hope the source code developer can help me,thinks
/guojie

Attachment: 1680859278285.png
(Size: 303.70KB, Downloaded 134 times)
Attachment: 1680859193503.png
(Size: 284.30KB, Downloaded 133 times)
Attachment: 1680860011194.png
(Size: 563.82KB, Downloaded 153 times)

[Updated on: Fri, 07 April 2023 05:34] by Moderator

Re: Compile the papyrus source code [message #1858645 is a reply to message #1858562]

Thu, 13 April 2023 07:54

Eclipse User

Hi,

as the continuous build is fine, there are no issues with the source code. Since the git repository contains a consistent set of plugins with a certain version number, the feature.xml file does not duplicate this information, i.e. describes which plugins are included but not their version number.

It's typically a good idea to start with an existing binary installation of Papyrus and only import a very small subset of plugins from source code (with matching version number, i.e. corresponding git tag) instead of trying to compile "everything".

Re: Compile the papyrus source code [message #1858646 is a reply to message #1858562]

Thu, 13 April 2023 07:55

Eclipse User

Hello,

It could be quite hard to get every dependencies of Papyrus in your Eclipse to make it compile the entire source code.

Usually, to code on Papyrus we do as follow :
1. install Papyrus Nightly build in you Eclipse [1] (it will also install dependency)
2. import in you workspace only plugins you want to compile and modified
3. then to test you modification you can run a new eclipse as Eclipse Application (this will include plugins in the workspace + plugin in the installation excluding plugin in the workspace)

HTH,
Pauline

1] https://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/master/

Re: Compile the papyrus source code [message #1858694 is a reply to message #1858645]

Sun, 16 April 2023 21:17

Eclipse User

Thank you Ansgar Radermacher，
I will try as you suggest

Re: Compile the papyrus source code [message #1858695 is a reply to message #1858646]

Sun, 16 April 2023 21:21

Eclipse User

Thank you Pauline Deville，
I will try to follow the steps you gave me。

Re: Compile the papyrus source code [message #1858723 is a reply to message #1858646]

Tue, 18 April 2023 04:18

Eclipse User

Hello Pauline，
I have a new problem，As shown in Figure 1, when compiling a single plug-in, there will be an error as shown in the figure.
I want to know what the left directory is like when compiling or developing by yourself. I don't need to know the code, but just want to see the directory structure, so that I can compile and modify correctly.
really hope you can reply and help me.

Attachment: Figure1.png
(Size: 299.64KB, Downloaded 137 times)
Attachment: Figure1.png
(Size: 299.64KB, Downloaded 130 times)
Attachment: Figure1.png
(Size: 299.64KB, Downloaded 121 times)

Re: Compile the papyrus source code [message #1858743 is a reply to message #1858645]

Wed, 19 April 2023 01:58

Eclipse User

Hello Ansgar Radermacher，
I'll try to import a very small subset of plugins from source code，But it still failed to compile，As shown in Figure 1, I don't know if it's my environment.So, I'd like to ask about the environment needed to compile small subset(Hopefully the official version):
1.linux，mac or windows?
2.The version between eclipse version and papyrus version corresponds to the requirements?
3.Which version of maven uses?
In addition to the question, I would like to know the detailed steps for compiling a small subset. If this detailed step is provided,Would be greatly appreciated.

guo jie

Attachment: Figure1.png
(Size: 299.64KB, Downloaded 138 times)

Re: Compile the papyrus source code [message #1858772 is a reply to message #1858743]

Thu, 20 April 2023 08:40

Eclipse User

Guo,

can you tell us why you want to compile Papyrus?

There are two options
1. compile "everything" using maven. This can be done with any OS that supports maven (via "mvn clean verify"). I personally use mvn 3.8.5. on a Ubuntu 22 machine, but I typically prefer to let the CI job on eclipse.org do that.

2. Only use a (small) subset of plugins, as you've started to do. A typical motivation is to debug a plugin or apply changes. In this case, you do that in an Eclipse that has already a matching Papyrus version installed. Eclipse compiles the code of the imported projects without using maven at all. You should install the xtend SDK in Eclipse, as some plugins rely on generated code that is not part of the git (e.g. xtend files compile into Java code). If there are errors in a .project build-spec, they might not be relevant for you such as the oomph related one in your screenshot. Make sure that there are no errors in the MANIFEST and in the Java or xtend code.

[Updated on: Thu, 20 April 2023 08:45] by Moderator

Re: Compile the papyrus source code [message #1858778 is a reply to message #1858772]

Thu, 20 April 2023 22:33

Eclipse User

I heard that Papyrus is powerful, so I want to learn from the source code and ideas of the experts.
I will try to compile Papyrus as per your suggestion.
Thinks！

Re: Compile the papyrus source code [message #1858806 is a reply to message #1858772]

Sun, 23 April 2023 22:38

Eclipse User

hello ,
When using "mvn clean verify" to compile, there is a dependency download failure, as shown in Figure 2. When accessing the address with the dependency, a "Not Found" error occurs, as shown in Figure 3. How to solve this situation?

Attachment: Figure2.png
(Size: 19.64KB, Downloaded 129 times)
Attachment: Figure3.png
(Size: 70.88KB, Downloaded 139 times)

Re: Compile the papyrus source code [message #1858970 is a reply to message #1858806]

Wed, 03 May 2023 10:32

Eclipse User

Hi,

it's a good idea to compile "only" main Papyrus (still 487 plugins). This can be done by launching a clean verify in the subfolder "releng/main".

Re: Compile the papyrus source code [message #1859013 is a reply to message #1858970]

Fri, 05 May 2023 23:26

Eclipse User

Hello!
Yes, I tried to do so, but it still shows that the website https://download.eclipse.org/eclipse/updates/4.26-I-builds/I20221123-1800 does not have any content, so it will report an error at the step shown in the figure. Is it because the content in the repository has been deleted or updated, and the reason for the address not being updated in the code?

Attachment: Figure1.png
(Size: 28.44KB, Downloaded 121 times)

Re: Compile the papyrus source code [message #1859095 is a reply to message #1859013]

Thu, 11 May 2023 08:15

Eclipse User

Hello,
https://download.eclipse.org/eclipse/updates/4.26-I-builds/I20221123-1800 was an Eclipse integration build. It disappeared several weeks ago.
I suggest you to start a build from the tag 6.4.0. You can checkout it with this command :

git checkout -b local/6.4.0 6.4.0

and launch the following maven command at the root of the repository:

mvn clean verify -f releng/main/pom.xml

Previous Topic:	Release of Papyrus SW designer
Next Topic:	Show only set properties of stereotypes in the diagram

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 05 05:14:38 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter