Hey there. Thanks for this detailed problem report, and especially
for the manifest that reproduces the problem. I will make sure we
generate a test case for this tomorrow so that we don't lose track of
it.
I can't promise a specific timeframe for fixing it, but that test will
make sure that doe
I forgot to mention, the other annoying issue is that the error
message points to the file and line number of the parameterized class
declaration, NOT the require statement. Enabling verbose/debug output
doesn't help in finding the offending require statement. I basically
had to figure out for my
