Then we need a check on the vfs file to see if the post structure analysis options are consistent with the already created vfs files. If not, they need to be recreated with the proper options. Basically a second vfs visitor validation phase.
That doesn't help.
e.g 1st phase already starts reaper
We need some sort of simple/lightweight VFS lookup,
just need to get to the contents of META-INF.
Something conceptually similar to what we do with DeploymentUnit::getResourceClassLoader.
e.g. creating temp CL
- directories/files --> JDK's File API
- jars --> a way to read just certain bytes; META-INF/vfs.properties?
Creating a temp CL is equivalent to creating a VirtualFile that we can throw away without lingering side-effects. Why can't we reap/unreap/whatever with the VFS layers that would be holding locks/streams open and then recreate the VF? I suppose its not a huge issue to require unpacked deployments if you want to supply VFS metadata, but it would be better to avoid such a restriction.