tapestry-json has a special relationship to tapestry-ioc; it includes a Tapestry IOC module class providing type coercers; however it doesn't want to have a full dependency on tapestry-ioc; it's merely value-add if both are present in the classpath. Alternately, we could implement a tapestry-json-ioc module that provided the module, but that seemed wasteful.
I'll have to look at the Gradle docs to see if there's a way, parallel to what I did for IntelliJ, to make the desired Eclipse project inter-dependencies appear. On Mon, Aug 8, 2011 at 1:22 AM, Ulrich Stärk <[email protected]> wrote: > In tapestry-ioc/build.gradle we have "provided project(':tapestry-test')" and > in > tapestry-json/build.gradle we have "provided project(':tapestry-ioc')". > > When running "gradle eclipse" this leads to gradle not creating links from > tapestry-ioc to > tapestry-test and tapestry-json to tapestry-ioc and results in build errors > since both projects > require classes from the respective other project. > > Is there a reason why the type here is 'provided' and not 'compile'? > > Uli > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
