Hi Chinthaka, On 9/18/06, Eran Chinthaka <[EMAIL PROTECTED]> wrote:
Jeremy Hughes wrote: > The trouble I see is we have a declared dependency in our pom.xml on > axiom-impl and of course that drags in the axiom-api artifact. > However, neither of these shows a dependency on woodstox. It is the > axiom-parent that depends on woodstox. I can't add axiom-parent as a > dependency to the woden pom.xml because there's nothing in the > repository corresponding to axiom-parent. Let me clarify a bit here. You can not only have a dependency on axiom-impl. You MUST drag axiom-api also in. Then you will have to add stax-api and woodstox jars well.
In fact I can build woden without a dependency on axiom-impl or woodstox but I *do* need axiom-api and stax-api. To test woden I need axiom-impl and woodstox. I'd like to split woden into modules as suggested by Jochen. My initial thoughts are: woden-api (the api we expect our users to code to) woden-dom-impl (the implementation that is coded to the DOM API) woden-axiom-impl (the implementation that is coded to the Axiom API) woden-tools (tools like ant and the WSDL converter) woden-test (the test code for all the implementations) (Note: when we get to it, a woden-common will probably be a good thing - to factor out the code that is common across woden-*-impl modules). Each of the above modules has compile and run time dependencies. In fact woden-api, and woden-*-impl don't have anything runnable so we don't need to specify runtime dependencies for them. The compile-time dependencies for woden-test shouldn't include any woden-*-impl (assume woden-test is black-box testing for now). The runtime dependencies for woden-test though will need to include an implementation of woden-api - lets say woden-axiom-impl. Because woden-axiom-impl depends on axiom-api, then we'll also need to specify an implementation of axiom-api - i.e. axiom-impl and so it goes on. Then there is the issue of white vs black box testing. IMO woden-test is the test cases for woden-api. If we need it then I'd like to consider woden-dom-impl-test to be a module for white box test cases on the dom impl. I haven't checked recently how many white box test cases we have but I have a feeling it is small - most use the API. I may just be showing my inexperience with maven2 here, so would appreciate comments from anyone who has split up code in this way before. Thanks, Jeremy
BTW, I'd like to draw your attention on http://marc.theaimsgroup.com/?l=axis-dev&m=115842187810423&w=2, while you all do this migration. -- Chinthaka
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
