[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-assembly] [ASSEMBLY-195] import and export of the same namespace for some testcases - PROPOSAL
Comments inline. On Mar 11, 2010, at 4:36 PM, Mike Edwards wrote:
To be precise, the claim is that the Assembly spec is unclear about what the runtime should do in this situation, not that it will lead to cyclic dependencies. After rereading the paragraph cited, I still do not think ASM12023 is clear on the appropriate behavior. As I mentioned in a previous post, consider the following: Contribution A ---(resolve {urn:foo}bar) ---> Contribution B ---(resolve {urn:foo}bar) ---> Contribution C ---(resolve {urn:foo}bar) ---> Contribution C Assuming contributions B and C both contain an artifact X in {urn:foo:bar} and Contribution B imports and exports (resolve {urn:foo}bar), the following may result: 1. References to X from artifacts in B will resolve to the version of X contained in C 2. References to X from artifacts in A will resolve to the version of X contained in B Note that this behavior is different than OSGi and there are directives in the former that can be used to avoid this from happening. At a minimum, I think this needs to be clarified in the assembly spec as users will invariably encounter this. Import/export of the same namespace is valuable in some situations but it needs specification. Another way to look at this is: what normative statement is import/export of the same namespace testing? Jim
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]