For some reason, your post wasn't accepted by the mailing list. I suggest to use the new forum instead (http://forums.gradle.org).
-- Peter Niederwieser Principal Engineer, Gradleware http://gradleware.com Creator, Spock Framework http://spockframework.org Twitter: @pniederw errorken wrote > > http://www.gradle.org/multi_project_builds -> Example 310. Project lib > dependencies > > Explains that you can put a dependency on another project in a multi build > environment. > However, when I perform: gradle eclipse, I notice that a project REFERENCE > is being made and not a JAR dependency. > > So in my .classpath (eclipse) I see: <classpathentry kind="src" > path="/the-referenced-project" exported="true"/> > > What I expect is a JAR dependency. Like this; > > <classpathentry > sourcepath="/home/.gradle/caches/artifacts-7/artifacts/4711c4914672af8d621c2a26f0b97d14/........the-referenced-project.jar" > exported="true"/> > > The manual clearly states "What if one projects needs the jar produced by > another project in its compile path?" So I was expecting that the depended > project would be build first, installed in the local cache, and then a > dependency links was made to that JAR in the eclipse classpath file. > > Apprantly that is not the case. Is this a bug or am I doing something > wrong? > -- View this message in context: http://gradle.1045684.n5.nabble.com/Gradle-inter-project-dependency-via-JAR-in-eclipse-tp5095979p5096182.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
