In case anyone on this thread missed the announcement, the Google Plugin for
Eclipse 1.3 preview is now available:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/981bae88b387b2a6/468ca0d8e04532cb
Keith
On Tue, Mar 2, 2010 at 2:02 PM, bkbonner brian.bon...@paraware.com
Cool. Thx
On Mar 1, 2:56 pm, Keith Platfoot kplatf...@google.com wrote:
We're working on integrating our last few changes today, so look for an
announcement and download link sometime tomorrow or Wednesday. :-)
Keith
On Mon, Mar 1, 2010 at 2:46 PM, bkbonner brian.bon...@paraware.com wrote:
Keith, any news on the plugin update?
Brian
On Feb 4, 2:33 pm, Keith Platfoot kplatf...@google.com wrote:
Yes, I've been meaning to reply back to this thread. Thanks for reminding
me, Brian! :-)
Our plans for the next release of the Google Plugin for Eclipse (1.3)
include 4 changes
We're working on integrating our last few changes today, so look for an
announcement and download link sometime tomorrow or Wednesday. :-)
Keith
On Mon, Mar 1, 2010 at 2:46 PM, bkbonner brian.bon...@paraware.com wrote:
Keith, any news on the plugin update?
Brian
On Feb 4, 2:33 pm, Keith
Hi Keath,
Great initiative, thank you for looking in to maven support !!!
I'm using maven for some years now and introduced it at a number of
companies...
I can really recommend it, it's great to see google giving it more
attention, please continue the good job!
I just (last week) finished
Keith, this sounds great! I look forward to the plugin drop. Maybe
a News Noteworthy in the spirit of the other Eclipse modules would
be helpful.
It wasn't clear to me. Will this plugin release solve this issue:
1. Maven standard is using the src/test/java folder for test
cases. Mvn
Hi Keith,
Great great !!!
In fact currently it may works but it is need some twix in the WTP metadata
project file. BTW it a very comfortable environment, where it is easy and
efficient to test general integration (WEB1 + WEB2). Very efficient, because
you can choose or not to debug
Thx a lot for all this, it will clearly simplify GWT with Maven, but did you
plan to add some WTP support in the next GEP release ?
On Thu, Feb 4, 2010 at 8:33 PM, Keith Platfoot kplatf...@google.com wrote:
Yes, I've been meaning to reply back to this thread. Thanks for reminding
me, Brian!
Hi Olivier,
GPE 1.3 should be compatible with WTP/Eclipse EE. For example, you'll be
able to easily add GWT and/or App Engine to an existing Dynamic Web Project,
and then debug the application using the GPE Web Application launch
configurations. For GWT projects that have a separate backend
Keith, are you going to give the folks who replied to your message
some sort of thoughts on what you're going to implement and hopefully
let us try it before you end up releasing the next release of the
plugin?
Brian
On Jan 13, 11:35 am, Keith Platfoot kplatf...@google.com wrote:
Hi folks,
And hopefully (Nir mentioned this prior), there will be a way to
exclude a specific set of classes via some 'ant matcher' from the
module. We keep the path the same and it looks like GWT looks at both
directories and throws errors which I don't believe affect execution,
but are confusing:
Yes, I've been meaning to reply back to this thread. Thanks for reminding
me, Brian! :-)
Our plans for the next release of the Google Plugin for Eclipse (1.3)
include 4 changes designed to make integration with Maven and J2EE projects
easier:
1. The WAR directory can now be configured to be
Any improvements in GWT-Maven support from Google would be excellent! Google
are 'maven friendly' :) THANKS KEITH AND OTHERS!
I can't speak highly enough of Maven. It's an instant injection of mature
engineering practices for projects and companies alike. It's a shame it has
becoming
Hi all, from the current version IMHO there are 2 issues.
1- layout issue (as you mention) src/main/webapp or equivalent must be input
only.
2- classloader issues when using spring namespace handlers with DevMode.
A working workaround is to work with WTP (without jetty server) and let WTP
deploy
Hi,
From our perspective, we managed to get things working somewhat
adequately as follows:
1. use maven for automated builds and awesome dependency management
2. use eclipse and maven eclipse plugin
3. use gwt and gae plugins (where SDK must point to the same versions
as those declared in
On Tue, Jan 26, 2010 at 12:01 AM, cowper iamco...@gmail.com wrote:
Hi,
From our perspective, we managed to get things working somewhat
adequately as follows:
1. use maven for automated builds and awesome dependency management
2. use eclipse and maven eclipse plugin
3. use gwt and gae
Hi Keith,
Thanks for offering to help us maven users. I wish you guys did use
maven :)
On the development workstation, we use STS (for our purposes, Eclipse
Ganymede with m2eclipse plugin). We use the Google Plugin for Eclipse
for Development mode. We run development mode from the launch menu
6. In eclipse we just start Debug as Web application. (with all
libraries manually copied into war/WEB-INF/lib)
This is our main problem, and I don't think it is related to only
maven builds. Instead of using the project's class path including
references to other projects and external jars
As a complement I like to say that when using noserver mode
- using a classic WTP deployment approach for server side component
- GEP in this case manage only the GWT (client) code
In this case, it works perfectly as you expected.
It is just the embedded jetty server classpath that doesn't
On Wed, Jan 20, 2010 at 12:04 PM, Eelco Hillenius eelco.hillen...@gmail.com
wrote:
6. In eclipse we just start Debug as Web application. (with all
libraries manually copied into war/WEB-INF/lib)
This is our main problem, and I don't think it is related to only
maven builds. Instead of
Hi
We, at my work, use a different approach, than others I see mentioned here.
Development:
We are developers using eclipse and Intellij. Important for us is IDE
indenpendent usage, so I have created a Launcher.java file
which actually starts HostedMode.java with appropriate arguments. That way
First of all I would like to thank You for taking time to address the
issues which Maven users have. My comments might be slightly off topic
since my project doesn't use Eclipse and the Google plugin for Eclipse
but relies heavily on Maven, the wonderful gwt-maven-plugin (http://
Hi
It's a great new
- Create a new project?
Just a maven process, I've never used the perhaps-existing maven-gwt-plugin
archetype because I use very custom
- Perform GWT compiles?
With maven-gwt-plugin during packaging (clean install).
Some time with GEP when I want to test
@googlegroups.com
Subject: Re: Maven users survey
Hi Keith, this is fantastic that you are taking up this initiative.
I built a GWT 1.7 app using maven and the codehaus plugin
http://mojo.codehaus.org/gwt-maven-plugin/
There are a couple of different variants of maven gwt plugins, but the codehaus
GWT
On Wed, Jan 13, 2010 at 5:35 PM, Keith Platfoot kplatf...@google.com wrote:
Hi folks,
For the next release of the Google Plugin for Eclipse, we're planning on
making a few tweaks to make life easier for Maven users. That's right: we've
seen the stars on the issue tracker, and have decided
Hi Keith,
We are in the process of upgrading to GWT 2.0.0, so what our best
practices are is an interesting question right now, but here goes:
1. Our main pain point is the /war conundrum you spoke of.
- We configure the maven-war-plugin with webappDirectory${basedir}/
war/webappDirectory (new
Hello,
I know, this is GWT thread, but as I understand you are on Google
Plugin for Eclipse team,
so I assume, I can bother you regarding both GWT and GAE.
The problem with gwt-maven-plugin is that when running GAE project
locally, as described by other people above,
GAE is not initialized and
Hello,
I know, this is GWT thread, but as I understand you are on Google
Plugin for Eclipse team,
so I assume, I can bother you regarding both GWT and GAE.
The problem with gwt-maven-plugin is that when running GAE project
locally, as described by other people above,
GAE is not initialized and
Hi Keith,
basically my issues re described here:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/de0941a7c657c8f0/cbbf6292588041f8?#cbbf6292588041f8.
1. We have gwt as a maven 2 project where you can find these plugins
in pom file. Plus dependencies to other
Hi folks,
For the next release of the Google Plugin for Eclipse, we're planning on
making a few tweaks to make life easier for Maven users. That's right: we've
seen the stars on the issue tracker, and have decided it's time to act. I
would say, we feel your pain, but the problem is, we don't.
30 matches
Mail list logo
