Hi Niclas, this gradle build system works seamlessly for me. >From extracted src distribution I was able to:
- directly import new project into IDEA pointing to root gradle.build all modules properly configured so one can point to tutorials Main class and hit Run - generate IDEA project/modules via ./gradlew idea for older versions of IDEA versions ( without gradle plugin ) - easy install artifacts into my local maven repo I skip some tasks so I get it there quickly ./gradlew -Dversion=2.0-beta-1 install -x signArchives -x javadocs -x javadoc -x test -x website The bin distribution should save from compilation I assume. But I don't see way how to use (run samples/tutorials) this distribution. Thanks for the effort ! - Tibor On Jul 29, 2012, at 6:29 PM, Niclas Hedhman wrote: > Gang, > > Although there are still a few things to consider and figure out for > 2.0, I have spent most of the time the last few weeks trying to get > the final artifacts to build. > > Still got a bit more to do on it, but I would like to get some feedback;; > > http://repository.ops4j.org/maven2/org/org.qi4j/2.0-beta-1/ > > One particular thing is that I am trying to satisfy the non-Maven > developer by generating the URLs for downloading the dependencies of > each of our components and stick it into ilb/dependencies/ folder. I > have still not worked out how to locate the repository, so Maven > Central is currently hardcoded. > > Also, should we ship the entire website, or is it better to get the > 'versioning' of website working, and link the particular version from > the release with a redirect? > > I have excluded putting the "-javadoc" jars into the binary distro, > primarily since I think it is only used by the Maven developer and > they pick that up from the repository. The full javadoc (one > hierarchy) is in the dist though, and I think that is a good thing. > Opinions? > > What else? > > The idea is that if you download the sources, you should be able to > > ./gradlew -Dversion=2.0-beta-1 dist > > and it will build itself, the binary dist and explode the binary dist > into build/dist of the root project. > > But I haven't tested that yet. > > > The build now generates dependencies.xml for each module in Maven pom > format, and I will figure out how to auto include that in the > documentation for each module. Suggestion of DocBook format that will > style well is welcome. > > > So, even though I have been rather quiet lately, I have managed to > push some important (boring, ungrateful) stuff forward. > > > Again; Please review and come with feedback. > > > Cheers > -- > 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 _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
