This issue still occurs for me. I'm deploying to weblogic but I think this still happens on other containers as well. This pull request checks to see if the resource is an instanceof a AggregratedResourceMeta which is the base class for all bundled resource. If the resource is of this class type exit out early. This fixed the issue for me, I think it will help others are well.
What I would see is when map was called with a resource of class JavaScriptBundleResourceMeta when calling getOriginalFileSystemFile(resource.sourceUrl) was made a FileNotFoundException would get thrown and the bundle would never get created.
This is related to issue #12
This issue still occurs for me. I'm deploying to weblogic but I think this still happens on other containers as well. This pull request checks to see if the resource is an instanceof a AggregratedResourceMeta which is the base class for all bundled resource. If the resource is of this class type exit out early. This fixed the issue for me, I think it will help others are well.
What I would see is when map was called with a resource of class JavaScriptBundleResourceMeta when calling getOriginalFileSystemFile(resource.sourceUrl) was made a FileNotFoundException would get thrown and the bundle would never get created.