0> In article <[EMAIL PROTECTED]>, 0> Egon Willighagen <URL:mailto:[EMAIL PROTECTED]> ("Egon") wrote:
Egon> working on dh_java i encountered this: Egon> Egon> Duplicate library path: org/w3c/dom in both lib-dom-java and Egon> lib-openxml-java,libxerces-java! Egon> Egon> In other words, the org.w3c.dom classes are given in three Egon> packages... They probably have some version differences, but Egon> it seem not correct that this redundancy is available... Egon> Egon> More practical, when doing dh_java, it is not possible to Egon> determine which packages it relies on... Surely then the dependency will be on "( lib-dom-java | lib-openxml-java | libxerces-java )", since having any of those will satisfy the runtime? Though if there are version differences, you could end up having to introspect them all to find which ones will link with your package. :-( But I think the right way is to keep the interfaces package separate, and have it depend on a virtual implementation package that's provided by the actual implementations. If there are indeed different versions of the org.w3c.dom interfaces, then versioned dependencies/conflicts are probably appropriate for the implementation packages.