Hi Thomas, today I've tried to test the build with buck, but it has not worked for me...
On the root, the command "buck build" asks to specify a build target, while "buck targets" prints lots of empty lines then it rise a "RuntimeException: Not an ordinary file: gwt_tools/lib/javax/validation/validation-api-1.0.0.GA.jar" while on the /user folder running "buck targets" gives a "No such build target: //:servlet-api." (I've used the latest "buck" compiled after a master clone of github, on a Mac OS X with a freshly installed jdk 7 as buck don't run on windows and I didn't had yet java 7 on the mac). Which operative system do you use to build GWT with buck? Tomorrow I will try to find time to take a look at the POMs. If there is something else I can do for you (i.e. test patches), let me know I will try to support you. Cristiano 2013/9/25 Thomas Broyer <t.bro...@gmail.com> > > > On Wednesday, September 25, 2013 9:52:25 AM UTC+2, Cristiano wrote: >> >> Hi Thomas, >> I'm (part-time) having a look at your gwt-sandbox with maven build; >> >> I like the way it is modularized: >> gwt-dev-parent >> gwt-jsni-parser >> gwt-util-parent >> gwt-shared >> gwt-tools-api >> gwt-dev-json >> gwt-dev-ext >> gwt-user-parent >> gwt-core-shared >> gwt-core-client >> gwt-compiler >> gwt-maven-plugin >> gwt-regexp-server >> gwt-http >> gwt-safehtml-server >> gwt-codegen >> gwt-jetty-launcher >> gwt-devmode >> gwt-codeserver >> gwt-i18n-shared >> gwt-i18n-server >> gwt-core-server >> gwt-regexp-client >> gwt-bindery-parent >> event >> event-gwt >> gwt-event-shared >> gwt-event-client >> gwt-event-logical-shared >> gwt-event-logical-client >> gwt-safehtml-client >> gwt-dom >> gwt-i18n-client >> gwt-rpc-shared >> gwt-rpc-api >> gwt-rpc-client >> gwt-rpc-server >> gwt-browsermanager >> gwt-resources-core >> gwt-window >> gwt-timer >> gwt-junit >> gwt-jsonp >> gwt-resources >> gwt-mockutilities >> gwt-safecss-server >> gwt-safecss-client >> autobean-shared >> autobean-vm >> autobean-gwt >> gwt-user >> requestfactory-shared >> requestfactory-client >> requestfactory-server >> requestfactory-gwt >> requestfactory-apt >> gwt-dev >> gwt-user >> gwt-codeserver >> gwt-legacy-parent >> >> I think it is a very precious piece of work! >> >> >> The build process fails however in resolution of a pugin, >> com.google.gwt.maven:gwt-**maven-plugin:jar:2.6.0-**SNAPSHOT >> but it is not the >> org.codehaus.mojo<http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.codehaus.mojo%22> >> :gwt-maven-**plugin:jar:2.6.0-SNAPSHOT >> >> is that the one at >> https://github.com/tbroyer/**gwt-maven-plugin<https://github.com/tbroyer/gwt-maven-plugin> >> ? >> > > No, it's the <module>maven</module>. It's a snapshot/copy of the one > linked above. > > >> I don't like that it is still required to have the gwt-tools in the >> environment path; >> > > This is a temporary step in the migration process. The goal is to migrate > to non-patched/non-repackaged dependencies whenever possible, and deploy > the third-party deps on Central otherwise. > > >> referring to the your post ;-) for me the ultimate build tool is the one >> that allow you to build a project in two steps: >> >> [me@host]# ultimate-scm checkout >> http://my.project.org/source_**code<http://my.project.org/source_code>trunk >> [me@host]# ultimate-build-tool build trunk >> >> having to configure gwt-tools it is out of my ideal way of building a >> project: I don't know if it possible, but gwt-tools should be mavenized too >> in my opinion. Many libs found inside the gwt tools are available as maven >> artifacts in Maven Central Repo (for stability, I always try to avoid >> referring dependency not found on http://search.maven.org/) but this may >> require >> >> Later I also want to try out your buck build files at https://gwt-review. >> **googlesource.com/3741 <https://gwt-review.googlesource.com/3741>, >> (if I find out how the command line options to apply the patch :-D) so to >> compare the buck output. >> > > There's a "download" section next to each "patch set" giving you the Git > commands to checkout, pull or cherry-pick the changes. > > Just let me know if you want me to continue providing feedback, here ore >> somewhere else, or I will make some tests by myself and only give news in >> case i achieve something useful. >> > > Feedback is always welcome! I'd particularly appreciate a review of the > POMs (not much which modules I created and what I put into them, more about > how each module is built and who module dependencies are managed). I tried > to follow The Maven Way™ as much as possible. > > -- > http://groups.google.com/group/Google-Web-Toolkit-Contributors > --- > You received this message because you are subscribed to the Google Groups > "GWT Contributors" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
