I wonder how such a setup would play out in regards to Open Source usage. Say you create a big jar with all dependencies in there in several layers of "lib" fo

I wonder how such a setup would play out in regards to Open Source usage. Say you create a big jar with all dependencies in there in several layers of "lib" folders. Licenses like LGPL say you have to keep the LGPL archive accessible to the user and grant permission for them to alter/update them. Would a nested hierarchy of lib folders inside your jar be viewed as hindrance? Certainly you didn't "hide" the LGPL'd components in order for the user to not alter them but I think it could be viewed as "security through obscurity". If I don't immediately see a component, how do I know its there? I guess this could be solved by a readme that lists in detail what open source components are used and where in the hierarchy they can be found.