| Did not correctly import old projects (1.8.4) into 1.9.0 [message #1783980] |
Wed, 21 March 2018 01:49  |
Eclipse User |
|
|
|
I have an issue about Import old projects into 1.9.0 RC2
If i choose: "Import -> Existing Projects into Workspace" when files put to my workspace, all of them. If i start to edit App, when changes did not save to ****.sys, bus in ".project" and in "virtualDNS.dns" new data saved. After restart IDE all changed data is lost, sys file did not edited by IDE.
How i must correctly Import old Projects?
|
|
|
|
| Re: Did not correctly import old projects (1.8.4) into 1.9.0 [message #1784161 is a reply to message #1784127] |
Fri, 23 March 2018 01:56  |
| Eclipse User |
|
|
|
I enable automatic error reporting, but this is not error, no error messages. Before I wait your answer i`m continue with experiments, and i found a solution how to correct import old projects:
1. First, you need to prepare the IDE by adding all the used in old project libraries that were in the previous version to TypeLibrary.
2. Create a new System with the same name as the old project.
3. Delete all new TypeLibrary automatically added by IDE. I use typelibrary via links to ECLIPSE_HOME, do it for project.
4. Important step! Without with step project did not saved. In System Configuration, add Device and Segment ( i`m use Ethernet ) - without this project will not be saved to the file after close IDE.
5. Close the IDE.
6. In Explorer, take the old project file *.sys and *.dns and copy them to the new project. In System Configuration early added Device and Segment (step 4) will overwrited (even the color).
7. Run the project, make a minor change to any app and make sure that the project is saved to a file *.sys. You also need to make a change in dns.
8. Happy with your new imported project.
[Updated on: Fri, 23 March 2018 01:58] by Moderator |
|
|
|
|
|
|
|
|
| Re: Did not correctly import old projects (1.8.4) into 1.9.0 [message #1784584 is a reply to message #1784580] |
Thu, 29 March 2018 11:02 |
| Eclipse User |
|
|
|
I expected that use case. I different solution for your use case would be to put your common type library into version control system (e.g., git) and clone it into your project. You can easily add git support to 4diac and then commit all the changes into this common repo. This has the further advantage that you can more easily and structured share this between the members of your team. The problem only is that you may also want to check in your projects as well and this is with the current typelib and project setup not as easy as it could be.
That brings me to my last idea from above:
If you look at the current file structure in a 4diac project it look something like this:
project
|- project.sys
|- virtualdns.xml
|- events
|- iec61311
|- ...
so in order to check in your typelib into a repo you could only do it with git submodules and by using one dedicated directory in your typelib. My Idea was to change the structure of projects as follows:
project
|- project.sys
|- virtualdns.xml
|- typelibrary
|- events
|- iec61311
|- ...
With that you could very easily put the whole typelib into a repo or link the whole typelib to a common place like you are doing it.
I'm curios what you and others think about this as potential change for the 1.10 release.
P.S.: yes this has some backward compatibility issues but I think this could be solved in some code which would check for the typelib directory and if not present create one and move all directories into this lib on project opening/import.
|
|
|
Powered by
FUDForum. Page generated in 0.05056 seconds
Home