Thanks, Peter, > Can you make it so that the Jars will be uploaded separately? This would simplify your task.
Well, uploading all JARs into our repository is inconvenient. The WAR in question is a open-source library, and the WAR file is quite large (some 60 MB), and contains many tens of JARs. We're mostly reusing the code, just replacing the main servlet with our customized version. I wanted to be able, once a new version of that library is released, to replace that WAR only - the build and the customized code should continue working. And, of course, it's not only about JARs, but also about other resources in that WAR. I would prefer to find a more scriptable/dynamic solution. > It seems that the Jars extracted from the War are regular compile > dependencies. Hence you should add them to the "compile" configuration. Then > you won't have to fiddle with the compileJava, eclipseClasspath, and > ideaModule tasks. Those JARs are indeed regular compile dependencies. I'd be happy to add them to the compile configuration, but it seems to be read-only and only configurable using DSL statements which are static (or look so). How is it possible to add some arbitrary JAR to the compile configuration from a task? Regards, Andrew
