I think a major goal should be to cooperate with other container plugins,
specifically Jetty. I've been struggling with getting the Jetty plugin to
fully cooperate w/ the gwt plugin and am astounded at how hard it is to:
1. Get my server code to be updated without a server restart (if the
On Mon, Feb 25, 2013 at 4:47 PM, dparish dpar...@gmail.com wrote:
I think a major goal should be to cooperate with other container plugins,
specifically Jetty. I've been struggling with getting the Jetty plugin to
fully cooperate w/ the gwt plugin and am astounded at how hard it is to:
1.
Thomas,
Thanks very much for the response.
First, is there any way you can share a POM from one of your projects -- or
ideally point me at an entire open source project that uses it? Many things
aren't clear (to me) from the docs. Examples:
1). You say add a resource tag.
The problem is if
Inline.
On Sun, Feb 17, 2013 at 2:12 PM, Thomas Broyer t.bro...@gmail.com wrote:
Hmm, there's
https://github.com/tbroyer/gwt-sandbox/blob/master/user/gwt-user-core/pom.xml
but
this is work in progress, and unnecessary complicated in some places. This
is ongoing work to moving GWT itself
On Sun, Feb 17, 2013 at 7:46 AM, Rich rich.bur...@gmail.com wrote:
Thomas,
How does the plugin support supersource today. I've tried to piece this
together from multiple searches and have something close to your option 3,
but it's not clear.
1). How is the plugin configured to use
On Sunday, February 17, 2013 6:37:38 PM UTC+1, Rich wrote:
Thomas,
Thanks very much for the response.
First, is there any way you can share a POM from one of your projects --
or ideally point me at an entire open source project that uses it?
Hmm, there's
On Fri, Nov 16, 2012 at 1:56 AM, Brian Slesinsky bslesin...@gmail.com wrote:
It will be more convenient for Google if all Java code and Java resources
(that is, things in the classpath) are contained in directories named either
java or javatests, and the path from there is where the file should
On Thu, Nov 15, 2012 at 11:59 PM, Thomas Broyer t.bro...@gmail.com wrote:
I fully understand that we'll have to make some concessions for GWT
itself to make it easier for Google (even though Matthew actually told
me the opposite);
Well, our build system is turing complete, so theoretically
Oops, my mistake! Carry on.
On Friday, November 16, 2012 12:00:57 AM UTC-8, Thomas Broyer wrote:
The scope of this poll is however not about GWT itself actually (we'll
see if we can apply the outcome to GWT or not; I'd love to do it so
that GWT can serve as a reference, but if it's
I am not quite sure why super-sources should / must be treated differently?
Back i am probably lacking experience and knowledge here
I like the notion the *gwt.xml files are actuallly part of the sources and
not resources for gwt libraries.
So that would be Option 1, without
It will be more convenient for Google if all Java code and Java resources
(that is, things in the classpath) are contained in directories named
either java or javatests, and the path from there is where the file
should show up in the classpath. We can copy files but it makes builds or
I vote for alternative 1, as it complies with maven convention and I had no
problem at all with this structure.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
On Wednesday, November 14, 2012 11:16:11 AM UTC+1, Nader wrote:
I vote for alternative 1, as it complies with maven convention and I had
no problem at all with this structure.
The question is about whether *in a library* *.gwt.xml and the likes should
be seen as sources or resources, so
I agree with Stefan Ollinger. +1 for second alternative.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/uP_fDPSjRkcJ.
To post to this group,
Hi all,
As some of view may already know, I'm porting GWT to use Maven as the build
system (instead of Ant). I'm also about to reboot GWT+Maven integration
(more to come by the end of the week, stay tuned).
As part of this effort, I'm wondering which project structure to use as the
default,
Hi,
I would prefer alternative 2, since it follows the Maven standard
project layout. Personally I sometimes put the .ui.xml and .gwt.xml
files in the src/main/java folder, since it allows for faster
navigation in Eclipse. I guess that is mainly a tooling issue and should
not have any
It comes without saying (for me at least) that Java sources would go into
src/main/java and public resources (i.e. the things within **/public/**,
e.g. the CSS and image files from the themes) into src/main/resources
I agree with this.
everything in src/main/java
super-sources in
On Tuesday, November 13, 2012 5:18:15 PM UTC+1, Abraham Lin wrote:
Placing the super-sources in src/main/resources may also cause
filter-related surprises.
Ah, good catch!
Also feel free to propose a fourth alternative.
I'd propose keeping non-super sources in src/main/java, public
This is option 3 then (you agreed that It comes without saying (for me at
least) that Java sources would go into src/main/java, and I suppose that
by public resources you mean not only **/public/** but also *.ui.xml and
the like)
Ah sorry, I had misread your definition of everything to
19 matches
Mail list logo
