On 20 January 2011 13:39, Hilco Wijbenga wrote:
> During development of a widget JAR, however, I need to be able to
> change HTML/CSS and see the effect in the browser with a simple
> refresh. I don't know how to do that without using a WAR. So how do
> you work on your widgets? Or do you not run
Hi Jesse,
I know all about Maven and how to do things in the mythical "Maven
Way". I also understand GWT and GWT widgets. The problem is in the
efficient combination.
I would like to have a clean JAR for the widget and a WAR for
integration testing (of that widget). That's all easy.
During devel
Hello,
On Thu, Jan 20, 2011 at 1:24 PM, Hilco Wijbenga
wrote:
> On 20 January 2011 06:26, Jesse Farinacci wrote:
>>
>> This is by far the best solution. If you want to create widgets to be
>> shared across multiple projects, just make a packaging=jar and make
>> sure src/main/java is part of bui
On 20 January 2011 06:26, Jesse Farinacci wrote:
> Greetings Hilco,
>
> On Wed, Jan 19, 2011 at 8:07 PM, Hilco Wijbenga
> wrote:
>>
>> Option 1: It's easy to write a POM that creates a JAR for a GWT widget
>> including CSS and other resources. It's also easy to then write a POM
>> that depends on
Greetings Hilco,
On Wed, Jan 19, 2011 at 8:07 PM, Hilco Wijbenga
wrote:
>
> Option 1: It's easy to write a POM that creates a JAR for a GWT widget
> including CSS and other resources. It's also easy to then write a POM
> that depends on that JAR and creates a WAR for integration testing. So
> far
On 19 January 2011 17:49, Wayne Fay wrote:
>> achieves all my goals but isn't very elegant. Can anyone think of a
>> better way to do this?
>
> A couple thoughts...
>
> 1) You can create a jar out of a war project by binding the jar plugin
> to your build.
Excellent, with a few excludes and attac
> achieves all my goals but isn't very elegant. Can anyone think of a
> better way to do this?
A couple thoughts...
1) You can create a jar out of a war project by binding the jar plugin
to your build.
2) You may want to look at the maven-remote-resources-plugin and think
about putting the GWT w
Hi all,
Option 1: It's easy to write a POM that creates a JAR for a GWT widget
including CSS and other resources. It's also easy to then write a POM
that depends on that JAR and creates a WAR for integration testing. So
far so good.
Problem: Making changes in (e.g.) the CSS requires a full rebuild
