Re: GWT/Maven development cycle takes much too long

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

Re: GWT/Maven development cycle takes much too long

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

Re: GWT/Maven development cycle takes much too long

> > 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

Re: GWT Polymer

You are right Nándor, Vaadin is going to replace our current widgetset by polymer based elements. One of the ways we explored in our labs is to wrap every single polymer element with a GWT Widget or Element, and this is the reason we published the gwt-polymer-elements. Additionally we explored

Re: GWT/Maven development cycle takes much too long

> > 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 --

Re: GWT/Maven development cycle takes much too long

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 (= >>>

Re: GWT/Maven development cycle takes much too long

> > 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 Polymer

Francesco, add a comment to this issue https://github.com/manolo/gwt- polymer-elements/issues/151 Thank you - Manolo On Sat, Apr 22, 2017 at 10:47 AM, Francesco Izzi wrote: > Ciao Manuel > > I would be happy to contribute in testing and reporting. > > Thanks > Il

Re: GWT Polymer

Thank Harsh, add a comment to this issue https://github.com/manolo/gwt- polymer-elements/issues/151, so as I know your github account and will add as a contributor - Manolo On Sat, Apr 22, 2017 at 12:43 AM, harshyadav wrote: > Thanks a lot Manuel. > > We use gwt

Re: GWT/Maven development cycle takes much too long

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

Re: GWT/Maven development cycle takes much too long

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

Re: GWT/Maven development cycle takes much too long

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

Re: GWT Polymer

Hello Manuel, wasn't Vaadin going into the direction of migrating it's client side components to web components in the Vaadin Framework itself? If not, can you shed some light on the motivation behind the decision? Thanks! On Friday, April 21, 2017 at 9:10:06 PM UTC+2, Manuel Carrasco wrote:

Re: GWT/Maven development cycle takes much too long

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

Re: GWT/Maven development cycle takes much too long

> 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

add google app engine sdk to gwt 2.8 project

I develop gwt project until now i used with google app engine and gwt 2.7 and everything is ok but i want to upgrade to gwt 2.8 and i can not. this is what i did until now i remove the google app engine sdk and installed the gwt plugin 3 include gwt 2.7 and gwt 2.8 and javascript debugger

Re: GWT/Maven development cycle takes much too long

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

Re: GWT/Maven development cycle takes much too long

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

Re: GWT/Maven development cycle takes much too long

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

Re: GWT Polymer

Ciao Manuel I would be happy to contribute in testing and reporting. Thanks Il giorno sab 22 apr 2017 alle 00:43 harshyadav ha scritto: > Thanks a lot Manuel. > > We use gwt polymer elements heavily and look forward for its future > development. > I would be happy to