[
https://issues.apache.org/jira/browse/NPANDAY-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108711#comment-14108711
]
Brett Porter commented on NPANDAY-598:
--------------------------------------
Hi [~lcorneliussen], basically what happened here was that the fix you'd
applied got lost when I refactored. I noticed that, and reinstated it, and
should now be working as before.
However, I noted that this might not be the optimal solution in the long run -
the scope is based on where it is instantiated rather than where it is used.
Also, they are named as "caches", but they seem to be behaving as a way to
collect information during a resolution run, that can be accessed after the
resolution run, but are not to be used by subsequent resolution runs (hence the
problem when retained where they accumulated information from previous
resolutions).
I don't think there is anything actionable here now - just wanted to add some
information in case it's helpful for future reference.
This is completely separate to NPANDAY-599, where we've also been discussing
caching (which actually are keyed resolution caches for other scenarios), which
I confusingly referenced this change before I understood what was happening
there.
> Problem: resolving PDBs in a reactor module makes them a dependency for
> subsequent modules
> ------------------------------------------------------------------------------------------
>
> Key: NPANDAY-598
> URL: https://issues.apache.org/jira/browse/NPANDAY-598
> Project: NPanday
> Issue Type: Sub-task
> Components: Maven Plugins
> Reporter: Lars Corneliussen
> Fix For: 1.5.0-incubating
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
