Re: [gwt-contrib] Mavenizing GWT

2012-03-25 Thread Thomas Broyer
On Saturday, March 17, 2012 4:26:01 AM UTC+1, Ray Cromwell wrote: > > I agree with most of this, but I just wanted to mention that I think > breaking up the dependency chain will be a little tricky for maven > when it comes to tests. Maven general practice is that a given module > contains its te

Re: [gwt-contrib] Mavenizing GWT

2012-03-16 Thread Hilco Wijbenga
On 16 March 2012 20:26, Ray Cromwell wrote: > I agree with most of this, but I just wanted to mention that I think > breaking up the dependency chain will be a little tricky for maven > when it comes to tests. Maven general practice is that a given module > contains its tests and runs them. The pr

Re: [gwt-contrib] Mavenizing GWT

2012-03-16 Thread Ray Cromwell
I agree with most of this, but I just wanted to mention that I think breaking up the dependency chain will be a little tricky for maven when it comes to tests. Maven general practice is that a given module contains its tests and runs them. The problem with gwt-dev and gwt-user is that many of the g

[gwt-contrib] Mavenizing GWT

2012-03-16 Thread Thomas Broyer
Hi Rajeev [Cc: GWT-Contrib], I saw you created a BuildingWithMaven wiki page earlier today, which I suppose is about mavenizing the GWT build process. I thought about it a little these past weeks. The major pain point IMO is about dependencies, particularly those that have been patched: ECJ and