Eclipse Community Forums: Papyrus » Archiving model/project versions

Home » Modeling » Papyrus » Archiving model/project versions (trying to understand what files are needed by Papyrus to complete archive a project)

Archiving model/project versions [message #1855145]

Thu, 29 September 2022 10:57

Eclipse User

what files are needed by Eclipse/Papyrus to complete archive a project?

I have been saving the 'properties', 'di', 'notation', 'ocl', and 'uml' files. Yet when I encountered an issue with a corruption of the model within Eclipse/Papyrus - I found out that these files are not the entire set that is needed. With only these files Eclipse/Papyrus still produces error messages about a 'project' file. I suspect this project data is held somewhere other than the Projects' folder location.

I haven't been able to find this described in some documentation, though it would help me fix this issue for the future

Re: Archiving model/project versions [message #1855148 is a reply to message #1855145]

Thu, 29 September 2022 14:03

Eclipse User

Eclipse features an export of a project as archive out of the box.
Why do you not use this?
/Carsten

Re: Archiving model/project versions [message #1855152 is a reply to message #1855148]

Thu, 29 September 2022 17:07

Eclipse User

when I try "Export", the only option that shows up for Papyrus is "Export All Diagrams". I've used this to export the images of the diagrams. Yet, to save the entire eclilpse/Papyrus project (the extensions above and the missing 'project' items) this "Export All Diagrams" doesn't appear to be what you're implying I should export.

I think you mean "File" "Export", using "General" "Archive File". Trying that now.

[Updated on: Thu, 29 September 2022 17:18] by Moderator

Re: Archiving model/project versions [message #1855154 is a reply to message #1855152]

Thu, 29 September 2022 18:11

Eclipse User

this appears to work on export two additional hidden files; '.project' and files under '.setttings' are added to the set above.

When importing - there's a bit of a hurdle. One has to open a project, or create a project. The subsequent import creates a new 'folder' and then deposits the archive under this new folder. Net result the open project now is in a different subdir. The prior technique I used enabled me to put the various files into revision control, although it seems I missed two key files, as it always kept the same name and directory structure. Instead of import, I simply loaded a project from the file-system.

Instead of 'import' I used the "import Project...Archive', which had nearly the same issue, as the resulting dir was [project].zip_expanded. the at least had a name similar.

seems if I had the '.project' and '.settings' in my file set that I had been saving that would have been nearly the same as the export/import. correct?

[Updated on: Thu, 29 September 2022 21:40] by Moderator

Re: Archiving model/project versions [message #1855199 is a reply to message #1855154]

Fri, 30 September 2022 14:19

Eclipse User

No to export a project, right click on the project within the project explorer and choose export.

Re: Archiving model/project versions [message #1855201 is a reply to message #1855199]

Fri, 30 September 2022 15:31

Eclipse User

Hi

When importing from GIT, project etc should be updated automatically.

When importing from an archive make sure that you do not have conflicting prior contents. There are two alternative 'import's UIs; File->Import->General->Existing Projects into Workspace and File->Import->General->Projects from Folder or Archive. I mostly use the former since IIRC the latter often gives me unwanted folders.

Make sure that "." resource are shown in the Package Explorer so that you see all important files.

Regards

Ed Willink

Re: Archiving model/project versions [message #1855205 is a reply to message #1855201]

Fri, 30 September 2022 17:15

Eclipse User

Ok, thank you for the info.

My round-trip solution now is :

Export: select the project in Project Explorer. Select File | Export. In the Export dialog select General | FileSystem. In the File System dialog, make sure that the pesky '.project' and '.setttings' files are selected. (I also selected "Overwrite existing...without warning" and "Create directory .. files). This enables me to have the individual files, and revision control.

Import: select File | Import, "Existing Project.. Workspace". Then I answer "Yes to all" on the subsequent "Overwrite existing..." and voila it works.

ps, Export seems to have a bug with the this selection, as I have to make sure the directory is empty, despite the "Overwrite" selection. As well, Delete project even if I check "Permanently..." leave the project undeleted on the file-system, which issue why the subsequent import needs the "yes to all"... I'll file bugs.

:) I look and see if this magic is in the user-guide

Previous Topic:	Possible bug on css theme
Next Topic:	adding operations to a Class

Goto Forum:

-=] Back to Top [=-

Current Time: Mon Jul 07 01:37:21 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter