[GRADLE-1837] 'compile project' dependency not working under milestone-5 snapshot Created: 15/Oct/11  Updated: 04/Jan/13  Resolved: 15/Oct/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.0-milestone-5

Type: Bug
Reporter: Chris Beams Assignee: Unassigned
Resolution: Fixed Votes: 0


 Description   

repro:

git clone git@github.com:cbeams/spring-project.git
git checkout m5-classpath-bug
./gradlew build

notice compilation errors out of the spring-project-aj subproject:

package org.springframework.project.core does not exist

switch back to milestone-3 and notice compilation/building succeds. Nothing has changed in the project dependency configurations, only the upgrade to m5-snapshot from m3. Note that I did try Crebuild and -nodaemon as well to no effect.

$ git checkout 2edd4da3238b7a1a12ae1a96a3809af2fb70c502

$ gradle --version

------------------------------------------------------------
Gradle 1.0-milestone-3-20110826001614-0700
------------------------------------------------------------

Gradle build time: Friday, August 26, 2011 12:16:14 AM PDT
Groovy: 1.7.10
Ant: Apache Ant(TM) version 1.8.2 compiled on December 20 2010
Ivy: 2.2.0
JVM: 1.6.0_26 (Apple Inc. 20.1-b02-383)
OS: Mac OS X 10.7.1 x86_64

$ gradle clean build
...
BUILD SUCCESSFUL

Total time: 8.732 secs

By the way, I was trying to upgrade to milestone-5, because it contains the signing plugin documented here: http://gradle.org/releases/1.0-milestone-4/docs/userguide/signing_plugin.html

Unfortunately, I had to find out the hard way that Luke's standalone repository for the signing plugin at https://github.com/alkemist/gradle-signing-plugin is NOT in fact up to date with what's in M5 and what's advertised at the documentation above with regard to the availability of the signPom method. Thus the upgrade in an effort to be able to follow the instructions properly.

Thanks,

C



 Comments   
Comment by Adam Murdoch [ 16/Oct/11 ]

This issue happens when the target project publishes a source or javadoc jar.

Comment by Chris Beams [ 16/Oct/11 ]

Just commenting to confirm the fix works for me. Thanks, Adam!

Generated at Wed Jun 30 12:05:42 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.