Quoting Marc Grue <[email protected]>:
On 2011-11-22, at 16.00, Stanislav Muhametsin wrote:
You might have m-2 somewhere in your temporary files. IIRC on
Windows at least, it stores the gradle in
C:\Users\<username>\.gradle or something like that. If it spots any
gradle version in there, it will use that. You have to delete that
folder to force it re-download the gradle.
Yes. Removing the folder
~/.gradle/wrapper/dists/gradle-1.0-milestone-2/
and file
~/.gradle/wrapper/dists/gradle-1.0-milestone-2-bin.zip
made the build run (using m-3 as 'planned').
Congrats :)
<snip> (I agree on what you said there)
BUT the Idea artifacts (module .iml files...) were still not build
when I ran ./gradlew. Aren't they supposed to be built? The only
error messages the build produced (apart from unchecked/unsafe
operations and javadoc warnings) was:
I think you might need to run ./gradlew idea . At least for me, in
order to generate Eclipse project files, I need to run ./gradlew
eclipse .
Btw, the Eclipse project files won't build. They have loads of
circular references, so it is possible to load them, and to observe
the source code, but building fails at the moment.
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
