On Friday, October 14, 2016 at 10:20:28 AM UTC+2, Kirill Prazdnikov wrote:
>
> Well, my suggestion was only two modules:
> 1. GWT code - builds the client app
> 2. platform independent code (jar) for some logic shared between, for
> example, server app
>
> Is it incorrect ?
>
And so you cho
Well, my suggestion was only two modules:
1. GWT code - builds the client app
2. platform independent code (jar) for some logic shared between, for
example, server app
Is it incorrect ?
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsub
> My recommendation, do NOT create a maven module if you don't need it (I
> think that you do not need it).
>
+1. Right. I would only split my client side code into multiple maven
modules if I want to share client side code with a different project. If
you don't do that, then adding multiple
The IT directory in the gwt-maven-plugin includes more ussage examples,
this one includes all possible maven module types
https://github.com/tbroyer/gwt-maven-plugin/tree/master/src/it/e2e as
described here https://tbroyer.github.io/gwt-maven-plugin/. You do not need
to use resources->includes and
I do not know. We don't use "classifier-sources" in our maven files.
I never run super-dev-mode from command-line. I run it form within the IDE.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving em
> On 12 Oct 2016, at 19:38, Kirill Prazdnikov wrote:
>
> I do not completely understand which problems do you have, but we dont have
> any issues working with SDM with modules I described above.
maybe was something wrong in my project layout. Now I made another test, and in
the submodule I re
I do not completely understand which problems do you have, but we dont have any
issues working with SDM with modules I described above.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from i
> On 12 Oct 2016, at 10:29, Luca Morettoni wrote:
>
> Hi all, currently my application is using a single module for the GWT code,
> but I’d like to split it in some submodules to better organize the code.
> Everything is under maven and I organised the main project layout using
> Thomas Broyer
> On 12 Oct 2016, at 19:05, Kirill Prazdnikov wrote:
>
> As far as I know you need only one GWT maven module that builds the app.
> The rest modules are just regular (platform independent) modules
> (jar) and the gwt-app module depends on it.
>
> So for the client app u have 2: main GWT modul
As far as I know you need only one GWT maven module that builds the app.
The rest modules are just regular (platform independent) modules
(jar) and the gwt-app module depends on it.
So for the client app u have 2: main GWT module (A) with GWT specific code and
GWT dependencies and a plain jar m
As far as I know you need only one GWT maven module that builds the app.
The rest modules are just regular (platform independent) modules
(jar) and the gwt-app module depends on it.
So for the client app u have 2: main GWT module (A) with GWT specific code and
GWT dependencies and a plain jar m
> On 12 Oct 2016, at 10:29, Luca Morettoni wrote:
>
> Hi all, currently my application is using a single module for the GWT code,
> but I’d like to split it in some submodules to better organize the code.
> Everything is under maven and I organised the main project layout using
> Thomas Broyer
Hi all, currently my application is using a single module for the GWT code, but
I’d like to split it in some submodules to better organize the code.
Everything is under maven and I organised the main project layout using Thomas
Broyer gwt-maven-archetypes [1], so now I have a main maven project a
13 matches
Mail list logo
