> On 11 Jul 2016, at 18:58, Jim Laskey (Oracle) <james.las...@oracle.com> wrote: > >> How about the following helper method on ModulePool: >> >> Optional<LinkModule> findModule(ModuleEntry me); >> >> then the intent in code might be a littler clearer on the context. > > After thinking about this at bit: If we did that and then later worked out a > way to optimize across modules, we’d have to hunt down those cases. What > if I were to rename the method to findEntryInContext(String path, ModuleEntry > context)? >
Although widening the context later on might have unintended effects on some plugins if they depend on that method. Hmm… perhaps the right thing to do, API-wise, at the moment is not do anything? Paul.