We are testing argouml 0.26 and 0.26.2 with andromda, but we are encountering this problem in both versions (no such problem in 0.24) : any time we drag&drop a class having a dependency from another class into a diagram, this "supplier" dependency will be copied into "client" dependencies. This breaks andromda build, since it tries to create classes out of this "inverted" dependencies. There is no trace of this "inverted" dependency on any diagram, but you can see it into the properties tab.
Snapshot before dragging and dropping the class: http://www.nabble.com/file/p20607967/beforedraganddrop.png beforedraganddrop.png Snapshot after dragging and dropping the class, please notice the new client dependency: http://www.nabble.com/file/p20607967/afterdraganddrop.png afterdraganddrop.png Here is the zargo before drag& drop : http://www.nabble.com/file/p20607967/testDependencyBeforeDragAndDrop.zargo testDependencyBeforeDragAndDrop.zargo Here is the zargo after drag&drop http://www.nabble.com/file/p20607967/testDependencyAfterDragAndDrop.zargo testDependencyAfterDragAndDrop.zargo Please let us know if you wish more details or if you want us to open a jira issue about this, Thank you in advance, best regards, Luca Dall'Olio -- View this message in context: http://www.nabble.com/argouml-0.26.2-auto-creating-dependencies-on-drag-drop---breaks-andromda-build-tp20607967p20607967.html Sent from the argouml - dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
