Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Thomas Broyer
You need to "rebuild" the webapp when you make changes to it (but not recompile the GWT app), so "mvn package -Dgwt.compiler.skip"; then "reload web server". -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop r

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Vassilis Virvilis
Not so sure. I can refactor across projects in eclipse... On Mon, Apr 24, 2017 at 8:00 PM, Magnus wrote: > However, now that the error disappeared, I'll come back to the original >>> question and see how it speeds up the development process. >>> >> >> Now that you can have "resolve dependencies

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Magnus
> > However, now that the error disappeared, I'll come back to the original >> question and see how it speeds up the development process. >> > > Now that you can have "resolve dependencies from the workspace" enabled in > Eclipse, the GWT Eclipse Plugin should automatically configure the launch

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Thomas Broyer
On Monday, April 24, 2017 at 5:30:14 PM UTC+2, Magnus wrote: > > Friends, > > it seems as if I could solve the problem by adding this to the pom.xml: > > >org.apache.maven.plugins >maven-war-plugin >2.6 > > > As you can see in the error message, version 2.2.

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Jens
> I am happy to have a solution, but I wonder what was going on. Why istn't > the newest plugin used by default? I have seen that there already is a > version 3.0.0 of the plugin. > Should I hardcode the version in the pom.xml? > To get a reproducible build the version of all your dependencies

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Magnus
Friends, it seems as if I could solve the problem by adding this to the pom.xml: org.apache.maven.plugins maven-war-plugin 2.6 As you can see in the error message, version 2.2. is used by default. By changing it to 2.6 the error disappeared! I am happy to hav

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Ignacio Baca Moreno-Torres
But please, use the tbroyer plugin, it's much better, makes no sense start a new project using the old one. I also think that using maven makes a pretty reasonable development lifecycle, I just use the IDE to run the maven goals, works perfectly, much easier to configure and get it work. The tbroye

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Pavlo Iatsiuk
Magnus, if you still have a problem to run it - I can create a small "hello world" to show you how to do that with maven -- 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 ema

Re: GWT/Maven development cycle takes much too long

2017-04-24 Thread Pavlo Iatsiuk
Yes, I do everything from command line with maven to run war file - mvn jetty:run-war -Djetty.port=8095 -DskipTests=true to run code server - mvn gwt:run-codeserver gwt maven plugin settings org.codehaus.mojo gwt-maven-plugin ${VERSION.GWT} MyPage.html

Re: GWT/Maven development cycle takes much too long

2017-04-23 Thread Ignacio Baca Moreno-Torres
If you want to do it the same way just use the modular webapp-archetype ( https://github.com/tbroyer/gwt-maven-archetypes/blob/master/README.md) 😬👍 videos here (GWT Eclipse Plugin V3: https://www.youtube.com/playlist?list=PLBbgqtDgdc_TqzA-qXrjgTFMC_6DKAQyT). Please, watch all the videos! 😉 El dom.

Re: GWT/Maven development cycle takes much too long

2017-04-23 Thread Thomas Broyer
On Sunday, April 23, 2017 at 2:17:04 AM UTC+2, Magnus wrote: > > Hello Jens, > > I'm beginning to realize that removing scope=provided isn't a solution to > the eclipse problem. > Sorry that this took so long... > > However, then let's come back to the eclipse error again: > > org.apache.maven.p

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
Hello Jens, I'm beginning to realize that removing scope=provided isn't a solution to the eclipse problem. Sorry that this took so long... However, then let's come back to the eclipse error again: org.apache.maven.plugin.MojoExecutionException: Failed to copy file for artifact [msm.lib.acs:msm

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
You mean that removing scope=provided isn't really a solution to the eclipse problem? What would you do in this case? Magnus -- 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

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Jens
> > Ok, but how can I have the JARs into the WAR then? > If this is what most other people want, then there must be a solution... > As Thomas said, once you DO NOT use provided = true your library and all its required dependencies will end up in your WAR file. You just have to solve or ignore t

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
> > Your requirements is to have the JARs into the WAR (just like most other > people, so your requirements aren't wrong), so DO NOT use scope=provided. > Ok, but how can I have the JARs into the WAR then? If this is what most other people want, then there must be a solution... Magnus -- You

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Thomas Broyer
On Saturday, April 22, 2017 at 6:03:47 PM UTC+2, Magnus wrote: > > The question scope=provided or not affects the dependency for my own >>> library "my-lib" in the pom.xml of my application "my-app". >>> >>> >>>- If I remove it, the "Failed to copy file for artifact" returns (= >>> pr

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
> > The question scope=provided or not affects the dependency for my own >> library "my-lib" in the pom.xml of my application "my-app". >> >> >>- If I remove it, the "Failed to copy file for artifact" returns (= >> problem 1). >> - If I keep it, the external libraries referenced

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Thomas Broyer
On Saturday, April 22, 2017 at 5:06:00 PM UTC+2, Magnus wrote: > > There may be some misunderstandings: > > The question scope=provided or not affects the dependency for my own > library "my-lib" in the pom.xml of my application "my-app". > > >- If I remove it, the "Failed to copy file for a

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
There may be some misunderstandings: The question scope=provided or not affects the dependency for my own library "my-lib" in the pom.xml of my application "my-app". - If I remove it, the "Failed to copy file for artifact" returns (= problem 1). - If I keep it, the external libr

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Thomas Broyer
On Saturday, April 22, 2017 at 1:43:33 PM UTC+2, Magnus wrote: > > The external libs (like postgresql-40.0.0.jar) must be copied into the > WEB-INF/lib directory. When scope=provided, it isn't copied there. That was > the problem in the other thread. > How can I solve this? > Don't use scope=p

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
The external libs (like postgresql-40.0.0.jar) must be copied into the WEB-INF/lib directory. When scope=provided, it isn't copied there. That was the problem in the other thread. How can I solve this? Note that this other problem from the other thread, where the "solution" was to remove scope=

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
> And unfortunately this problem now reappeared. When I build the app with >> "mvn package", I end ab with a WEB-INF/lib folder not containing the >> external libs! >> > > This is expected: scope=provided means "this will be provided by 'the > environment'" so it's not packaged inside the

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Thomas Broyer
On Saturday, April 22, 2017 at 12:29:26 PM UTC+2, Magnus wrote: > > Hello, > > I found it! > The error is caused by the following dependency: > > > msm.lib.acs > msm-lib-acs > 1.0-SNAPSHOT > > > > The error immediately disappears when I set the scope to provided

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Magnus
Hello, I found it! The error is caused by the following dependency: msm.lib.acs msm-lib-acs 1.0-SNAPSHOT The error immediately disappears when I set the scope to provided again. Now I can enable dependency resolution in eclipse again. So far so good. But I als

Re: GWT/Maven development cycle takes much too long

2017-04-22 Thread Thomas Broyer
On Friday, April 21, 2017 at 7:38:37 PM UTC+2, Magnus wrote: > > >>> So, "mvn package" should Just Work™ (package the lib, then package the >> app using the lib's jar). >> > > Yes, works! > > >> "mvn gwt:devmode" and "mvn gwt:codeserver" should work without too much >> configuration (configur

Re: GWT/Maven development cycle takes much too long

2017-04-21 Thread Juan Pablo Gardella
I suggest to make a POC using https://github.com/tbroyer/gwt-maven-archetypes/ archetype, using modular-webapp. On Fri, 21 Apr 2017 at 14:38 Magnus wrote: > >>> So, "mvn package" should Just Work™ (package the lib, then package the >> app using the lib's jar). >> > > Yes, works! > > >> "mvn gwt:

Re: GWT/Maven development cycle takes much too long

2017-04-21 Thread Magnus
> > >> So, "mvn package" should Just Work™ (package the lib, then package the > app using the lib's jar). > Yes, works! > "mvn gwt:devmode" and "mvn gwt:codeserver" should work without too much > configuration (configure warDir/launcherDir, possibly projects/modules) > Actually, it gives an

Re: GWT/Maven development cycle takes much too long

2017-04-21 Thread Thomas Broyer
On Friday, April 21, 2017 at 5:58:58 PM UTC+2, Magnus wrote: > > Hi Thomas, > > I already have started to play with a reactor. Below is my top-level > pom.xml. But where to go from here? > What are the mvn commands to build everything on the top-level? If "mvn > install" isn't needed anymore, h

Re: GWT/Maven development cycle takes much too long

2017-04-21 Thread Magnus
Hi Thomas, I already have started to play with a reactor. Below is my top-level pom.xml. But where to go from here? What are the mvn commands to build everything on the top-level? If "mvn install" isn't needed anymore, how does the app project see the library? This is also the point with the de

Re: GWT/Maven development cycle takes much too long

2017-04-20 Thread Thomas Broyer
On Tuesday, April 18, 2017 at 6:03:29 PM UTC+2, Magnus wrote: > > Hello, > > after moving my projects to Maven, I am at a point where everything works > again, with the help of the people in this group. > However, when concentrating on the actual work again, I notice that the > development cycl

Re: GWT/Maven development cycle takes much too long

2017-04-20 Thread Magnus
Hi Pavlo! I have similar projects structure and do next: > - start my-app and code server for my-app. In my case I use jetty maven > plugin to start application and gwt plugin to start code server > - do your changes in my-lib and mvn install after that. It should be very > fast because there

Re: GWT/Maven development cycle takes much too long

2017-04-19 Thread Frank
I use the GWT Eclipse plugin from Brandon Donnelson (not the one from Google) for launching SuperDev. I have about 10 seperate library projects and I can make changes in those without and just refresh the browser and just wait about 3 seconds to see the changes. https://github.com/gwt-plugins/g

Re: GWT/Maven development cycle takes much too long

2017-04-19 Thread Kirill Prazdnikov
> > You did not address the special problem with the two maven projects: > Yes, sorry about that I'm not maven expert, I don`t know details. We use IDEA to start superdevmode and use maven modules list in parent pom so that there is no need to mvn-install all the modules and IDEA maven plugin

Re: GWT/Maven development cycle takes much too long

2017-04-19 Thread Pavlo Iatsiuk
Hello, I have similar projects structure and do next: - start my-app and code server for my-app. In my case I use jetty maven plugin to start application and gwt plugin to start code server - do your changes in my-lib and mvn install after that. It should be very fast because there is just pla

Re: GWT/Maven development cycle takes much too long

2017-04-18 Thread Boris Brudnoy
On Tue, Apr 18, 2017 at 12:03 PM Magnus wrote: > Hello, > > after moving my projects to Maven, I am at a point where everything works > again, with the help of the people in this group. > However, when concentrating on the actual work again, I notice that the > development cycle I have started wi

Re: GWT/Maven development cycle takes much too long

2017-04-18 Thread Magnus
Hello Kirill, thank you for your recommendations. I will remove all permutations as you said and see how it improves work. But I believe that the real cause of the problem is another one: You did not address the special problem with the two maven projects: Debug the app, then see a problem in th

GWT/Maven development cycle takes much too long

2017-04-18 Thread Kirill Prazdnikov
First of all I recommend remove all permutations. This is very easy, add this to module.gwt.xml: This will use the only perm for all browsers. That are not needed actually. Then you can omit GWT compilation at all before you are going to start super-dev-mode because codeserver itself will also

GWT/Maven development cycle takes much too long

2017-04-18 Thread Magnus
Hello, after moving my projects to Maven, I am at a point where everything works again, with the help of the people in this group. However, when concentrating on the actual work again, I notice that the development cycle I have started with takes too long, so that I cannot be productive in any