Next problem with Spring build

classic Classic list List threaded Threaded
18 messages Options
Reply | Threaded
Open this post in threaded view
|

Next problem with Spring build

sdevijver
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). Also, the from zipTree(jar) method does not seem to fill the Jar task (many thanks to Hans for his previous reply).

Below is the output which shows both problems. I've also uploaded the entire project here:


Thanks for your help

Steven


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
:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
C:\dev\spring-framework-2.5.6.SEC01\modules\spring-core\java14\build\libs\java14
-2.5.6.SEC01.jar: true
C:\dev\spring-framework-2.5.6.SEC01\modules\spring-core\java15\build\libs\java15
-2.5.6.SEC01.jar: true
[ant:jar] Warning: skipping jar archive C:\dev\spring-framework-2.5.6.SEC01\modu
les\spring-core\build\jar_for_module\spring-core.jar because no files were inclu
ded.
:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
:modules:spring-beans:java14:jar
:modules:spring-beans:java14:assemble
:modules:spring-beans:java14:compileTestJava
:modules:spring-beans:java14:processTestResources
:modules:spring-beans:java14:testClasses
:modules:spring-beans:java14:test
:modules:spring-beans:java14:check
:modules:spring-beans:java14:build
:modules:spring-beans:java15:compileJava
C:\dev\spring-framework-2.5.6.SEC01\tiger\src\org\springframework\beans\annotati
on\AnnotationBeanUtils.java:25: cannot find symbol
symbol  : class BeanWrapper
location: package org.springframework.beans
import org.springframework.beans.BeanWrapper;
                                ^
C:\dev\spring-framework-2.5.6.SEC01\tiger\src\org\springframework\beans\annotati
on\AnnotationBeanUtils.java:26: cannot find symbol
symbol  : class PropertyAccessorFactory
location: package org.springframework.beans
import org.springframework.beans.PropertyAccessorFactory;

[...]

C:\dev\spring-framework-2.5.6.SEC01\tiger\src\org\springframework\beans\factory\
annotation\CustomAutowireConfigurer.java:28: package org.springframework.core do
es not exist
import org.springframework.core.Ordered;
                               ^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
100 errors

FAILURE: Build failed with an exception.

* Where:
Empty build file

* What went wrong:
Execution failed for task ':modules:spring-beans:java15:compileJava'.
Cause: Compile failed; see the compiler error output for details.

* 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: 48.078 secs


Reply | Threaded
Open this post in threaded view
|

Re: Next problem with Spring build

hans_d
Administrator
<base href="x-msg://1082/">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?

Also, the from zipTree(jar) method does not seem to fill the Jar task (many thanks to Hans for his previous reply).

I will check this once we get the other stuff running.

- Hans

--
Hans Dockter
Gradle Project Manager


Below is the output which shows both problems. I've also uploaded the entire project here:


Thanks for your help

Steven


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
:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
C:\dev\spring-framework-2.5.6.SEC01\modules\spring-core\java14\build\libs\java14
-2.5.6.SEC01.jar: true
C:\dev\spring-framework-2.5.6.SEC01\modules\spring-core\java15\build\libs\java15
-2.5.6.SEC01.jar: true
[ant:jar] Warning: skipping jar archive C:\dev\spring-framework-2.5.6.SEC01\modu
les\spring-core\build\jar_for_module\spring-core.jar because no files were inclu
ded.
:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
:modules:spring-beans:java14:jar
:modules:spring-beans:java14:assemble
:modules:spring-beans:java14:compileTestJava
:modules:spring-beans:java14:processTestResources
:modules:spring-beans:java14:testClasses
:modules:spring-beans:java14:test
:modules:spring-beans:java14:check
:modules:spring-beans:java14:build
:modules:spring-beans:java15:compileJava
C:\dev\spring-framework-2.5.6.SEC01\tiger\src\org\springframework\beans\annotati
on\AnnotationBeanUtils.java:25: cannot find symbol
symbol  : class BeanWrapper
location: package org.springframework.beans
import org.springframework.beans.BeanWrapper;
                                ^
C:\dev\spring-framework-2.5.6.SEC01\tiger\src\org\springframework\beans\annotati
on\AnnotationBeanUtils.java:26: cannot find symbol
symbol  : class PropertyAccessorFactory
location: package org.springframework.beans
import org.springframework.beans.PropertyAccessorFactory;

[...]

C:\dev\spring-framework-2.5.6.SEC01\tiger\src\org\springframework\beans\factory\
annotation\CustomAutowireConfigurer.java:28: package org.springframework.core do
es not exist
import org.springframework.core.Ordered;
                               ^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
100 errors

FAILURE: Build failed with an exception.

* Where:
Empty build file

* What went wrong:
Execution failed for task ':modules:spring-beans:java15:compileJava'.
Cause: Compile failed; see the compiler error output for details.

* 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: 48.078 secs




Reply | Threaded
Open this post in threaded view
|

Re: Next problem with Spring build

hans_d
Administrator

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
Reply | Threaded
Open this post in threaded view
|

Re : [gradle-user] Next problem with Spring build

sdevijver
Hey Hans,

You're right, there's no double compilation, I must have been so surprised everything suddenly worked with the latest build that I didn't notice the spring-beans project was being built.

Regarding the [ant.jar] warning, this is a strange warning given that I've now discovered that the jar is correctly being created. I'm not sure why the warning is being printed but in any case it's not correct. from zipTree(jar) works correctly.

Thanks for your help

Steven


De : Hans Dockter <[hidden email]>
À : [hidden email]
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

Reply | Threaded
Open this post in threaded view
|

Re : [gradle-user] Next problem with Spring build

sdevijver
In reply to this post by hans_d
I think I've stumbled over another problem with multiple projects with identical group:name:version:

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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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

Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Next problem with Spring build

hans_d
Administrator
<base href="x-msg://20/">
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


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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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



Reply | Threaded
Open this post in threaded view
|

Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

sdevijver
Hans,

Thank you! Also, it seems to me the error message is not as clear as it could be.

Steven


De : Hans Dockter <[hidden email]>
À : [hidden email]
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


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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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




Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

hans_d
Administrator
<base href="x-msg://24/">
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


Steven


De : Hans Dockter <[hidden email]>
À : [hidden email]
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


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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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






Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Next problem with Spring build

hans_d
Administrator
In reply to this post by sdevijver
<base href="x-msg://150/">Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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



Reply | Threaded
Open this post in threaded view
|

Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

sdevijver
Hey Hans,

I've downloaded the latest version. All is not well, have a look at the output below. I've removed my .gradle folder to no avail. I've uploaded the project again since the version you've used might not have been representative:


Steven


---Output---


C:\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-agent:clean
:modules:spring-aop:clean
:modules:spring-beans:clean
:modules:spring-context:clean
:modules:spring-context-support:clean
:modules:spring-core:clean
:modules:spring-jdbc:clean
:modules:spring-jms:clean
:modules:spring-orm:clean
:modules:spring-tx:clean
:modules:spring-web:clean
:modules:spring-webmvc:clean
:modules:spring-webmvc-portlet:clean
:modules:spring-agent:java15:clean
:modules:spring-aop:java14:clean
:modules:spring-aop:java15:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-context-support:java14:clean
:modules:spring-context:java14:clean
:modules:spring-context:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clea n
:modules:spring-jdbc:java14:clean
:modules:spring-jdbc:java15:clean
:modules:spring-jms:java14:clean
:modules:spring-orm:java14:clean
:modules:spring-orm:java15:clean
:modules:spring-tx:java14:clean
:modules:spring-tx:java15:clean
:modules:spring-web:java14:clean
:modules:spring-web:java15:clean
:modules:spring-webmvc-portlet:java14:clean
:modules:spring-webmvc-portlet:java15:clean
:modules:spring-webmvc:java14:clean
:modules:spring-webmvc:java15:clean
:modules:spring-agent:java15:compileJava
:modules:spring-agent:java15:processResources
:modules:spring-agent:java15:classes
:modules:spring-agent:java15:jar
:modules:spring-agent:java15:assemble
:modules:spring-agent:java15:compileTestJava SKIPPED
:modules:spring-agent:java15:processTestResources SKIPPED
:modules:spring-agent:java15:testClasses SKIPPED
:modules:spring-agent:java15:test SKIPPED
:modules:spring-agent:java15:check
:modules:spring-agent:java15:build
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java15\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java15\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

[ant:jar] Warning: skipping jar archive C:\spring-framework-2.5.6.SEC01\modules\
spring-core\build\jar_for_module\spring-core.jar because no files were included.

:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core\ivydata-2.5.6.SEC01.proper
ties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:spring-c
ore\ivydata-2.5.6.SEC01.properties (The filename, directory name, or volume labe
l syntax is incorrect)

:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
Terminate batch job (Y/N)? y

C:\spring-framework-2.5.6.SEC01>





De : Hans Dockter <[hidden email]>
À : [hidden email]
Envoyé le : Jeu 29 Octobre 2009, 10 h 07 min 23 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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




Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

hans_d
Administrator
Hi Steven,

we have some issues with our incremental build in trunk. Try to rebuild with: -C rebuild
Some of the cache state is in <userGradleHome>.

- Hans

On Oct 29, 2009, at 13:26, Steven Devijver <[hidden email]> wrote:

Hey Hans,

I've downloaded the latest version. All is not well, have a look at the output below. I've removed my .gradle folder to no avail. I've uploaded the project again since the version you've used might not have been representative:


Steven


---Output---


C:\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-agent:clean
:modules:spring-aop:clean
:modules:spring-beans:clean
:modules:spring-context:clean
:modules:spring-context-support:clean
:modules:spring-core:clean
:modules:spring-jdbc:clean
:modules:spring-jms:clean
:modules:spring-orm:clean
:modules:spring-tx:clean
:modules:spring-web:clean
:modules:spring-webmvc:clean
:modules:spring-webmvc-portlet:clean
:modules:spring-agent:java15:clean
:modules:spring-aop:java14:clean
:modules:spring-aop:java15:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-context-support:java14:clean
:modules:spring-context:java14:clean
:modules:spring-context:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clea n
:modules:spring-jdbc:java14:clean
:modules:spring-jdbc:java15:clean
:modules:spring-jms:java14:clean
:modules:spring-orm:java14:clean
:modules:spring-orm:java15:clean
:modules:spring-tx:java14:clean
:modules:spring-tx:java15:clean
:modules:spring-web:java14:clean
:modules:spring-web:java15:clean
:modules:spring-webmvc-portlet:java14:clean
:modules:spring-webmvc-portlet:java15:clean
:modules:spring-webmvc:java14:clean
:modules:spring-webmvc:java15:clean
:modules:spring-agent:java15:compileJava
:modules:spring-agent:java15:processResources
:modules:spring-agent:java15:classes
:modules:spring-agent:java15:jar
:modules:spring-agent:java15:assemble
:modules:spring-agent:java15:compileTestJava SKIPPED
:modules:spring-agent:java15:processTestResources SKIPPED
:modules:spring-agent:java15:testClasses SKIPPED
:modules:spring-agent:java15:test SKIPPED
:modules:spring-agent:java15:check
:modules:spring-agent:java15:build
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java15\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java15\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

[ant:jar] Warning: skipping jar archive C:\spring-framework-2.5.6.SEC01\modules\
spring-core\build\jar_for_module\spring-core.jar because no files were included.

:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core\ivydata-2.5.6.SEC01.proper
ties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:spring-c
ore\ivydata-2.5.6.SEC01.properties (The filename, directory name, or volume labe
l syntax is incorrect)

:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
Terminate batch job (Y/N)? y

C:\spring-framework-2.5.6.SEC01>





De : Hans Dockter <[hidden email]>
À : [hidden email]
Envoyé le : Jeu 29 Octobre 2009, 10 h 07 min 23 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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




Reply | Threaded
Open this post in threaded view
|

Re : [gradle-user] Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

sdevijver
Hans,

On closer inspection I think the issue is related to the naming of directories in the cache folder. ":modules:spring-core" is not a valid folder name on windows because of the colons.

Steven


De : Hans Dockter <[hidden email]>
À : "[hidden email]" <[hidden email]>
Envoyé le : Jeu 29 Octobre 2009, 16 h 37 min 21 s
Objet : Re: [gradle-user] Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

we have some issues with our incremental build in trunk. Try to rebuild with: -C rebuild
Some of the cache state is in <userGradleHome>.

- Hans

On Oct 29, 2009, at 13:26, Steven Devijver <[hidden email]> wrote:

Hey Hans,

I've downloaded the latest version. All is not well, have a look at the output below. I've removed my .gradle folder to no avail. I've uploaded the project again since the version you've used might not have been representative:


Steven


---Output---


C:\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-agent:clean
:modules:spring-aop:clean
:modules:spring-beans:clean
:modules:spring-context:clean
:modules:spring-context-support:clean
:modules:spring-core:clean
:modules:spring-jdbc:clean
:modules:spring-jms:clean
:modules:spring-orm:clean
:modules:spring-tx:clean
:modules:spring-web:clean
:modules:spring-webmvc:clean
:modules:spring-webmvc-portlet:clean
:modules:spring-agent:java15:clean
:modules:spring-aop:java14:clean
:modules:spring-aop:java15:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-context-support:java14:clean
:modules:spring-context:java14:clean
:modules:spring-context:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clea n
:modules:spring-jdbc:java14:clean
:modules:spring-jdbc:java15:clean
:modules:spring-jms:java14:clean
:modules:spring-orm:java14:clean
:modules:spring-orm:java15:clean
:modules:spring-tx:java14:clean
:modules:spring-tx:java15:clean
:modules:spring-web:java14:clean
:modules:spring-web:java15:clean
:modules:spring-webmvc-portlet:java14:clean
:modules:spring-webmvc-portlet:java15:clean
:modules:spring-webmvc:java14:clean
:modules:spring-webmvc:java15:clean
:modules:spring-agent:java15:compileJava
:modules:spring-agent:java15:processResources
:modules:spring-agent:java15:classes
:modules:spring-agent:java15:jar
:modules:spring-agent:java15:assemble
:modules:spring-agent:java15:compileTestJava SKIPPED
:modules:spring-agent:java15:processTestResources SKIPPED
:modules:spring-agent:java15:testClasses SKIPPED
:modules:spring-agent:java15:test SKIPPED
:modules:spring-agent:java15:check
:modules:spring-agent:java15:build
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java15\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java15\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

[ant:jar] Warning: skipping jar archive C:\spring-framework-2.5.6.SEC01\modules\
spring-core\build\jar_for_module\spring-core.jar because no files were included.

:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core\ivydata-2.5.6.SEC01.proper
ties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:spring-c
ore\ivydata-2.5.6.SEC01.properties (The filename, directory name, or volume labe
l syntax is incorrect)

:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
Terminate batch job (Y/N)? y

C:\spring-framework-2.5.6.SEC01>





De : Hans Dockter <[hidden email]>
À : [hidden email][hidden email]
Envoyé le : Jeu 29 Octobre 2009, 10 h 07 min 23 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email][hidden email]>
À : [hidden email][hidden email]
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





Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

Adam Murdoch-2
In reply to this post by hans_d


Hans Dockter wrote:
Hi Steven,

we have some issues with our incremental build in trunk. Try to rebuild with: -C rebuild
Some of the cache state is in <userGradleHome>.

I don't think it's the incremental build stuff. Those are ivy warnings in the output, and the path it's trying to write to looks like the internal repository has come back for some reason.


- Hans

On Oct 29, 2009, at 13:26, Steven Devijver <[hidden email]> wrote:

Hey Hans,

I've downloaded the latest version. All is not well, have a look at the output below. I've removed my .gradle folder to no avail. I've uploaded the project again since the version you've used might not have been representative:


Steven


---Output---


C:\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-agent:clean
:modules:spring-aop:clean
:modules:spring-beans:clean
:modules:spring-context:clean
:modules:spring-context-support:clean
:modules:spring-core:clean
:modules:spring-jdbc:clean
:modules:spring-jms:clean
:modules:spring-orm:clean
:modules:spring-tx:clean
:modules:spring-web:clean
:modules:spring-webmvc:clean
:modules:spring-webmvc-portlet:clean
:modules:spring-agent:java15:clean
:modules:spring-aop:java14:clean
:modules:spring-aop:java15:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-context-support:java14:clean
:modules:spring-context:java14:clean
:modules:spring-context:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clea n
:modules:spring-jdbc:java14:clean
:modules:spring-jdbc:java15:clean
:modules:spring-jms:java14:clean
:modules:spring-orm:java14:clean
:modules:spring-orm:java15:clean
:modules:spring-tx:java14:clean
:modules:spring-tx:java15:clean
:modules:spring-web:java14:clean
:modules:spring-web:java15:clean
:modules:spring-webmvc-portlet:java14:clean
:modules:spring-webmvc-portlet:java15:clean
:modules:spring-webmvc:java14:clean
:modules:spring-webmvc:java15:clean
:modules:spring-agent:java15:compileJava
:modules:spring-agent:java15:processResources
:modules:spring-agent:java15:classes
:modules:spring-agent:java15:jar
:modules:spring-agent:java15:assemble
:modules:spring-agent:java15:compileTestJava SKIPPED
:modules:spring-agent:java15:processTestResources SKIPPED
:modules:spring-agent:java15:testClasses SKIPPED
:modules:spring-agent:java15:test SKIPPED
:modules:spring-agent:java15:check
:modules:spring-agent:java15:build
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java15\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java15\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

[ant:jar] Warning: skipping jar archive C:\spring-framework-2.5.6.SEC01\modules\
spring-core\build\jar_for_module\spring-core.jar because no files were included.

:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core\ivydata-2.5.6.SEC01.proper
ties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:spring-c
ore\ivydata-2.5.6.SEC01.properties (The filename, directory name, or volume labe
l syntax is incorrect)

:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
Terminate batch job (Y/N)? y

C:\spring-framework-2.5.6.SEC01>





De : Hans Dockter <[hidden email]>
À : [hidden email]
Envoyé le : Jeu 29 Octobre 2009, 10 h 07 min 23 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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





-- 
Adam Murdoch
Gradle Developer
http://www.gradle.org
Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

hans_d
Administrator

On Oct 29, 2009, at 8:35 PM, Adam Murdoch wrote:



Hans Dockter wrote:
Hi Steven,

we have some issues with our incremental build in trunk. Try to rebuild with: -C rebuild
Some of the cache state is in <userGradleHome>.

I don't think it's the incremental build stuff.

Sorry. I shouldn't answer this kind of email from my mobile phone without reading the stacktrace properly.

Those are ivy warnings in the output, and the path it's trying to write to looks like the internal repository has come back for some reason.

In this form it was always there. Ivy is always writing the deployment descriptors into the cache. The problem is that I have changed the name of the project dependency to its path when resolving. Therefore we have this issue. I will transform colons into underscores for the name and everything should work fine then on windows.

- Hans

--
Hans Dockter
Gradle Project Manager



- Hans

On Oct 29, 2009, at 13:26, Steven Devijver <[hidden email]> wrote:

Hey Hans,

I've downloaded the latest version. All is not well, have a look at the output below. I've removed my .gradle folder to no avail. I've uploaded the project again since the version you've used might not have been representative:


Steven


---Output---


C:\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-agent:clean
:modules:spring-aop:clean
:modules:spring-beans:clean
:modules:spring-context:clean
:modules:spring-context-support:clean
:modules:spring-core:clean
:modules:spring-jdbc:clean
:modules:spring-jms:clean
:modules:spring-orm:clean
:modules:spring-tx:clean
:modules:spring-web:clean
:modules:spring-webmvc:clean
:modules:spring-webmvc-portlet:clean
:modules:spring-agent:java15:clean
:modules:spring-aop:java14:clean
:modules:spring-aop:java15:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-context-support:java14:clean
:modules:spring-context:java14:clean
:modules:spring-context:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clea n
:modules:spring-jdbc:java14:clean
:modules:spring-jdbc:java15:clean
:modules:spring-jms:java14:clean
:modules:spring-orm:java14:clean
:modules:spring-orm:java15:clean
:modules:spring-tx:java14:clean
:modules:spring-tx:java15:clean
:modules:spring-web:java14:clean
:modules:spring-web:java15:clean
:modules:spring-webmvc-portlet:java14:clean
:modules:spring-webmvc-portlet:java15:clean
:modules:spring-webmvc:java14:clean
:modules:spring-webmvc:java15:clean
:modules:spring-agent:java15:compileJava
:modules:spring-agent:java15:processResources
:modules:spring-agent:java15:classes
:modules:spring-agent:java15:jar
:modules:spring-agent:java15:assemble
:modules:spring-agent:java15:compileTestJava SKIPPED
:modules:spring-agent:java15:processTestResources SKIPPED
:modules:spring-agent:java15:testClasses SKIPPED
:modules:spring-agent:java15:test SKIPPED
:modules:spring-agent:java15:check
:modules:spring-agent:java15:build
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java15\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java15\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

[ant:jar] Warning: skipping jar archive C:\spring-framework-2.5.6.SEC01\modules\
spring-core\build\jar_for_module\spring-core.jar because no files were included.

:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core\ivydata-2.5.6.SEC01.proper
ties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:spring-c
ore\ivydata-2.5.6.SEC01.properties (The filename, directory name, or volume labe
l syntax is incorrect)

:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
Terminate batch job (Y/N)? y

C:\spring-framework-2.5.6.SEC01>





De : Hans Dockter <[hidden email]>
À : [hidden email]
Envoyé le : Jeu 29 Octobre 2009, 10 h 07 min 23 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email]>
À : [hidden email]
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





-- 
Adam Murdoch
Gradle Developer
http://www.gradle.org

Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

Adam Murdoch-2


Hans Dockter wrote:

>
> On Oct 29, 2009, at 8:35 PM, Adam Murdoch wrote:
>
>>
>>
>> Hans Dockter wrote:
>>> Hi Steven,
>>>
>>> we have some issues with our incremental build in trunk. Try to
>>> rebuild with: -C rebuild
>>> Some of the cache state is in <userGradleHome>.
>>
>> I don't think it's the incremental build stuff.
>
> Sorry. I shouldn't answer this kind of email from my mobile phone
> without reading the stacktrace properly.
>
>> Those are ivy warnings in the output, and the path it's trying to
>> write to looks like the internal repository has come back for some
>> reason.
>
> In this form it was always there. Ivy is always writing the deployment
> descriptors into the cache.

There's some way to stop it caching anything on the file system for the
internal repository. I managed to do so a while back, but I can't
remember how. For some reason, ivy is using the cache again. Perhaps the
recent refactoring in there switched it back on?

> The problem is that I have changed the name of the project dependency
> to its path when resolving. Therefore we have this issue. I will
> transform colons into underscores for the name and everything should
> work fine then on windows.

I think a better solution is to not cache anything (for the internal
repository, that is)


--
Adam Murdoch
Gradle Developer
http://www.gradle.org


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

hans_d
Administrator

On Oct 29, 2009, at 9:17 PM, Adam Murdoch wrote:

>
>
> Hans Dockter wrote:
>>
>> On Oct 29, 2009, at 8:35 PM, Adam Murdoch wrote:
>>
>>>
>>>
>>> Hans Dockter wrote:
>>>> Hi Steven,
>>>>
>>>> we have some issues with our incremental build in trunk. Try to  
>>>> rebuild with: -C rebuild
>>>> Some of the cache state is in <userGradleHome>.
>>>
>>> I don't think it's the incremental build stuff.
>>
>> Sorry. I shouldn't answer this kind of email from my mobile phone  
>> without reading the stacktrace properly.
>>
>>> Those are ivy warnings in the output, and the path it's trying to  
>>> write to looks like the internal repository has come back for some  
>>> reason.
>>
>> In this form it was always there. Ivy is always writing the  
>> deployment descriptors into the cache.
>
> There's some way to stop it caching anything on the file system for  
> the internal repository. I managed to do so a while back, but I  
> can't remember how. For some reason, ivy is using the cache again.

I'm not sure. Ivy usually always use the cache for the ivy.xml's  
relevant for resolving a configuration, as it always writes an xml  
file with the data of a resolve for a configuration.

> Perhaps the recent refactoring in there switched it back on?

I can't see how any of my changes could have affected this behavior (I  
know, that is what they always say ;)).

>
>> The problem is that I have changed the name of the project  
>> dependency to its path when resolving. Therefore we have this  
>> issue. I will transform colons into underscores for the name and  
>> everything should work fine then on windows.
>
> I think a better solution is to not cache anything (for the internal  
> repository, that is)

As I understand the ivy logic this is not possible, as the reason why  
ivy writes the ivy.xml's of the resolved dependency into the cache is  
not resolver specific.

- Hans

--
Hans Dockter
Gradle Project Manager
http://www.gradle.org

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|

Re: Re : [gradle-user] Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

hans_d
Administrator
In reply to this post by sdevijver
<base href="x-msg://106/">Hi Steven,

On Oct 29, 2009, at 5:29 PM, Steven Devijver wrote:

Hans,

On closer inspection I think the issue is related to the naming of directories in the cache folder. ":modules:spring-core" is not a valid folder name on windows because of the colons.

This is fixed now.

Thanks

- Hans


Steven


De : Hans Dockter <[hidden email]>
À : "[hidden email]" <[hidden email]>
Envoyé le : Jeu 29 Octobre 2009, 16 h 37 min 21 s
Objet : Re: [gradle-user] Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

we have some issues with our incremental build in trunk. Try to rebuild with: -C rebuild
Some of the cache state is in <userGradleHome>.

- Hans

On Oct 29, 2009, at 13:26, Steven Devijver <[hidden email]> wrote:

Hey Hans,

I've downloaded the latest version. All is not well, have a look at the output below. I've removed my .gradle folder to no avail. I've uploaded the project again since the version you've used might not have been representative:


Steven


---Output---


C:\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-agent:clean
:modules:spring-aop:clean
:modules:spring-beans:clean
:modules:spring-context:clean
:modules:spring-context-support:clean
:modules:spring-core:clean
:modules:spring-jdbc:clean
:modules:spring-jms:clean
:modules:spring-orm:clean
:modules:spring-tx:clean
:modules:spring-web:clean
:modules:spring-webmvc:clean
:modules:spring-webmvc-portlet:clean
:modules:spring-agent:java15:clean
:modules:spring-aop:java14:clean
:modules:spring-aop:java15:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-context-support:java14:clean
:modules:spring-context:java14:clean
:modules:spring-context:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clea n
:modules:spring-jdbc:java14:clean
:modules:spring-jdbc:java15:clean
:modules:spring-jms:java14:clean
:modules:spring-orm:java14:clean
:modules:spring-orm:java15:clean
:modules:spring-tx:java14:clean
:modules:spring-tx:java15:clean
:modules:spring-web:java14:clean
:modules:spring-web:java15:clean
:modules:spring-webmvc-portlet:java14:clean
:modules:spring-webmvc-portlet:java15:clean
:modules:spring-webmvc:java14:clean
:modules:spring-webmvc:java15:clean
:modules:spring-agent:java15:compileJava
:modules:spring-agent:java15:processResources
:modules:spring-agent:java15:classes
:modules:spring-agent:java15:jar
:modules:spring-agent:java15:assemble
:modules:spring-agent:java15:compileTestJava SKIPPED
:modules:spring-agent:java15:processTestResources SKIPPED
:modules:spring-agent:java15:testClasses SKIPPED
:modules:spring-agent:java15:test SKIPPED
:modules:spring-agent:java15:check
:modules:spring-agent:java15:build
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java15\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java15\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

[ant:jar] Warning: skipping jar archive C:\spring-framework-2.5.6.SEC01\modules\
spring-core\build\jar_for_module\spring-core.jar because no files were included.

:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core\ivydata-2.5.6.SEC01.proper
ties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:spring-c
ore\ivydata-2.5.6.SEC01.properties (The filename, directory name, or volume labe
l syntax is incorrect)

:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
Terminate batch job (Y/N)? y

C:\spring-framework-2.5.6.SEC01>





De : Hans Dockter <[hidden email]>
À : [hidden email][hidden email]
Envoyé le : Jeu 29 Octobre 2009, 10 h 07 min 23 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email][hidden email]>
À : [hidden email][hidden email]
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







Reply | Threaded
Open this post in threaded view
|

Re : [gradle-user] Re : [gradle-user] Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

sdevijver
Hey Hans,

The ivy error messages indeed have vanished, and I can now add a project dependency on ':modules:spring-core:java14' from ':modules:spring-beans:java14'.

Thanks!

Steven


De : Hans Dockter <[hidden email]>
À : [hidden email]
Envoyé le : Ven 30 Octobre 2009, 12 h 39 min 12 s
Objet : Re: [gradle-user] Re : [gradle-user] Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

On Oct 29, 2009, at 5:29 PM, Steven Devijver wrote:

Hans,

On closer inspection I think the issue is related to the naming of directories in the cache folder. ":modules:spring-core" is not a valid folder name on windows because of the colons.

This is fixed now.

Thanks

- Hans


Steven


De : Hans Dockter <[hidden email]>
À : "[hidden email]" <[hidden email]>
Envoyé le : Jeu 29 Octobre 2009, 16 h 37 min 21 s
Objet : Re: [gradle-user] Re : [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

we have some issues with our incremental build in trunk. Try to rebuild with: -C rebuild
Some of the cache state is in <userGradleHome>.

- Hans

On Oct 29, 2009, at 13:26, Steven Devijver <[hidden email]> wrote:

Hey Hans,

I've downloaded the latest version. All is not well, have a look at the output below. I've removed my .gradle folder to no avail. I've uploaded the project again since the version you've used might not have been representative:


Steven


---Output---


C:\spring-framework-2.5.6.SEC01>gradle clean build upload
:modules:spring-agent:clean
:modules:spring-aop:clean
:modules:spring-beans:clean
:modules:spring-context:clean
:modules:spring-context-support:clean
:modules:spring-core:clean
:modules:spring-jdbc:clean
:modules:spring-jms:clean
:modules:spring-orm:clean
:modules:spring-tx:clean
:modules:spring-web:clean
:modules:spring-webmvc:clean
:modules:spring-webmvc-portlet:clean
:modules:spring-agent:java15:clean
:modules:spring-aop:java14:clean
:modules:spring-aop:java15:clean
:modules:spring-beans:java14:clean
:modules:spring-beans:java15:clean
:modules:spring-context-support:java14:clean
:modules:spring-context:java14:clean
:modules:spring-context:java15:clean
:modules:spring-core:java14:clean
:modules:spring-core:java15:clea n
:modules:spring-jdbc:java14:clean
:modules:spring-jdbc:java15:clean
:modules:spring-jms:java14:clean
:modules:spring-orm:java14:clean
:modules:spring-orm:java15:clean
:modules:spring-tx:java14:clean
:modules:spring-tx:java15:clean
:modules:spring-web:java14:clean
:modules:spring-web:java15:clean
:modules:spring-webmvc-portlet:java14:clean
:modules:spring-webmvc-portlet:java15:clean
:modules:spring-webmvc:java14:clean
:modules:spring-webmvc:java15:clean
:modules:spring-agent:java15:compileJava
:modules:spring-agent:java15:processResources
:modules:spring-agent:java15:classes
:modules:spring-agent:java15:jar
:modules:spring-agent:java15:assemble
:modules:spring-agent:java15:compileTestJava SKIPPED
:modules:spring-agent:java15:processTestResources SKIPPED
:modules:spring-agent:java15:testClasses SKIPPED
:modules:spring-agent:java15:test SKIPPED
:modules:spring-agent:java15:check
:modules:spring-agent:java15:build
:modules:spring-core:java14:compileJava
:modules:spring-core:java14:processResources
:modules:spring-core:java14:classes
:modules:spring-core:java14:jar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

:modules:spring-core:java15:compileJava
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
:modules:spring-core:java15:processResources
:modules:spring-core:java15:classes
:modules:spring-core:java15:jar
:modules:spring-core:moduleJar
:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java14\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java14\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core:java15\ivydata-2.5.6.SEC01
.properties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:s
pring-core:java15\ivydata-2.5.6.SEC01.properties (The filename, directory name,
or volume label syntax is incorrect)

[ant:jar] Warning: skipping jar archive C:\spring-framework-2.5.6.SEC01\modules\
spring-core\build\jar_for_module\spring-core.jar because no files were included.

:: problems summary ::
:::: WARNINGS
        exception occured while writing properties file C:\Users\steven.ERICOM\.
gradle\cache\org.springframework\:modules:spring-core\ivydata-2.5.6.SEC01.proper
ties: C:\Users\steven.ERICOM\.gradle\cache\org.springframework\:modules:spring-c
ore\ivydata-2.5.6.SEC01.properties (The filename, directory name, or volume labe
l syntax is incorrect)

:modules:spring-beans:java14:compileJava
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:modules:spring-beans:java14:processResources
:modules:spring-beans:java14:classes
Terminate batch job (Y/N)? y

C:\spring-framework-2.5.6.SEC01>





De : Hans Dockter <[hidden email]>
À : [hidden email][hidden email]
Envoyé le : Jeu 29 Octobre 2009, 10 h 07 min 23 s
Objet : Re: [gradle-user] Re : [gradle-user] Next problem with Spring build

Hi Steven,

this is fixed and I can build the attached sample project successfully.

- Hans

--
Hans Dockter
Gradle Project Manager


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:

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:


Steven



De : Hans Dockter <[hidden email][hidden email]>
À : [hidden email][hidden email]
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