Menu
▾
▴
Re: [Gwt-openlayers-users] Maven + Project Structure and Showcase
|
From: Andrew H. <ahh...@gm...> - 2010-02-22 12:05:30
|
FYI: Here's the post from the "GWT Eclipse Plugin Team" @ 14th Jan. http://groups.google.com/group/google-web-toolkit/browse_thread/thread/b43de4bb51a0ea2d/b0b46575d4892d9c <http://groups.google.com/group/google-web-toolkit/browse_thread/thread/b43de4bb51a0ea2d/b0b46575d4892d9c> On Mon, Feb 22, 2010 at 5:11 PM, Andrew Hughes <ahh...@gm...> wrote: > Thanks Guys, > > There's quite a lot of chatter on the GWT forums regarding support for > Maven. GWT 1.7+ made things harder for the Maven guys - many of the > complexities have now been resolved (mostly due to GWT's hardcoded paths) > but it's not 100%. Google appear to have acknowledged that a significant > proportion of GWT development occurs outside the confounds of Eclipse and do > in fact exist inside maven. We all like EJB's and Hibernate and Spring and > Seam and Struts and.... anyway you get it :) > > If not now for the showcase, then perhaps soon.... > > Re tests: I think this is a tomcat vs jetty classpath issue. In particular > this is related to the Mock dependencies. I don't have code to look at right > now, but I this is a known problem and a change in the gwt-***** <scope> can > resolve it. I'll have a dig and see what I can find. > > > > Take it easy :) > > > > On Mon, Feb 22, 2010 at 12:56 AM, Farrukh Najmi < > fa...@we...> wrote: > >> >> Guys, >> >> First my apologies taht I have not been very involved as UI and GWT has >> been off my radar for a while. >> However, I must say I second doing all project management, build, >> distribution, testing etc. tasks via maven. >> I also second using maven for all sample projects such as showcase. >> >> When I was doing active GWT dev all my projects were maven based and I >> was able to debug client and server code with Netbeans IDE just fine. >> >> Make sure to use the following for gwt maven projects: >> >> http://mojo.codehaus.org/gwt-maven-plugin/ >> >> and to not use the following deprectaed project: >> >> http://code.google.com/p/gwt-maven/ >> >> Sorry I do not have more informatioon at my finger tips but wanted to >> make sure I endorsed the idea of >> using maven maximally. The benefits are huge. >> >> On 02/21/2010 08:06 AM, Edwin Commandeur wrote: >> > Hi Andrew, >> > >> > On of the strongholds of GWT is the IDE support. The showcase has been >> > setup as Google Eclipse project, since that is easy to get running >> > within the Eclipse IDE as long as you have the official Google Eclipse >> > plugin (which will most probably be up-to-date with GWT versions). >> > >> > The GWT-OL is just a jar-red GWT module, so that is easy to compile >> > and package with Maven. >> > >> > The showcase is a webapp and the Google Eclipse default folder >> > structure does not follow the Maven defaults. The showcase should be >> > packaged as a war not a jar. However, I think you would always want to >> > run the showcase in an IDE, in order to be able look at the code and >> > to be able to debug it. >> > >> > I would agree that it would be nice to use Maven for both building the >> > GWT-OL jar and the showcase, and to be independent of the IDE for >> > running the showcase (most IDEs have good Maven support). >> > >> > It is a bit of a pain indeed that you now have to copy the the GWT-OL >> > jar to the showcase. Though an Ant task could easily do that after a >> > package and that Ant task could be called from Maven. Also, it is >> > probably possible to use Maven only for the dependency management for >> > the showcase. Then the default Maven goal for the GWT-OL module should >> > be install. >> > >> > I haven't looked at the gwt-maven project for a while, but in the past >> > it used to be a bit of a pain to get Maven and GWT play together if >> > you want to launch the project and debug it in the IDE. At least, not >> > as easy as using the Google Eclipse plugin. For example look at: >> > http://www.screaming-penguin.com/node/7353. It is not difficult, but >> > automatic copying of the GWT-OL jar or using Maven only for dependency >> > management and subsequently running the project with Google Eclipse >> > seems easier to me. >> > >> > What you can always do is make the poms, and copy the showcase stuff >> > over to a new folder, for example 'samples' or 'explorer' that is >> > setup with Maven in mind and if that works out fine, then we can drop >> > the original showcase. >> > >> > One other thing that has not been fixed yet in the Maven poms is how >> > to run the testcases. The GWT stuff is Ant oriented, so it was easy to >> > setup an Ant test target, but it would be good to fix this in Maven as >> > well. >> > >> > Greetings, >> > Edwin >> > >> > >> > >> > On 19 February 2010 00:05, Andrew Hughes<ahh...@gm...> wrote: >> > >> >> Hi Guys, >> >> I wanted to add something to the showcase (based on some new >> additions). But >> >> this was a little bit odd because... >> >> 1. The showcase is not a maven project. >> >> 2. If it was, then the showcase/openlayers and not grouped maven >> project >> >> (modules) so I can't (easily) have the showcase depend on the latest >> >> snapshot >> >> and then you can get into the fact that the showcase really should be >> on the >> >> same compile/test/release lifecycle e.t.c. >> >> To fix this would require the following: >> >> gwt-openlayers/pom.xml (artifactId=parent, packaging=pom) >> >> gwt-openlayers/gwt-openlayers/pom.xml >> >> (artifactId=gwt-openlayers, packaging=jar) >> >> gwt-openlayers/showcase/pom.xml (artifactId=showcase, packaging=jar). >> >> otherwise, I can't (easily) do a showcase example of recent changes, I >> can't >> >> release them with the gwt-openlayers release and I can't sync the two >> >> dependencies in the release phase. >> >> Thoughts? :) >> >> >> >> -- >> Regards, >> Farrukh >> >> Web: http://www.wellfleetsoftware.com >> >> >> >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Gwt-openlayers-users mailing list >> Gwt...@li... >> https://lists.sourceforge.net/lists/listinfo/gwt-openlayers-users >> > > |
