@Walter
I tried your WSProjectPlugin with no success.
After building it and putting the generated jar into my root project "libs"
folder I made it available through
So far so good. The problem is how to use it. Provided that I have a
multi-project structure like the following
I tried configuring deps on root project as
but it seems they never contributes as compilation dependencies. While if I
use the gradle way (such as /compile project (':sublib1') /) it works,
(provided that I include /sublib1/ from /settings.gradle/.
Any idea?
Having developed such plugins, you could also be interested in
http://issues.gradle.org/browse/GRADLE-1014
PS: the svn organization of your project vitiates the default checkout
instructions provided at
http://code.google.com/p/gradle-wdc-plugins/source/checkout
Cheers
Davide
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Is-it-possible-to-elect-a-local-gradle-project-to-satisfy-other-projects-deps-tp4497854p4758878.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
