All, I am having an issue that has been encountered before. The issue concerns the inclusion of a file called spring.handlers that exists in multiple spring jars that are included with a project. I'm building a release version of a jar that includes its dependencies, such that there needs to exist in the META-INF folder of the generated release jar a spring.handlers containing a combination of all the spring.handlers encountered in all the dependency jars collected and included.
The maven-shade-plugin has been offered as a solution for this situation, but I am finding that the shade plugin is causing my compile to take too long, and it creates many warning messages. Putting aside that I need to fine-tune my dependencies, and that the shade plugin is not all to blame for the inefficiency of my build, I need another solution to get me by--something that does not involve manual intervention on my part every time I build. What I would like to do is have maven ignore all spring.handlers entries, and have the build substitute my own manually collected spring.handlers at the end. Is there an easy way to do this? It looks like I could use the DontIncludeResourceTransformer (if this also does not add too much time to my build), and then include mine at the end, but I'm not sure if the DontIncludeResourceTransformer would prevent me from doing so. I'm open to writing my own plugins, but I haven't done this yet, and I'm wondering how difficult this would be. Thanks for any suggestions you can offer, Scott -- View this message in context: http://maven.40175.n5.nabble.com/spring-handlers-tp5048978p5048978.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
