On Sat, Jun 18, 2011 at 11:40 AM, Kris De Volder <[email protected]> wrote:
> It seems to me that neither Gradle nor the IDE is in the perfect position
> to do this right... but if Gradle and the IDE work together we may be
> able to get a nice solution.
>
> What I'm thinking is, an "ExternalDependency" as returned by the
> Gradle project model in the tooling API should have some type of
> identifying 'key' associated with it (similar to how maven etc.
> identify/resolve deps).
>
> Also a project should have this type of identifier associated with it
> (i.e. the key it uses to 'publish' to the repo).
>
>From my perspective, if you have two projects being built by Gradle,
then Gradle could keep a reference to those projects soemwhere in
.gradle.
If the second project declares a depedency such as:
compile group: "projectA", name: "core", version: "1.0.0"
Then there should be a cmd line option on gradle so that before it
tries to resolve the binary dependency from a declared repository, it
should first look for a project named "projectA:core" that has a
declared version of 1.0.0.
If Gradle has already built such a project then it should
automatically perform a build or jar or uploadArtifacts on that
project/module (checking first that the project is still on the local
HDD), then include the created binary as part of the classpath. Better
still somehow link the appropriate configurations as if it was a
larger multimodule build.
This would save having to do some conditional declaration as part of
the dependencies.
This flag could also be used in the eclipse or idea plugins to
automatically create a project with projectA:core as a module of
projectB.
-Mike
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
