--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 (gwt codeserver) will recognize the "source code" and could also transpile the code on the fly... (at least the last time I check it out)...
If you want to completely separate everything you could go for:
--modules
----mod1
----mod2
--webui
----webui-client
----webui-server
--builder-modules
Elhanan schrieb am Sonntag, 18. Oktober 2020 um 19:06:45 UTC+2:
i did just that only it's more likemain_pom--mod1--mod2--webui----webui-client----webui-server--builder-mod that collects all jars from other modes into a directory for final deploy and installationwhat i wanna do is also be able to build only the webui project, and possibility to use the codeserver option which i don't think i can now because they are all split in 3 modulesI 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.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 cockpit i can't use any of the rapid inplace server development, but compile the while thing and copy the distro to a linux server running the cockpit server)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 the main concept: From GWT project you get just JS file(s) and you can copy it somewhere else where you have a web server. I also already use "only" the JS file(s) and copy the automatically to NGinX without server part.--Elhanan schrieb am Sonntag, 18. Oktober 2020 um 17:03:21 UTC+2: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 uiHmm 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 there...--Elhanan schrieb am Sonntag, 18. Oktober 2020 um 16:55:35 UTC+2: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 moduleIs 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:
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 can copy the output directory of that submodule into the main artifact?--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/42DICj36J0E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/38ff23af-b3d7-4aef-80e8-9451486aa641n%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/42DICj36J0E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/b426f9bc-5962-4cc4-888a-895a1cd71d42n%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/42DICj36J0E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/cf8187c9-d562-4d21-92ad-272ff71507d4n%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/42DICj36J0E/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-tool...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/76b5972a-2e46-404a-a17d-29195093514an%40googlegroups.com.
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 it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/15e62e34-87a3-4df8-b539-cd4311ef462dn%40googlegroups.com.
No comments:
Post a Comment