On Oct 28, 2009, at 12:48 PM, Steven Devijver wrote:
Hans,
Thank you! Also, it seems to me the error message is not as clear as
it could be.
I agree. This message comes from the internals of Ivy. Gradle should
do its own validation checks. Although in this case this validation
check would only apply for uploading artifacts together with an
ivy.xml/pom.xml.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
Steven
De : Hans Dockter <[email protected]>
À : [email protected]
Envoyé le : Mer 28 Octobre 2009, 12 h 38 min 22 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with
Spring build
On Oct 27, 2009, at 12:23 AM, Steven Devijver wrote:
I think I've stumbled over another problem with multiple projects
with identical group:name:version:
I plan to provide a fix for this today.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
in modules:spring-beans:java14 I prefer to depend
on :modules:spring-core:java14 instead on :modules:spring-
core. :modules:spring-core includes java 1.5 classes, I only want
to depend on java 1.4 as a matter of scrunity. However, when I add
this dependency in the modules:spring-beans:java14 project - as
below - I get the following error (see output further down below):
dependencies {
compile project(':modules:spring-core:java14')
compile ':cglib-nodep-2.1_3'
}
--Output--
C:\dev\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-beans:clean
:modules:spring-core:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clean
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: ERRORS
a module is not authorized to depend on itself:
org.springframework#java
14;2.5.6.SEC01
FAILURE: Build failed with an exception.
* What went wrong:
Could not resolve all dependencies for configuration 'compile'.
* Try:
Run with -s or -d option to get more details. Run with -S option to
get the full
(very verbose) stacktrace.
BUILD FAILED
Total time: 17.531 secs
It seems Gradle is again confused by the projects having the same
group:name:version. I've uploaded the project here:
http://drop.io/fganwg0
Steven
De : Hans Dockter <[email protected]>
À : [email protected]
Envoyé le : Lun 26 Octobre 2009, 22 h 12 min 43 s
Objet : Re: [gradle-user] Next problem with Spring build
On Oct 26, 2009, at 6:26 PM, Hans Dockter wrote:
Thanks a lot Steven for all your feedback.
On Oct 26, 2009, at 5:50 PM, Steven Devijver wrote:
Hey all,
I've encountered the next problem with the Spring build. I'm
using the latest build. For some reason which I can't identify
Gradle compiles the depended upon projects twice (build fails on
the second iteration).
Were is something compiled twice in the output below?
The modules/spring-beans/java15 project has no build.gradle for
defining any dependencies. Shouldn't there be one?
If you type gradle -n you get a hierarchical dependency report. I
have just improved the output for project dependencies in trunk
(path instead of group/name/version). That should help to figure
out this kind of problems.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
