On Sat, May 26, 2012 at 1:31 PM, Dawid Weiss <[email protected]> wrote:
> Ideally, this should be configurable via plugins because there is
> simply no way to predict what people may come up with?
As far as I can see, a very simple change to shade allows a/b/c to
match /a/b/c, and I have yet to think of a problem with it.
That log message, however, is nuts. Searching in classpath and then
logging that file path? I'd file that as a bug in Velocity.
>
> The relevant fragment from velocity is not even consistent -- look:
>
> inputStream =
> getClass().getResourceAsStream("/org/apache/velocity/runtime/defaults/velocity.properties");
> configuration.load(inputStream);
> if(log.isDebugEnabled())
> log.debug("Default Properties File: " + (new
> File("org/apache/velocity/runtime/defaults/velocity.properties")).getPath());
>
> So they use the '/' leading form to lookup the resource but they
> report something else (and a file!, not a resource).
>
> Dawid
>
> On Sat, May 26, 2012 at 10:00 PM, Benson Margulies
> <[email protected]> wrote:
>> The problem here is that we need to relocate /a/b/c to /q/r/s.
>> However, since relocations are stated in terms of a.b.c form and not
>> path form, there's no syntax that maps.
>>
>> Unless, of course, a pattern of a.b.c -> q.r.s should just work for
>> getClass().getResource("/a/b/c");
>>
>> It seems reasonable to me, but perhaps I'm missing something? Any
>> thoughts from deep-shade thinkers would be helpful here.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
