Mark Hobson wrote:
Hi Brett,
On 06/06/07, Mark Hobson [EMAIL PROTECTED] wrote:
On 06/06/07, Brett Porter [EMAIL PROTECTED] wrote:
My recollection would be that some artifacts are filtered out but
their transitive dependencies still needed to be taken into
consideration for version
Hi Brett,
On 06/06/07, Mark Hobson [EMAIL PROTECTED] wrote:
On 06/06/07, Brett Porter [EMAIL PROTECTED] wrote:
My recollection would be that some artifacts are filtered out but
their transitive dependencies still needed to be taken into
consideration for version calculations, so this could
Hi Brett,
On 06/06/07, Brett Porter [EMAIL PROTECTED] wrote:
My recollection would be that some artifacts are filtered out but
their transitive dependencies still needed to be taken into
consideration for version calculations, so this could be the reason
for this.
If an artifact is filtered
On 04/06/07, Mark Hobson [EMAIL PROTECTED] wrote:
Hi there,
Is the ArtifactFilter passed into the ArtifactCollector.collect
methods meant to be applied before calls to the ResolutionListeners?
Currently it appears to disregard the filter whilst recursing and then
apply it only when calculating
On 06/06/2007, at 8:28 AM, Mark Hobson wrote:
On 04/06/07, Mark Hobson [EMAIL PROTECTED] wrote:
Hi there,
Is the ArtifactFilter passed into the ArtifactCollector.collect
methods meant to be applied before calls to the ResolutionListeners?
Currently it appears to disregard the filter whilst
Hi there,
Is the ArtifactFilter passed into the ArtifactCollector.collect
methods meant to be applied before calls to the ResolutionListeners?
Currently it appears to disregard the filter whilst recursing and then
apply it only when calculating
ArtifactResolutionResult.artifactResolutionNodes.
