./gradlew idea is needed and not automatic. Hard for the system to understand if you want IDEA or Eclipse.
The property in build.gradle is a mistake, but I still don't understand why it would make a difference. AND niclas:qi4j-sdk niclas$ ls ~/.gradle/caches 1.0-milestone-2/ 1.0-milestone-3/ 1.0-milestone-4/ artifacts/ niclas:qi4j-sdk niclas$ ls ~/.gradle/wrapper/dists gradle-1.0-milestone-2 gradle-1.0-milestone-2-bin.zip gradle-1.0-milestone-3 gradle-1.0-milestone-3-bin.zip I have the milestone-2 as well, and don't see any problems. Again, can you get this problem manifested again, capture the console output and send it to me? Also, locate the junit test output file that fails and include that as well. I just tested, milestone-2 also builds Qi4j without problems. The deprecations are not in our 'code' but somewhere in the plugins. On Wed, Nov 23, 2011 at 3:47 AM, Marc Grue <[email protected]> wrote: > Hi Stanislav, > > Thanks - I also ran 'gradle idea' too in order to get the Idea artifacts > build (although having some problems running out of java heap memory when > resolving dependencies). I wonder if they build for Niclas or others with > ./gradlew alone - that's the plan, right? > > Cheers, > Marc > > On 2011-11-22, at 20.21, Stanislav Muhametsin wrote: > >> 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 > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
