Generally you use subprojects when you want to have the recompile
cycle to include both. For example if project-web-app and project-core
are sibling subprojects, and project-web-app has a dependency of
compile project(':project-core')
then when you edit something in project-core, a 'gradle assemble" in
project-web-app will also recompile project-core. With a "download jar
from repo" dependency you don;t get the recompile.
See
http://gradle.org/0.9-preview-1/docs/userguide/tutorial_java_projects.html#sec:examples
Philip
On Wed, Apr 28, 2010 at 8:31 AM, Roger Studner <[email protected]> wrote:
> I've been using and enjoying gradle for awhile now.. amazing stuff
>
> Two things i've never done "as of yet" is both publish my artifacts, and have
> subprojects (not sure if these are "related" in gradle terminology).
>
> If I have the concepts of:
>
> product-core
> product-data
> then say, product-web-app
>
> Is this a case of product-web-app having 2 "sub-projects" (core and data)..
> or that core and data are both gadle projects that publish themselves to a
> repo, and product-web-app "depends on them"?
>
> And, if the 2nd part is true.. I'm not 100% sure I get the use of
> sub-projects in gradle.
>
> If anyone has examples of publishing artifacts and using subprojects... would
> love to get a link :) I know they passed through this mailing list a few
> months back, but I hven't had luck trackin' down good examples
>
> Thanks,
> Roger
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
