What's the problem with using compile project(':project:path')?
When it's time to publish Gradle will resolve the inter-project
dependencies into proper Maven dependencies (at least for projects that
define the group, version, archivesBaseName, and apply the maven plugin)
On Tue, Feb 11, 2014 at 8:42 AM, Daniele Segato <[email protected]>wrote:
> Hi,
>
> I've (little) experience with maven and I know you can develop a maven
> project using different modules that depends each others.
>
> Dependencies are defined using the standard dependency mechanism like if
> they are published on a maven repository but you can still use them locally
> without pushing.
>
> This very handy because it allow you to mix together different separate
> libraries that will be released as artifact but you can still refactor them
> and immediately see the effect of a modification on your code.
>
> I couldn't find a way to do this with gradle.
>
>
> I either define the dependency locally:
>
> compile project(':project:path')
>
> which use the local sources
>
> or I define the remote dependency
>
> compile 'my:project:0.1.0-SNAPSHOT'
>
> which try to download the snapshot from a maven repository.
>
>
> Trying with the second way cause these issues:
>
> - you have to uploadArchives every time you modify something to see the
> effect in the other projects that depends on this
> - you have to force a dependency update with --refresh-depencencies option
> to gradle
>
>
> is there something like the maven "install" command that deploy the
> artifact in the local maven repository?
> Can I leave the artifact-style dependency in my modules and still develop
> them locally seamlessly?
>
>
> As a plus some of my libraries has its own git repository which makes
> things more complex, if possible, but that could be solved by creating a
> "super repo" that combines them with git submodules.
>
>
> Any suggestion?
> Do anyone understood what I'm talking about?
>
> thank you and regards,
> Daniele
>
> --
> You received this message because you are subscribed to the Google Groups
> "adt-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
http://developer.android.com | http://tools.android.com
Please do not send me questions directly. Thanks!
--
You received this message because you are subscribed to the Google Groups
"adt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
