On 24/02/10 8:36 AM, Colin Yates wrote:
Hi all, I have a number of different projects with some common libraries (who hasn't ;)). I am evolving away from the multi-project build (which is working very well actually) simply because we want to enforce versioning between these projects. Assume I have the following: - libA - libB - projectAWar - projectAUtility Note: that the dependencies go upwards so projectAUtility depends on projectAWar (or rather the JAR from projectAWar) depends on libB depends on libA. To repeat, projectAWar does *not* depend on projectAUtility. Given that each of these are defined as separate projects I have to define the dependencies just like any external library right? If that is true then I assume I must publish each dependant module into a maven repository. I have this working (copied from the documentation), but there are a few questions:
Do you need to use a maven repository? Gradle 0.8 had some bugs that mean you cannot attach a source or javadoc artifact to a project (they've since been fixed). You could use an ivy repository, instead.
-- Adam Murdoch Gradle Developer http://www.gradle.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
