You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/03/28 15:01:35 UTC
[jira] Moved: (MANTTASKS-41) type attribute of
artifact:dependencies doesn't work for indirect dependencies
[ http://jira.codehaus.org/browse/MANTTASKS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl moved MNG-1542 to MANTTASKS-41:
---------------------------------------------
Complexity: (was: Intermediate)
Key: MANTTASKS-41 (was: MNG-1542)
Project: Maven 2.x Ant Tasks (was: Maven 2)
Workflow: jira (was: Maven New)
> type attribute of artifact:dependencies doesn't work for indirect dependencies
> ------------------------------------------------------------------------------
>
> Key: MANTTASKS-41
> URL: http://jira.codehaus.org/browse/MANTTASKS-41
> Project: Maven 2.x Ant Tasks
> Issue Type: Sub-task
> Components: Ant tasks
> Affects Versions: 2.0
> Reporter: Tomislav Bodor
> Fix For: 2.1.x
>
> Attachments: build.xml, pom.xml
>
>
> It appears that the type filter doesn't work properly with indirect dependencies. It doesn't look like an issue with the TypeArtifactFilter itself, but somewhere deeper. However, it's related to this feature, so here it is...
> The problem manifests with transitive dependencies that are of different type, e.g. a war artefact depends on a jar library. Whatever the type in that case (jar or war), the dependency list returned by artifact:dependencies is empty.
> I've traced through it and here is some more information:
> DefaultArtifactCollector applies the filter using ResolutionNode.filterTrail. This iterates over the (dependency) node trail and applies the specified filter to each dependency in turn. If all dependencies are of the same type and the type matches the one specified in the filter, no problems. However, I've got a dependency that is a war archive and that in turn has some jar dependencies. If type is set to jar, filter fails when testing the first dependency in the trail - the war in this case and never gets to the jar. The result is that whatever the value of the type attribute, the dependency list always ends up empty for trails that contain dependencies of different types.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Moved: (MANTTASKS-41) type attribute of artifact:dependencies doesn't work for indirect dependencies
Posted by Jason van Zyl <ja...@maven.org>.
On 28 Mar 07, at 9:11 AM 28 Mar 07, Brett Porter wrote:
> Jason,
>
> Can you set up the released versions for these before moving more
> issues so that affects versions, etc are retained?
I think most of those are so unmaintained it doesn't matter. I'll be
going through them, as they are only 40, and sort/categorize them.
No one has looked at them in ages and I doubt anything matches anyway.
Jason.
> I only see 1.0-alpha-1 in there at the moment, and it doesn't make
> much sense to go backwards.
>
> I've adjusted the project configuration to be standard maven style
> (workflow, creation screen).
>
> We should also move the old issues out of MNG so they remain
> together and remove the component.
>
> Let me know if I can help with any of these.
>
> Cheers,
> Brett
>
> On 28/03/2007, at 11:01 PM, Jason van Zyl (JIRA) wrote:
>
>>
>> [ http://jira.codehaus.org/browse/MANTTASKS-41?
>> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Jason van Zyl moved MNG-1542 to MANTTASKS-41:
>> ---------------------------------------------
>>
>> Complexity: (was: Intermediate)
>> Key: MANTTASKS-41 (was: MNG-1542)
>> Project: Maven 2.x Ant Tasks (was: Maven 2)
>> Workflow: jira (was: Maven New)
>>
>>> type attribute of artifact:dependencies doesn't work for indirect
>>> dependencies
>>> --------------------------------------------------------------------
>>> ----------
>>>
>>> Key: MANTTASKS-41
>>> URL: http://jira.codehaus.org/browse/MANTTASKS-41
>>> Project: Maven 2.x Ant Tasks
>>> Issue Type: Sub-task
>>> Components: Ant tasks
>>> Affects Versions: 2.0
>>> Reporter: Tomislav Bodor
>>> Fix For: 2.1.x
>>>
>>> Attachments: build.xml, pom.xml
>>>
>>>
>>> It appears that the type filter doesn't work properly with
>>> indirect dependencies. It doesn't look like an issue with the
>>> TypeArtifactFilter itself, but somewhere deeper. However, it's
>>> related to this feature, so here it is...
>>> The problem manifests with transitive dependencies that are of
>>> different type, e.g. a war artefact depends on a jar library.
>>> Whatever the type in that case (jar or war), the dependency list
>>> returned by artifact:dependencies is empty.
>>> I've traced through it and here is some more information:
>>> DefaultArtifactCollector applies the filter using
>>> ResolutionNode.filterTrail. This iterates over the (dependency)
>>> node trail and applies the specified filter to each dependency in
>>> turn. If all dependencies are of the same type and the type
>>> matches the one specified in the filter, no problems. However,
>>> I've got a dependency that is a war archive and that in turn has
>>> some jar dependencies. If type is set to jar, filter fails when
>>> testing the first dependency in the trail - the war in this case
>>> and never gets to the jar. The result is that whatever the value
>>> of the type attribute, the dependency list always ends up empty
>>> for trails that contain dependencies of different types.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the
>> administrators: http://jira.codehaus.org/secure/Administrators.jspa
>> -
>> For more information on JIRA, see: http://www.atlassian.com/
>> software/jira
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [jira] Moved: (MANTTASKS-41) type attribute of artifact:dependencies doesn't work for indirect dependencies
Posted by Brett Porter <br...@apache.org>.
Jason,
Can you set up the released versions for these before moving more
issues so that affects versions, etc are retained? I only see 1.0-
alpha-1 in there at the moment, and it doesn't make much sense to go
backwards.
I've adjusted the project configuration to be standard maven style
(workflow, creation screen).
We should also move the old issues out of MNG so they remain together
and remove the component.
Let me know if I can help with any of these.
Cheers,
Brett
On 28/03/2007, at 11:01 PM, Jason van Zyl (JIRA) wrote:
>
> [ http://jira.codehaus.org/browse/MANTTASKS-41?
> page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jason van Zyl moved MNG-1542 to MANTTASKS-41:
> ---------------------------------------------
>
> Complexity: (was: Intermediate)
> Key: MANTTASKS-41 (was: MNG-1542)
> Project: Maven 2.x Ant Tasks (was: Maven 2)
> Workflow: jira (was: Maven New)
>
>> type attribute of artifact:dependencies doesn't work for indirect
>> dependencies
>> ---------------------------------------------------------------------
>> ---------
>>
>> Key: MANTTASKS-41
>> URL: http://jira.codehaus.org/browse/MANTTASKS-41
>> Project: Maven 2.x Ant Tasks
>> Issue Type: Sub-task
>> Components: Ant tasks
>> Affects Versions: 2.0
>> Reporter: Tomislav Bodor
>> Fix For: 2.1.x
>>
>> Attachments: build.xml, pom.xml
>>
>>
>> It appears that the type filter doesn't work properly with
>> indirect dependencies. It doesn't look like an issue with the
>> TypeArtifactFilter itself, but somewhere deeper. However, it's
>> related to this feature, so here it is...
>> The problem manifests with transitive dependencies that are of
>> different type, e.g. a war artefact depends on a jar library.
>> Whatever the type in that case (jar or war), the dependency list
>> returned by artifact:dependencies is empty.
>> I've traced through it and here is some more information:
>> DefaultArtifactCollector applies the filter using
>> ResolutionNode.filterTrail. This iterates over the (dependency)
>> node trail and applies the specified filter to each dependency in
>> turn. If all dependencies are of the same type and the type
>> matches the one specified in the filter, no problems. However,
>> I've got a dependency that is a war archive and that in turn has
>> some jar dependencies. If type is set to jar, filter fails when
>> testing the first dependency in the trail - the war in this case
>> and never gets to the jar. The result is that whatever the value
>> of the type attribute, the dependency list always ends up empty
>> for trails that contain dependencies of different types.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
> administrators: http://jira.codehaus.org/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/
> software/jira
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org