Community
Participate
Working Groups
Build ID: Eclipse 3.4 We could have multiple resources (here talking about XMIResource) with depencies between them, this means, elements from one resource might reference elements from another resource. Being this the case, the import wizard does not take into account this situation, ignoring these external references while importing the resource into a repository, leaving data inconsistent in the repository. Some of the requirements on this new import wizard are: - Check for external dependencies in a resource - Determine the dependency graph - Analyze graph: transitive dependencies, recursive dependencies, ... ? - Import a close-set of inter-dependant resources into a single repository - Scatter resources among different repos. Depends on Bug 213402 - Leave the imported resource referencing external elements. Depends on Bug 213402 A possible workflow could be: 1. User decides to import a local resource 2. The import logic detects that there are external references and offers to import automatically those into the repository. These dependant resources could be: 2.a) imported into the same repository 2.b) scattered among different repositories (Bug 213402 needs to be solved first) 2.c) references to them will be kept: Bug 213402 will allow references other than CDO repositories, in this case, an element within the CDO repository could reference an external XMIResource. 2.d) Not imported. References to elements in the former resource to import will be left empty/unset (and therefore, incosistent). The user must be warned about the inconsistent situation. - special situations must be take into account: recursive dependencies (resource "a" depends on "b", and viceversa) or transitive (a depends on b, b on c, c on .....) Looking forward for your comments on this enhacement. /Victor
Hi Vik, Good description! I guess you still intend to make an initial contribution? So I will wait for that ;-) Btw. I can't remember that we talked about multiple repositories as import targets. Don't you mean multiple resources in one repository? If you really mean multiple repositories I wouldn't start with this particular requirement. Usually Simon is really fast but anyway I'd suggest to move this requirement to a different enhancement request which then gets the "depends-on".
(In reply to comment #1) > Hi Vik, Good description! thanks Eike! > > I guess you still intend to make an initial contribution? So I will wait for > that ;-) > Yes, I hope this could be an initial contribution :D > Btw. I can't remember that we talked about multiple repositories as import > targets. Don't you mean multiple resources in one repository? Yes, we agreed that the target should be a single repository, but since 213402 will support references to other repositories, we could also give this option (is not top priorty, of course ;)). > > If you really mean multiple repositories I wouldn't start with this particular > requirement. Usually Simon is really fast but anyway I'd suggest to move this > requirement to a different enhancement request which then gets the > "depends-on". > Yes, I agree with you. First a single target repository. Lets leave multiple target repositories for the future :)
Vic did you do some works in the Editor that you could shared ? I planned to improve UI and don't want to duplicate effort!
Simon, excuse me for my delay answering here, I took one week off :) I haven't done any effort for this bug, since it was not really critical for our product. I've worked in the CDO enhanced editor generator, which is a bit abandoned right now :( , and also I did some work on a repository resource explorer, and also got to modify our editors to allow loading a resource on demand, by using "Load Resource..." action in the context menu (accessible through right click). If those are of interest for you, I could try to factor out my code and share it :)
(In reply to comment #4) > Simon, > > excuse me for my delay answering here, I took one week off :) > > I haven't done any effort for this bug, since it was not really critical for > our product. > > I've worked in the CDO enhanced editor generator, which is a bit abandoned > right now :( , and also I did some work on a repository resource explorer, and > also got to modify our editors to allow loading a resource on demand, by using > "Load Resource..." action in the context menu (accessible through right click). > If those are of interest for you, I could try to factor out my code and share > it :) > Hi Victor, Yes I would like to reuse everything you could have done. As you notice with all the news bugzilla (from the UI) I planned (already did some of them) to improve the UI. If you have any request please let me know! Simon
Re-assigning to Vik in preparation of his new committer state...
Created attachment 120239 [details] Sketch depicting the dialog for inter-dependant resource import - Ignore action should be "unset" - The title message should be something like "The resource you are about to import reference objects from other resources
Rebasing all unresolved enhancement requests to 3.0
Rebasing all outstanding enhancements requests to version 4.0
Moving all open enhancement requests to 4.1
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
Moving all outstanding enhancements to 4.3
Moving all open enhancement requests to 4.4
Moving all open bugzillas to 4.5.
Moving all unaddressed bugzillas to 4.6.
Moving all open bugs to 4.7
Moving all unresolved issues to version 4.8-
Moving all unresolved issues to version 4.9
Moving to 4.13.
