On Thu, Apr 14, 2011 at 4:11 AM, Bob Tarling <[email protected]> wrote: > Linus said: >> There seems to be a new dependency between the >> argouml-core-diagrams-activity2 module and the argouml-core-notation module. >> Looking at this from above it is obvious that we should not have such >> dependencies > > How can the activity diagram not rely on notations to generate the > text they display? They have done so for a long time.
I can't tell from Linus' description which way the dependency points and why it's a problem, but I would have thought that the only real issue is with cycles in the dependency graph. The whole notion of 'core,' 'non-core,' 'more-core-than-core' seems to me to be bound to break down sooner or later. The dependency graph should be considered independent of granularity or "layers." As far as managing build dependencies go, most of the alternatives are discussed in this StackOverflow question http://stackoverflow.com/questions/27818/how-can-i-manage-osgi-build-dependencies ArgoEclipse currently uses the Eclipse PDE headless build which is, honestly, kind of a pain to set up, but it does avoid the issue of having to replicate dependency information since it just uses the existing dependencies documented in the plugin manifests. In the future, we'll probably look at migrating to the Buckminster build environment. Tom ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2719915 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
