[
https://issues.apache.org/jira/browse/NPANDAY-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105249#comment-14105249
]
Brett Porter commented on NPANDAY-599:
--------------------------------------
thanks, I forgot to update the ticket.
Yes, I think rather than trying to modify the lookups, it's better to have a
single cache, but key it based on the project ID.
> Cache resolve-result reactor-wide to avoid pdb/gac/++ beeing resolved
> multiple times
> ------------------------------------------------------------------------------------
>
> Key: NPANDAY-599
> URL: https://issues.apache.org/jira/browse/NPANDAY-599
> Project: NPanday
> Issue Type: Sub-task
> Components: Maven Plugins
> Reporter: Lars Corneliussen
> Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> Currently it seems like our custom contributors/resolvers execute for every
> possible path (artifact.getDependencyTrail() changes...).
> We can cache what we resolved reactor-wide in a separate component.
> Cachekey would be artifact.getId(), right?
> Should we let each contributor implement the cache
> (ArtifactResolvingContributor) - or should it be generically handled in the
> artifact resolver?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
