jira-importer commented on issue #232: URL: https://github.com/apache/maven-war-plugin/issues/232#issuecomment-2967854496
**[Brian E. Fox (imported)](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=bri...@infinity.nu)** commented There are additional problems with the way the overlaying is done. Example: War A is a template project. Lets say I have foo.html that is a default file. War B depends on War A but I want to override foo.html. War C depends on War B but I want to yet again override foo.html Because the war of the current project is assembled and then the overlays copied on top, the plugin needs logic to not overwrite files that already exist in the target folder. Then if we layer it such that C is built first and then B is overlaid and A last and we never overwrite a file that exists, we end up with what we intended. However, lets say we are in snapshot mode and developer working on B needs to see the results of his efforts in C. Because we've said that we can never overwrite the files that exist to get proper layering, this means that any files in B won't be recopied again to the target because they already exist. It means they need to do a clean build everytime. I had built a overlaying model before war support that worked opposite. I expand each dependent war into the target folder BEFORE the current project's war gets assembled. So in my example above, I expand A, then B overwriting all of A and then C get's assembled on top getting the last word. By always overwriting the files each time, if B changed, those files immediately take effect without a clean build. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
