So far I got this. This seems just a beginning
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
I use 1.6.4. from a maven repo..
I used http://code.google.com/p/gwt-maven/ for my maven build but
moved to the codehouse gwt maven plugin as indicated on the
http://code.google.com/p/gwt-maven/ site, as this latter one will not
be developed anymore and they adviced to move to the codehouse
Just point your output dir to your target dir with the codehouse
plugin and simple ignore it...
That what I do
Works fine...
--Ed
On Apr 16, 3:27 pm, Mark Renouf mark.ren...@gmail.com wrote:
The maven-gwt-plugin from codehaus is looking quite good at this
point. I recommend trying
Hey Salvador,
Nice job on consolidating all of this information. I'm not a Maven user, but
it seems like your information has been helpful to many.
I'm specifically interested in the problems that you're seeing with using
GEP in this situation. Even though right-click launch behaviors may not
Nice job on consolidating all of this information. I'm not a Maven user, but
it seems like your information has been helpful to many.
Hi Rajeev,
Thanks for your input !
I'm specifically interested in the problems that you're seeing with using
GEP in this situation.
You can take a look at
Hey Salvador,
Replies inline:
On Mon, May 4, 2009 at 2:59 PM, Salvador Diaz diaz.salva...@gmail.comwrote:
Nice job on consolidating all of this information. I'm not a Maven user,
but
it seems like your information has been helpful to many.
Hi Rajeev,
Thanks for your input !
I'm
Thanks Murray,
In fact I realised while writing the post that GEP doesn't do anything
in this configuration (I said it in the post) but the google team is
actively working to address the relevant issues. As for the link in
the m2eclipse wiki, I'm a little reluctant to do it now, it'd appear
as a
Excellent! I'll take a closer look next week and be sure to post. What I'm
after is very similar to you although I don't know if I need to use GEP
(what does it actually do?), and want to get it working under RAD 7.5
instead (which is based on eclipse 3.4).
You might also consider adding a link
I'm curious how folks are adapting to this new layout. How many of
you are letting GWT write its output to war/**, and how many are going
the maven approach and moving things to target/war/** ? Personally, I
much prefer the maven idea of keeping source and generated files
separate. However, I
On Thu, Apr 30, 2009 at 10:07 AM, KaffeineComa kaffeinec...@gmail.comwrote:
However, I don't want to be continually swimming upstream
against this layout, in particular if it will cause pain for my
colleagues using Eclipse (I'm an Intellij user myself).
I am most reluctantly following the
I wanted to share some progress I've made in making things work
smoothly together.
First off, I discovered the new phase prepare-package in Maven
2.1.0. This is perfect for binding the gwt compile goal to. This means
the app gets compiled down to Javascript just before packaging, which
is
Thanks heaps for this, its possibly exactly what i'm looking for.
For the 1.6 support, are you using the codehaus plugin or the other one.
I would encourage you to rename in your pom anything confidential, then post
the entire pom here in another post if you can. I wouldn't worry too much
about
I know I am doing something dumb but any suggestions? Also why am I
getting the embedded Tomcat message--I thought things in 1.6 were
transitioning to Jetty?
If you run that goal in debug mode (mvn gwt:run -X) it should tell you
exactly what it's doing (it sounds like it's using a
I think i'm going to open a new issue saying that they should have their own
mailing list :-)
The mailing list (http://mojo.codehaus.org/gwt-maven-plugin/mail-
lists.html http://mojo.codehaus.org/gwt-maven-plugin/mail-%0Alists.html)
is for the whole Mojo project so you'll also get mails
from
The thing I'd not like to lose, is live-edit capability. ie: changes
take effect with a simple page reload in HostedMode (and also Restart
Server button in 1.6).
I think GWT provides enough options to make things work, but it's
harder than it should be. If I had a magic wand though, I'd say
I can't tell how disappointed I am.
Yep, me too. Yet more time spent futzing around trying to keep my src
tree clean.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this
same here...
2009/4/17 P.G.Taboada pgtabo...@googlemail.com
The one remaining issue is the new build output format (WAR), and how
resources are deployed. I'm totally against having GWT compile
directly into /src/main/webapp. It's completely against the principles
of keeping your source
It would seem my original post has uncovered all sorts of aches and
pains with the new GWT structure. Personally I use maven with the GWT-
maven plugin from Google code and only had to change the version
number of GWT 1.6.4 and it worked. I don't actually fully understand
what was changed but I
I have been struggling updating my older style (gwt 1.5 with the
older pre-codehause maven plugin) project working with the codehause
gwt-maven-plugin 1.1-SNAPSHOT.
So I resorted to start with a maven project created using the plugin's
archetype in my Eclipse environment which gives looks like
Does the codehaus maven plugin have a decent mailing list? It seems like
they don't have their own mailing list which is a bit of a pain.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To
Where is the snapshot respository where the versions 1.1-SNAPSHOT
codehaus gwt-maven-plugin lives? only the 1.0 is in the central
repository.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google Web Toolkit
I totally agree on the fact that gwt team should not provide the maven
plugin, the codehaus one can do the job. They should just take care of
beeing able to integrate with any build system.
My problems with the current google eclipse plugin :
* If you enable gwt support on your project, GWT SDK
It would definitely be nice if the Google Eclipse plugin was build
system agnostic, or at least gave you more configuration options.
Maybe we should just file a issue with the Google Eclipse plugin (I
can't find the Google Code project...)?
--
Arthur Kalmenson
On Thu, Apr 16, 2009 at 4:33 AM,
The maven-gwt-plugin from codehaus is looking quite good at this
point. I recommend trying 1.1-SNAPSHOT.
I just reported an issue with running unit tests (which has been fixed
in SVN, waiting on a new SNAPSHOT build). With that it does absolutely
everything I've expected (on all platforms,
I'm totally against having GWT compile
directly into /src/main/webapp. It's completely against the principles
of keeping your source tree clean and putting all artifacts under
target. If you stick with traditional maven approach, it means you
need to execute war:exploded first before
One of the big wins with Maven is the rigid directory structure,
where source files of all stripes are in src/ and build outputs are in
target/. It's good practice because it doesn't allow for intermingling
source files and build files.
The new GWT war/ dir next to src/ problematic because you
Who agrees that having a solid,
feature complete Maven plugin from Google would increase adoption of
GWT faster than anything?
I think the google team is focusing in the basics first, and that
implies not being able to deliver all the goodies at the same time, I
think it all fits rather
On second though I think I agree with Salvador. Looking closer at the
Codehaus plugin it should do the job job in the long term.
On Apr 15, 1:20 am, Salvador Diaz diaz.salva...@gmail.com wrote:
Who agrees that having a solid,
feature complete Maven plugin from Google would increase
I invested more ore less 8h and dont have a wokring configuration of the
trunk of the mojo gwt plugin and gwt 1.6
Some things work, but many don't. Kinda anoying...
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Hi
I was using a maven plugin (http://gwt-maven.googlecode.com/svn/trunk/
mavenrepo) with GWT 1.5.3 without Hosted Mode (in Linux the hosted
mode gives a firefox browser older and doesn't support gears, for
example), I generate a war and the copy it to a jboss server to test
it. I know that it
I find it somewhat odd that the GWT team does not just create an
official maven plugin. They can program the most amazing Java to
Javascript cross compiler, have the most shiny widgets and speedy RPC
services but if people are left in the dark as to how to build the
bloody thing it will never be
We were using Maven because that's what everyone uses, but found
that it did not meet our needs.
* It requires a great deal of configuration to properly build a GWT
project
* The tools to integrate Maven/GWT/Eclipse are always in a state of
flux
* Some of the really nice stuff in Maven
Currently we are trying to update our buildsystem from gwt 1.5 + gwt-maven
from google code
We are trying to use the trunk of gwt-maven from codehaus since those two
plugins are merging.
We were able to sucessfully compile a gwt project, but we still have some
open issues.
Has anyone a working
On Sun, Apr 12, 2009 at 7:35 PM, Daniel Kurka
kurka.dan...@googlemail.comwrote:
Currently we are trying to update our buildsystem from gwt 1.5 + gwt-maven
from google code
We are trying to use the trunk of gwt-maven from codehaus since those two
plugins are merging.
We were able to
Hi,
I just tried to enable maven dependencies management with google
eclipse plugin and m2eclipse. The plugin complains about project
output folder not set to war/WEB-INF/classes.
I know I can switch my maven project output, but is there any chance
the plugin can be set up to adapt to my
I am curious if anybody using Maven+GWT has tried moving to GWT 1.6
yet. I noticed there is no public repository containing the 1.6
realease only RC, Beta, and Milestones. I can always manually deploy
GWT to our internal repository but it's a bit of a pain.
Also, if anybody is using GWT+Maven
I also believe in the importance of build systems! :)
My company's current project (medium size, about 32,000 lines of code)
uses a handwritten Ant build system. We do, however, use the Maven
Ant tasks to manage our project's external dependencies. In addition
to using Ant in our builds, we
Currently we use maven and http://code.google.com/p/gwt-maven/ for our
build process.
When we upgrade to GWT 1.6 we will check the codehaus plugin and how
the new Google Eclipse plugin + new app structure can be used in a
more comfortable way.
Regards,
Martin
On Apr 9, 5:03 pm, Benju
38 matches
Mail list logo
