Re: [Gwt-openlayers-devl] [Gwt-openlayers-users] Maven + Project Structure and Showcase

[Edwin C. <com...@gm...>]

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? :)
> --AH
> ------------------------------------------------------------------------------
> Download Intel&#174; 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
>
>