On Thu, Mar 3, 2011 at 7:50 AM, Steve Ebersole <[email protected]> wrote:
> This is in a project named 'hibernate-entitymanager'. Compiling the tests of > this project causes gralde to try and compile the main sources from the > dependent 'hibernate-core' module (even though they are already compiled), but > it tries to do so as part of 'hibernate-entitymanager' (using its configs) > which does not have all the needed deps to compile those classes. The general approach is expected (a great feature IMHO), but even if you "work on" a particular module, and made changes to its 'upstream' dependencies within the same project, Gradle will see that and re-compile it. (Countless times I have been 'confused' why my stuff doesn't work, only to realize that I was compiling the wrong submodules.) Now, since a compile is actually happening, it means that it fails to detect that compile is not required. I assume you have never compile hibernate-core, in which case there are no class files, hence hibernate-core is not up to date. You could; 1. Either try to recreate the class files by extracting them from a Jar and stick them into the output directory, or 2. Change the compile( project( "hibernate-core") ) dependency to an external dependency, in hibernate-entitymanager. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/24svnvk I relax here; http://tinyurl.com/2cgsug --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
