On Monday, October 19, 2020 at 4:43:26 PM UTC+2, Elhanan wrote:
>
> what's the difference between
> warDir, webappDirectory, workDir,workingDirectory, codeServerWorkDir ,
> devModeWorkDir, tempDir?
> i mean it's hard to follow all those around.
>
I'm assuming you're using autocompletion in
If you put your static resources in the public path of your module (by
default a "public" subpackage next to your *.gwt.xml file), they'll be
copied (by GWT itself, not the gwt-maven-plugin) to the output next to the
*.nocache.js and *.cache.* files, so they'll end up in your WAR.
The only
Therefore I'm using the simplest gwt:devmode... Standalone is the best...
only
But I think you could just use the default dirs...
Elhanan schrieb am Montag, 19. Oktober 2020 um 16:43:26 UTC+2:
> what's the difference between
> warDir, webappDirectory, workDir,workingDirectory,
what's the difference between
warDir, webappDirectory, workDir,workingDirectory, codeServerWorkDir ,
devModeWorkDir, tempDir?
i mean it's hard to follow all those around.
On Mon, Oct 19, 2020 at 2:58 PM Elhanan Maayan wrote:
> hey thomas, the thing is, i wanna do it right without any hacks, but
hey thomas, the thing is, i wanna do it right without any hacks, but if i
demine the pom as gwt-app, the output is just gwt compiled code with no
static html or css resources, if i use war in the pom type, the output is
just the static resources. i want the entire artifact to be considered as
I haven't followed the whole discussion, but if you don't have a need for
shared and server modules (what I call a "standalone" app), then you can
put your HTML file (and associated resources) into your module's public path
I also understand that tbroyer is against doing maven install in general,
which is what i intend to do as it's part of the whole build process, all
i need is for the the entire output be recognized as an artifact to be
carried to he main build , the solution your provider with the assembly
seems
Hmm ok... Never take a look at that...
Elhanan Maayan schrieb am Mo., 19. Okt. 2020, 10:00:
> no i meant, that when i do regular compile i still see *.devmode.* files
> on the target dir, and when i try to use just a normal server, it says it
> can't see the codeserver.
>
> On Mon, Oct 19, 2020
no i meant, that when i do regular compile i still see *.devmode.* files on
the target dir, and when i try to use just a normal server, it says it
can't see the codeserver.
On Mon, Oct 19, 2020 at 1:30 AM Dr. Lofi Dewanto
wrote:
> Hmmm do you mean, maven-gwt-plugin compiles / transpiles
Hmmm do you mean, maven-gwt-plugin compiles / transpiles everything first
before it starts with gwt:devmode? ... Actually it doesn't need to, I
agree... maybe @tbroyer could explain?
Elhanan Maayan schrieb am So., 18. Okt. 2020, 23:58:
> thanks, btw i don't understand why the maven plugin
thanks, btw i don't understand why the maven plugin insists on compiling it
for devmode
On Mon, Oct 19, 2020 at 12:44 AM lofid...@gmail.com
wrote:
> Yes, the main thing you have a fast turn around time for *compile - test
> cycle* for UI development. Because if you are working on UI you don‘t
>
Yes, the main thing you have a fast turn around time for *compile - test
cycle* for UI development. Because if you are working on UI you don‘t care
about the business logic on the server. You just need some *data examples*
which you can mock easily with your DTO...
Elhanan schrieb am Sonntag,
essentially i could use all the real static files in the client side
On Mon, Oct 19, 2020 at 12:30 AM lofid...@gmail.com
wrote:
> Yes and you can control it using Maven assembly as I showed above
>
>
Yes and you can control it using Maven assembly as I showed above
https://github.com/gwtboot/domino-rest-enum-date/blob/master/domino-rest-enum-date-client/src/assembly/distribution.xml
You can add the CSS files to be added to the server module on deployment...
But again, of course you can use
yes, but in addition to the html file your also have the css files as
well..
On Sun, Oct 18, 2020 at 10:54 PM lofid...@gmail.com
wrote:
> Yes correct, HTML file is your host file.
>
> I always put a simple HTML file to be able to launch / debug gwt webapp on
> the client... see:
>
additionally ... in the case using the structure of gwt-maven-plugin also
correct.
There are two possibilities using *gwt:codeserver* (the case you said) or
*gwt:devmode* (my example) see the difference:
https://tbroyer.github.io/gwt-maven-plugin/codeserver.html
Both possible, I just prefer
Yes correct, HTML file is your host file.
I always put a simple HTML file to be able to launch / debug gwt webapp on
the client... see:
https://github.com/gwtboot/domino-rest-enum-date/blob/master/domino-rest-enum-date-client/src/main/java/com/example/public/index.html
But you don't have to
i missing something basic here with all the code server/dev mode/super dev
mode/launch dir/workdir/startup url/s
at the end of the day you have to have an html file to use, when you launch
for debug, but the gwt plugins are in the client module which doesn't have
the html file on one hand, but
Yes, but that's not a problem... in my example above I took out the html
file (
https://github.com/gwtboot/domino-rest-enum-date/blob/master/domino-rest-enum-date-client/src/assembly/distribution.xml)
so that I only packaged the JS files... and at the end I use the HTML files
from the server
but the webui-server contains all the static resources like the html page
On Sun, Oct 18, 2020 at 8:24 PM lofid...@gmail.com
wrote:
> --webui
> webui-client ---> this is the GWT code
> webui-server ---> this is server-side code like Servlet, Spring Boot,
> JavaEE servers
>
> This is the
--webui
webui-client ---> this is the GWT code
webui-server ---> this is server-side code like Servlet, Spring Boot,
JavaEE servers
This is the standard layout for maven-gwt-plugin so would be no problem at
all... and for the mod1 / mod2: as long as you do: install, the
webui-client
i did just that only it's more like
main_pom
--mod1
--mod2
--webui
webui-client
webui-server
--builder-mod that collects all jars from other modes into a directory for
final deploy and installation
what i wanna do is also be able to build only the webui project, and
possibility to use the
I cannot follow you, maybe you could write something like:
cockpit
-- cockpit-client-ui
-- cockpit-server
...
I'm not sure how the structure of your projects looks like?
Elhanan schrieb am Sonntag, 18. Oktober 2020 um 17:28:19 UTC+2:
> i'm assuming those 2 need to be in there own aggregator pom
i'm assuming those 2 need to be in there own aggregator pom (i.e my main
parent pom will a web ui pom, which will have those submodules) , because i
want to be able to build just that webproject alone without the need to
build the whole project again (this is because that in order to develop for
In my example I only use the gwt-maven-plugin for the "client" part (GWT
part). On the server part I use "pure" Spring Boot approach, therefore I
copied all the JS stuffs from the "client" part with the help of
maven-dependencies-plugin. I'm not using war deployment on Spring Boot...
For me
yes, i understand that gwt-maven-plugin is "opinionated" (i.e forces me to
do it) and i'm in the process of doing so, the thing is there's no "Server
part" it's meant to operate as a page under cockpit ui
On Sun, Oct 18, 2020 at 6:00 PM lofid...@gmail.com
wrote:
> Hmm it is not good to have
Hmm it is not good to have "server" part and "client" part (web browser,
GWT) in one Maven module... The best practice is always to separate them.
I wrote some simple explanation in this project:
https://github.com/gwtboot/domino-rest-enum-date with 3 Maven modules,
check the explanation over
i don't know, right now i'm having trouble to even compile everything, i
mean, i can either compile all the static files (html WEB-INF) into a war,
OR i can compile the gwt sources, depending on what i place in pom.xml
(gwt-app or war) i was trying to have it all in one module
On Sun, Oct 18,
Is it not possible to add those contents into an artifact with assembly for
example? So that you can use it later for the dependency? I'm doing this in
this example:
https://github.com/gwtboot/domino-rest-enum-date
Hope this helps.
Elhanan schrieb am Sonntag, 18. Oktober 2020 um 12:48:30 UTC+2:
hi..
i have a submodule of a gwt project that it's artifact are meant to be
included as part of the main artifact (which is a pom containing a debian
installer)
usually i would use copy-depdencies plugin to copy the jars into the main
artifact, but in this case there's no jar, is there a way i
30 matches
Mail list logo
