Hi I have to figure out the gerrit instructions but you may fork this in the mean time.
the initial transform was chronicled on a plus posting and is hopefully repeatable on current trunk to some degree at https://plus.google.com/u/0/112159826230131242033/posts/2vWKkHoiZZT current most-effort sha1 for pre-2.5.0 is at https://github.com/jnorthrup/gwt/commit/36b079a550b2f6959750d1647766677b6207bb92 ( https://github.com/jnorthrup/gwt/network ) Bhaskar has sent me a link to gerrit this week but other priorities have held me from it. it may be as simple as stealing the poms that are here since they link the custom gwt tools jars cdn entries. It seems universally accepted that the unit tests will not survive this effort. On Sat, Nov 2, 2013 at 7:02 AM, Cristiano Costantini < cristiano.costant...@gmail.com> wrote: > Hi James, > in the report of the latest GWT Contributor Hangout it is written that you > want to work on Mavenization. > > I would like to help in some way (if I have time and the right skills). > > Can you tell us what it is your idea? > It is written that you have shell scripts that do the conversion, can you > share them? > > Thank you, > > Cristiano > > > > > > > > 2013/10/30 James Northrup <northrup.ja...@gmail.com> > >> >* dependencies have to be deployed to a Maven repo >> >> I wanted to chime in here, the dependencies to build a splattered >> hierarchy of java with poms using intellij to back-fill dependencies is >> here, tested on 2.5.0--rc i beleive. >> >> <repository> >> <id>gwt-maven-rewraps</id> >> <url>http://gwt-maven-rewraps.googlecode.com/git/</url> >> </repository> >> >> if intellij can backfill gradle builds the same way it backfills with >> maven deps, all the better. >> >> in my experience things reach a point of mvn clean install with poms if >> you cordone off unit test support to be last and then don't run the unit >> tests. >> >> >> On Wednesday, October 2, 2013 9:29:46 AM UTC-7, Thomas Broyer wrote: >>> >>> >>> >>> On Wednesday, October 2, 2013 4:48:14 PM UTC+2, Geoffrey Wiseman wrote: >>>> >>>> On Sunday, September 29, 2013 8:51:47 PM UTC-4, Matthew Dempsky wrote: >>>>> >>>>> Anyway, I'm of the same opinion here as Thomas: I want to make it easy >>>>> for developers to use GWT in their projects and to contribute to GWT >>>>> itself. I supported switching to Maven as a means to this end, but I'm no >>>>> fan of it beyond that, and I don't think any other core GWT contributors >>>>> are at this point. >>>>> >>>> >>>>> To summarize: if anyone still feels strongly that GWT should use >>>>> Maven, those individuals need to roll up their sleeves and work on making >>>>> it happen. >>>>> >>>> >>>> I neither love or hate Maven. It's one of the best supported build >>>> tools in Java, and I end up using it for that reason as much as anything >>>> else. It simplifies some things and makes other things more complex. If one >>>> of its alternatives got really popular, I would probably try it. In the >>>> end, I probably prefer Maven to Ant, mainly because Maven projects /tend/ >>>> to be a little more likely to work out of the box without configuration on >>>> an individual developer's machine, but that's more to do with how people >>>> use Ant than with Ant itself. >>>> >>>> That said, I agree with a bunch of the comments here that getting GWT >>>> to the point where someone can contribute to it without days of setup is >>>> key; I once tried to contribute a patch to something, but after a few hours >>>> of not getting the project fully set up, I gave up and went back to what I >>>> was actually working on. If you can reduce the barrier to entry so that >>>> it's not hard to contribute, even if that means installing Gradle or Buck, >>>> I think the problem is solved. If you moved to Maven and still had immense >>>> setup hurdles, the problem still isn't solved, AFAICS. >>>> >>> >>> The main issue with Maven here is that the road is long to reach a state >>> where setting up your dev env is a breeze: >>> * dependencies have to be deployed to a Maven repo >>> * code *has* to be modularized a bit (because, as I said, gwt-dev tests >>> depend on gwt-user and the hello sample sources) >>> There might be some intermediary steps but we'd then lose "features" of >>> the build (e.g. no gwt-dev tests), and/or it wouldn't solve the setup issue >>> (if you don't deploy deps to a Maven repo) >>> So moving to Maven requires a "big bang" move, i.e. the easiest way to >>> fail. >>> Gradle allows for "baby steps": 1) make it work 2) make it better 3) >>> modularize, piece by piece. >>> Buck would require some work to setup IDEs, including hand-generating >>> Eclipse .project/.classpath files "by hand". >>> >>> >>>> So, I'd just be happy if that barrier to entry could be reduced -- >>>> reduced setup, increased modularity, simpler out-of-the-box configuration, >>>> etc. That'd make it easier for people like me to be more involved. >>>> >>> -- >> 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 a topic in the > Google Groups "GWT Contributors" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-web-toolkit-contributors/MZRnJwCbKUM/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > google-web-toolkit-contributors+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- Jim Northrup * (408) 837-2270 * -- 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.
