> > Just two clarifications for our readers. By 'parent' and 'child' here, > we are not talking about the POM <parent> mechanism. Our 'parent' here > is someone who is depending on a 'child'. > > No, the child p1 can neither see it's parent p2 or it's sibling p3. p3 > might be able to see p1 if it depends on it, and p2 would be able to > see all three. > > Or in other words - a POM can only see it's direct dependencies, and > their transient dependencies, but can't see those that depend upon him > (that would form a loop). > > > Now that's not totally true, we added some kind of loop-support to > Raven, but you would have trouble building it as Maven does not like > such loops. > :-) Well, I was trying to understand the story that, workbench loaded 0.6 interface, plug-in loaded a class that implements 0.7-SNAPSHOT interface. What is the mechanism that Raven knows it should be an error. You may not want to answer since it is too complicated and I do not have to know :-) Anyway what I learned is that, I should keep the Maven dependency coherent with the workbench that my plug-in will talk to. -- Raven does the right job to remind me not to make mistake!!
Thanks, Wei ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/taverna-mailing-lists/ Developers Guide: http://www.mygrid.org.uk/tools/developer-information
