Philippe,
I have found a way to use the src/main/gwt folder work seamless between m2e,
GPE and maven-gwt-plugin.
When using this method src/main/gwt shows up in Eclipse as a src folder and
nothing is excluded. Also doing a gwt:compile and gwt:run from the command
line worked fine as well.
On 8 March 2011 06:56, Philippe Beaudoin philippe.beaud...@gmail.com wrote:
A quick update on my progress on this...
As you suggested, adding src/main/resources as source in Eclipse works fine.
The problem is that m2eclipse automatically adds excluding=** in
.classpath for any resource folder.
A quick update on my progress on this...
As you suggested, adding src/main/resources as source in Eclipse works fine.
The problem is that m2eclipse automatically adds excluding=** in
.classpath for any resource folder. I have therefore not found a way to have
the GEP work out-of-the-box with a
There's a deeper question there: are UiBinder ui.xml, LocalizableResources
properties, ClientBundle css, images, etc. resources or sources?
Because these are all about client-side code, which is meant to be given to
the GWT Compiler, I tend to think of them as sources more than
resources.
In
First, one idea about the original question. You might be able to get
away with adding src/main/resources as a source folder in the Eclipse
project if it isn't already. It's been a while since I've used
Eclipse; I don't know if that would be enough to make the GEP happy.
If calling
Phillippe, I'm in the same situation as you, just multiplied a few
times, since I have multiple modules that each have the same copy of
my define.css file in them (since you can't use CssResources as a
src ...), so I have to drop a whole directory structure into my war.
I think - and I haven't
Thanks for all the answers! I'm glad to see it's a popular topic.
Thomas insight on source vs resource makes sense, but as Brian pointed out,
the problem I have is really about having non-java files in the java
directory. I'd be fine having everything sit under /src/main/.
Given that my
On 3 March 2011 21:31, Philippe Beaudoin philippe.beaud...@gmail.com wrote:
Hi!
I'm using Maven to build my GWT project, together with the standard Maven
directory layout. That is, sources are in src/main/java while resources
(such as CSS files) are in src/main/resources.
Now, in one of my
On 4 March 2011 12:02, Thomas Broyer t.bro...@gmail.com wrote:
There's a deeper question there: are UiBinder ui.xml, LocalizableResources
properties, ClientBundle css, images, etc. resources or sources?
From Maven's point of view: yes, they are resources, not sources.
Sources contain source
There's a deeper question there: are UiBinder ui.xml, LocalizableResources
properties, ClientBundle css, images, etc. resources or sources?
From Maven's point of view: yes, they are resources, not sources.
Sources contain source code (i.e. Java code).
Java code is just one example. Groovy
On 4 March 2011 19:53, Brian Reilly brian.irei...@gmail.com wrote:
There's a deeper question there: are UiBinder ui.xml, LocalizableResources
properties, ClientBundle css, images, etc. resources or sources?
From Maven's point of view: yes, they are resources, not sources.
Sources contain
I haven't worked with Groovy/Scala and Maven. Are you saying
Groovy/Scala code is supposed to go in src/main/resources? That would
indeed be strange.
Generally, no. Groovy (and maybe Scala too) is a little bit of an
unusual case because (I think) you don't actually have to compile the
source
Hi!
I'm using Maven to build my GWT project, together with the standard Maven
directory layout. That is, sources are in src/main/java while resources
(such as CSS files) are in src/main/resources.
Now, in one of my .ui.xml file I have a ui:style tag that uses an src
attribute to define some
13 matches
Mail list logo
