I am investigating converting our j2ee EAR build from ant to gradle. Our ear contains 4 main artifacts (a utility jar, a war and 2 ejb jars). We don't use IVY or Maven. We keep our library dependencies in a separate directory structure that has the following format:
\java-libs\<libname>\<libname-version>\<original lib dist structure> examples: \java-libs\jakarta-oro\jakarta-oro-2.0.8\<original lib dist for oro 2.0.8> \java-libs\jibx\jibx-1.1.3\<original lib dist for jibx 1.1.3> Note that the <original lib dist structure> represents the structure that library zip file contained when unzipped to its versioned directory. A quick count shows that we have 44 library distribution dependancies The issues I am encountering are: 1. Some distributions do not version name their jars and I don't like the ideas of mucking with the original distributions to rename them. (We keep the version name ourselves in the directory structure) 2. Our ant build often pulls in all dependant jars within a library distribution with a *.jar file specification It sounds like gradle MAY offer some kind of solution for issue #1 with the addArtifactPattern if it can address the full path and not just the file name of the artifact. It looks like issue #2 could be addressed with Client Modules but again, I may have library distributions that provide dependant jars that don't contain versioning within their names. This may be my problem to contend with but for me its a massive one. It means that I have to build the depandancies for all 44 distributions. Some may contain few or none, but some do contain MANY (hibernate, spring, etc) Any thoughts on how to approach my 2 issues? -- View this message in context: http://www.nabble.com/dependancy-on-legacy-library-distributions-tp21216605p21216605.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
