On Fri, Aug 14, 2009 at 9:16 AM, Philip Crotwell <[email protected]>wrote:
> Another case is code that is used in the build process, but not in the > runtime. Things that would be called from build.gradle, but never used > from the dist code. I am now writing some groovy code to do "helper" > stuff for the build. It is big enough that I don't want it directly in > build.gradle but it is unclear to me at this point where to put code > like that. It needs to be part of a source release, but should not > live in src/main/java or src/main/groovy. Also, if there were a > standard "place" for this type of build helper code, it could > automatically be added to the build classpath, making it much easier > to use custom code within the build process. > Have you tried the special buildSrc module? It will be built (if necessary) before the build is run and added to the classpath (as you suggest). We have found it very convenient. -- John Murph Automated Logic Research Team
