Re: GWT/Maven development cycle takes much too long

[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-lib-acs:jar:1.0-SNAPSHOT:compile]

...
Caused by: java.io.FileNotFoundException: 
/home/wagner/dvl/prj/msm/msm-lib-acs/target/classes (Is a directory)

 

I see two approaches then:


   - 
*solve the eclipse error without removing scope=provided *Does anyone have 
   an idea what may be causing the eclipse error? What file is not found? What 
   is the process behind this file access? Can you solve it by placing a dummy 
   file somewhere?
   
   - 
*using another maven plugin *As some of you may have noticed in another 
   thread, I was evaluating both, Mojo's and Thomas' eclipse plugin. Then, I 
   saw that I can live with the pom.xml created by webAppCreator, without 
   really caring about which plugin is used then.
   But I thought it was the "GWT way to go", since the pom was created by 
   webAppCreator, which is shipped with the GWT SDK.
   
   However, in this thread, Thomas said that the Mojo-Haus plugin doesn't 
   work in reactor builds. But I was unsure what I am actually using. When 
   looking into my pom.xml I see a plugin with groupId = net.ltgt.gwt.maven. 
   This seems to refer to Thomas' plugin. But in contrast, the error message 
   refers to "MojoExecutionException". Sorry, but I still cannot follow this. 
   Which plugin am I using? And if it's the "wrong" one, how can I switch in 
   my existing pom.xml?

There seem to exist people without those problems. I simply want to do it 
the same way.

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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 the Eclipse error.

-- J.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

[Manuel Carrasco Moñino]

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 other ways such as
direct usage of webcomponents directly from the Vaadin server side. And
even we explored in our labs how to use polymer in other platforms like
Angular, etc.

As I mentioned in my first email Vaadin main motivation on doing that is
leaving framework communities lead their integration with polymer, and
Vaadin Elements UI Team to focus on delivering polymer Components.

So the strategy of Vaadin is that our widgetset uses standards so as it can
be used in any platform including our Vaadin Framework. It is not happening
currently because our framework widgetset is only usable from vaadin, even
it cannot be used from GWT.

Said that, this does not mean that Vaadin is abandoning GWT, we just want
to use webcomponents standards for the UI part of the Vaadin Framework, so
as it can be used at the same time in any framework and we can obtain more
feedback to improve them. Obviously, since Vaadin is an open-source
Company, our polymer elements are Apache licensed.

Additionally, Vaadin indirectly support gwt-polymer-elements since we can
still use our Company time  aka 'Community Friday' to collaborate with the
project. But Vaadin thinks that it should be owned by the GWT community,
because they are the best to contribute with ideas and to feature it.

Thank you
- Manolo



On Sat, Apr 22, 2017 at 3:43 PM, Nándor Előd Fekete  wrote:

> 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:
>>
>> Hi all,
>>
>> From today, Vaadin has transferred the ownership of the
>> gwt-polymer-elements and gwt-api-generator libraries to me.
>>
>> https://github.com/manolo/gwt-polymer-elements/
>> https://github.com/manolo/gwt-api-generator/
>>
>> Vaadin decision is based on encouraging communities to maintain polymer
>> bridges for their favourites frameworks, hence Vaadin can focus their
>> efforts on delivering high quality UI elements made in Polymer. It also
>> happened recently with the Angular2Polymer bridge.
>>
>> I will design a roadmap for the next months.
>>
>> I'm looking for contributors so let me know who is interested on any
>> matter: coding, testing, reporting, answering, etc, and I will grant access
>> to the repos.
>>
>> Thanks
>> - Manolo
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 (= 
>>>   problem 1).
>>>   - If I keep it, the external libraries referenced by "my-lib" 
>>>   (like postgresql-40.0.0.jar) don't get copied into the WEB-INF/lib 
>>> folder 
>>>   of "my-app" (problem 2).
>>>
>>> So by changing scope=provided I can only choose between problem 1 and 
>>> problem 2.
>>>
>>>
>> Yep, between one correct build that doesn't import in Eclipse (because of 
>> Eclipse), or an "incorrect" build (from your requirements).
>>
>
> I am willing to learn, so my "requirements" may be wrong.
> What do you recommend for my situation?
>  
>
>> Now you said that problem 2 isn't a problem, because the external 
>>> libraries are provided at runtime, e. g. by Tomcat.
>>>
>>
>> No.
>> I'm saying you should *not* use scope=provided if that's not what you 
>> want (and it's not what you want, so don't use it), and find a solution (or 
>> workaround at least) for the Eclipse issue, 
>>
>
> I believe it's not an eclipse issue: I create a war file with "mvn 
> package" and this war file doesn't contain the necessaey libs.
> Tell me, where is my error in reasoning?
>
>  You should IMO focus on the Maven part and get it right; then make it 
> work in/with your IDE
>
> Well, we have passed some milestones in this thread (eclipse error, 
> scope=provided yes or no).
> But at the point we are now, it's nothing but a Maven issue:
> Creating a package with maven (mvn package) creates a package (war) with 
> missing jar files.
>
> To make a long story short:
>
>- Before Maven I created a war file with all necessary jar files in 
>WEB-INF/lib
>- With Maven this war file is actually missing those jar files.
>
> Please don't pay too much attention on my "requirements". They may be 
> wrong, since I don't know how it should be done the usual way...
>

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.
Then this causes an issue when importing the project in Eclipse, when 
resolving dependencies from the workspace; this is an Eclipse issue, Maven 
is fine.
Workarounds:

   - do not resolve dependencies from the workspace; but then you need to 
   "mvn install" your library and this has a huge impact on the developer 
   experience (the initial subject of this thread)
   - if the error does not prevent you from working on the project, then 
   ignore it.

But this is an Eclipse issue.
 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 by "my-lib" 
>>   (like postgresql-40.0.0.jar) don't get copied into the WEB-INF/lib 
>> folder 
>>   of "my-app" (problem 2).
>>
>> So by changing scope=provided I can only choose between problem 1 and 
>> problem 2.
>>
>>
> Yep, between one correct build that doesn't import in Eclipse (because of 
> Eclipse), or an "incorrect" build (from your requirements).
>

I am willing to learn, so my "requirements" may be wrong.
What do you recommend for my situation?
 

> Now you said that problem 2 isn't a problem, because the external 
>> libraries are provided at runtime, e. g. by Tomcat.
>>
>
> No.
> I'm saying you should *not* use scope=provided if that's not what you 
> want (and it's not what you want, so don't use it), and find a solution (or 
> workaround at least) for the Eclipse issue, 
>

I believe it's not an eclipse issue: I create a war file with "mvn package" 
and this war file doesn't contain the necessaey libs.
Tell me, where is my error in reasoning?

 You should IMO focus on the Maven part and get it right; then make it work 
in/with your IDE

Well, we have passed some milestones in this thread (eclipse error, 
scope=provided yes or no).
But at the point we are now, it's nothing but a Maven issue:
Creating a package with maven (mvn package) creates a package (war) with 
missing jar files.

To make a long story short:

   - Before Maven I created a war file with all necessary jar files in 
   WEB-INF/lib
   - With Maven this war file is actually missing those jar files.

Please don't pay too much attention on my "requirements". They may be 
wrong, since I don't know how it should be done the usual way...

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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

[Manuel Carrasco Moñino]

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 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 contribute in the best of my abilities: mainly
>> testing and reporting.
>>
>> Regards,
>> Harsh Yadav
>>
>> On Friday, April 21, 2017 at 3:10:06 PM UTC-4, Manuel Carrasco wrote:
>>>
>>> Hi all,
>>>
>>> From today, Vaadin has transferred the ownership of the
>>> gwt-polymer-elements and gwt-api-generator libraries to me.
>>>
>>> https://github.com/manolo/gwt-polymer-elements/
>>> https://github.com/manolo/gwt-api-generator/
>>>
>>> Vaadin decision is based on encouraging communities to maintain polymer
>>> bridges for their favourites frameworks, hence Vaadin can focus their
>>> efforts on delivering high quality UI elements made in Polymer. It also
>>> happened recently with the Angular2Polymer bridge.
>>>
>>> I will design a roadmap for the next months.
>>>
>>> I'm looking for contributors so let me know who is interested on any
>>> matter: coding, testing, reporting, answering, etc, and I will grant access
>>> to the repos.
>>>
>>> Thanks
>>> - Manolo
>>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Francesco Izzi
> CNR - IMAA
> geoSDI
> Direzione Tecnologie e Sviluppo
>
> C.da S. Loja
> 85050  Tito Scalo - POTENZA (PZ)
> Italia
>
> phone: +39 0971427310 <+39%200971%20427310>
> fax:   +39 0971 427271 <+39%200971%20427271>
> mob: +39 3666373172 <+39%20366%20637%203172>
> mail: francesco.i...@geosdi.org
> skype:  neofx8080
>
> web: http://www.geosdi.org
>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

[Manuel Carrasco Moñino]

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 polymer elements heavily and look forward for its future
> development.
> I would be happy to contribute in the best of my abilities: mainly testing
> and reporting.
>
> Regards,
> Harsh Yadav
>
> On Friday, April 21, 2017 at 3:10:06 PM UTC-4, Manuel Carrasco wrote:
>>
>> Hi all,
>>
>> From today, Vaadin has transferred the ownership of the
>> gwt-polymer-elements and gwt-api-generator libraries to me.
>>
>> https://github.com/manolo/gwt-polymer-elements/
>> https://github.com/manolo/gwt-api-generator/
>>
>> Vaadin decision is based on encouraging communities to maintain polymer
>> bridges for their favourites frameworks, hence Vaadin can focus their
>> efforts on delivering high quality UI elements made in Polymer. It also
>> happened recently with the Angular2Polymer bridge.
>>
>> I will design a roadmap for the next months.
>>
>> I'm looking for contributors so let me know who is interested on any
>> matter: coding, testing, reporting, answering, etc, and I will grant access
>> to the repos.
>>
>> Thanks
>> - Manolo
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 artifact" returns (= 
>   problem 1).
>   - If I keep it, the external libraries referenced by "my-lib" (like 
>   postgresql-40.0.0.jar) don't get copied into the WEB-INF/lib folder of 
>   "my-app" (problem 2).
>
> So by changing scope=provided I can only choose between problem 1 and 
> problem 2.
>
>
Yep, between one correct build that doesn't import in Eclipse (because of 
Eclipse), or an "incorrect" build (from your requirements).
 

> Now you said that problem 2 isn't a problem, because the external 
> libraries are provided at runtime, e. g. by Tomcat.
>

No.
I'm saying you should *not* use scope=provided if that's not what you want 
(and it's not what you want, so don't use it), and find a solution (or 
workaround at least) for the Eclipse issue, which is BTW unrelated to GWT I 
believe.
You should IMO focus on the Maven part and get it right; then make it work 
in/with your IDE (and fully understand –and document– the changes you'll 
possibly need to make to make it work).

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 libraries referenced by "my-lib" (like 
  postgresql-40.0.0.jar) don't get copied into the WEB-INF/lib folder of 
  "my-app" (problem 2).
   
So by changing scope=provided I can only choose between problem 1 and 
problem 2.


Now you said that problem 2 isn't a problem, because the external libraries 
are provided at runtime, e. g. by Tomcat.
Let's focus this point.

I am running my own Tomcat and when I deploy a WAR file, I don't want to 
care about the external libraries it needs.
Before Maven, there was no need for this, because the external libs were 
included in WEB-INF/lib.

Now - with Maven - I shall care about the libs a WAR file needs a *second 
time*?
I already have specified all the dependencies in the pom.xml of my-lib.

Why not include all the needed jar fiiles in WEB-INF/lib and have one WAR 
file that can be deployed as its own?

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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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=provided.
What scope=provided says is exactly what you see is happening: please don't 
put those things into the WAR as they will be provided at runtime (put into 
Tomcat's "common" libraries, Jetty's lib/ext or extraClasspath, or anything 
equivalent in other servlet containers).

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

[Nándor Előd Fekete]

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:
>
> Hi all,
>
> From today, Vaadin has transferred the ownership of the 
> gwt-polymer-elements and gwt-api-generator libraries to me.
>
> https://github.com/manolo/gwt-polymer-elements/
> https://github.com/manolo/gwt-api-generator/
>
> Vaadin decision is based on encouraging communities to maintain polymer 
> bridges for their favourites frameworks, hence Vaadin can focus their 
> efforts on delivering high quality UI elements made in Polymer. It also 
> happened recently with the Angular2Polymer bridge.
>
> I will design a roadmap for the next months.
>
> I'm looking for contributors so let me know who is interested on any 
> matter: coding, testing, reporting, answering, etc, and I will grant access 
> to the repos.
>
> Thanks
> - Manolo
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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=provided, is completely outside eclipse:
When I "mvn package" my app, the postgresql lib is not copied into the lib 
folder.

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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 WAR (and transitive 
> dependencies as well, of course).
> And because the error you're having specifically happens when trying to 
> copy the JAR into the WEB-INF/lib, if you say that this should no longer 
> happen (by using scope=provided), then the error goes away.
>  
>
>> Maybe another scope is better?
>>
>
> No.
> The problem is that Eclipse wants to package your app.
>

This problem is outside eclipse. When I "mvn package" the app it results in 
missing libs in the WEB-INF/lib folder.
How can I solve that?

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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

add google app engine sdk to gwt 2.8 project

[Gal Lavie]

 

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 form this site 
http://gwt-plugins.github.io/documentation/gwt-eclipse-plugin/Download.html i 
removed the google app engine sdk because eclipse said me to remove it. i 
copied all packages from old project to new project. but i have errors 
because i removed google app engine sdk. I installed Google cloud paltform 
and i can create new project in google app engine but i cant add sdk to gwt 
project. how i can connect between google app engine and gwt 2.8 and deploy 
the project to google

in my code i get error like this "The import javax.jdo cannot be resolved 
for this line"

import javax.jdo.annotations.IdGeneratorStrategy;

I'm really lost all the week i work on upgrade my project to new gwt 2.8 
thank you

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 again.
> Now I can enable dependency resolution in eclipse again.
>
> So far so good. But I also remember why I removed the provided scope.
> Juan recommended this in another thread 
>  
> as a solution to another problem:
>
> My app uses my lib (msm.lib.acs above), and my lib uses common libs from 
> the maven repository, e. g. postgresql-42.0.0.jar.
> The problem was that those libs were not copied into the application's 
> WEB-INF/lib folder. So I ended up in missing jars.
>
> 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!
>
> So I made one step backward, dependency resolution is enabled again, but 
> the external jars are missing in the app folder.
>

This is expected: scope=provided means "this will be provided by 'the 
environment'" so it's not packaged inside the WAR (and transitive 
dependencies as well, of course).
And because the error you're having specifically happens when trying to 
copy the JAR into the WEB-INF/lib, if you say that this should no longer 
happen (by using scope=provided), then the error goes away.
 

> Maybe another scope is better?
>

No.
The problem is that Eclipse wants to package your app.
As hinted in my other message, maybe this has been worked around in more 
recent versions of the maven-war-plugin (though I still believe the problem 
is with Eclipse and trying to package the app on project import) 

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 also remember why I removed the provided scope.
Juan recommended this in another thread 
 
as a solution to another problem:

My app uses my lib (msm.lib.acs above), and my lib uses common libs from 
the maven repository, e. g. postgresql-42.0.0.jar.
The problem was that those libs were not copied into the application's 
WEB-INF/lib folder. So I ended up in missing jars.

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!

So I made one step backward, dependency resolution is enabled again, but 
the external jars are missing in the app folder.
Maybe another scope is better?

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 email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT/Maven development cycle takes much too long

[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 (configure warDir/launcherDir, possibly projects/modules)
>>
>
> Actually, it gives an error (see below):
>
> Could not find goal 'devmode' in plugin 
> org.codehaus.mojo:gwt-maven-plugin:2.8.0 among available goals...
>
>
> I believe I have to extend the minimal top-level pom.xml, but how?
> And I'd like to leave the pom.xml in the sub folders as is, because they 
> are working for their own... Is this possible?
>

As I said, the MojoHaus plugin doesn't work well in reactor builds, it 
simply hasn't been designed to support them.
The net.ltgt.gwt.maven:gwt-maven-plugin (where the devmode and codeserver 
goals can be found) has been specifically designed for that.
You can probably mix both plugins (i.e. keep the MojoHaus plugin in the 
submodules for the build, use the net.ltgt.gwt.maven plugin in the root 
module only for the devmode/codeserver goals) with a bit more configuration 
(explicit projects and modules, rather than automatic discovery in 
submodules).
 

>  
>
>> This is also the point with the development cycle: When debugging, 
>>> eclipse doesn't "see" the changed library source code, because it fetches 
>>> the library source code from the jar file in its own target folder.
>>>
>>
>> Actually the one from your local repository (~/.m2/repository/), not 
>> directly the one from the target/ folder.
>>
>
> This is an important point! If the app used the library jar from the 
> repository and not from its own target directory, there would be no need to 
> "mvn package" the app and this takes most of the time...
>  
>
>> Wouldn't it be better for developing if the original library code was 
>>> used instead? Could it be that this is the core of the problem?
>>>
>>
>>  
>
>> And the problem is that Eclipse errors when importing your app project 
>> when using the default configuration for resolving dependencies from the 
>> workspace; which is why you turned that setting off.
>> If you figure out how to get this working, then it should (hopefully 
>> work) the same with or without a reactor.
>>
>
> I can enable it for the lib project without problems. But as soon as I 
> enable it for the app project, the error reappears.
> It's hard to figure it out when even the experts in this group have no 
> idea. But I see that this is an essential point, so I have documented the 
> error as detailed as possible again (see below). I hope there will be a 
> solution...
>

It really doesn't look like this is specific to GWT; so if I were you I'd 
ask on the M2Eclipse mailing list (if any) and/or on StackOverflow. You (a 
priori) need to find Eclipse/M2Eclipse experts, not GWT experts that 
(possibly) happen to use Eclipse/M2Eclipse. It looks really strange to me 
that Eclipse attemps to package the project on import, and this is the crux 
of the problem (it is the maven-war-plugin that's failing).
It would probably help to know the exact version of Eclipse (and M2Eclipse, 
WTP, and m2e-wtp plugins) you're using, and any other plugin you have 
installed that could trigger that behavior (reproducing in an 
out-of-the-box Eclipse install would allow excluding bad plugin 
interactions).
Having a small (as small as possible, just a jar and war projects, no 
external dependencies besides javax.servlet) project available (e.g. on 
GitHub) would also help, so that others could try to reproduce the problem 
from the same sources.

(also, maven-war-plugin 2.2 is 5 years old already, maybe try using a more 
recent version? if you don't explicitly specify a version, try a newer 
Maven version; though the one Eclipse uses is likely the one it bundles, so 
it depends directly on the version of the M2Eclipse plugin being used)

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWT Polymer

[Francesco Izzi]

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 contribute in the best of my abilities: mainly testing
> and reporting.
>
> Regards,
> Harsh Yadav
>
> On Friday, April 21, 2017 at 3:10:06 PM UTC-4, Manuel Carrasco wrote:
>>
>> Hi all,
>>
>> From today, Vaadin has transferred the ownership of the
>> gwt-polymer-elements and gwt-api-generator libraries to me.
>>
>> https://github.com/manolo/gwt-polymer-elements/
>> https://github.com/manolo/gwt-api-generator/
>>
>> Vaadin decision is based on encouraging communities to maintain polymer
>> bridges for their favourites frameworks, hence Vaadin can focus their
>> efforts on delivering high quality UI elements made in Polymer. It also
>> happened recently with the Angular2Polymer bridge.
>>
>> I will design a roadmap for the next months.
>>
>> I'm looking for contributors so let me know who is interested on any
>> matter: coding, testing, reporting, answering, etc, and I will grant access
>> to the repos.
>>
>> Thanks
>> - Manolo
>>
> --
> 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+unsubscr...@googlegroups.com.
> To post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Francesco Izzi
CNR - IMAA
geoSDI
Direzione Tecnologie e Sviluppo

C.da S. Loja
85050  Tito Scalo - POTENZA (PZ)
Italia

phone: +39 0971427310
fax:   +39 0971 427271
mob: +39 3666373172
mail: francesco.i...@geosdi.org
skype:  neofx8080

web: http://www.geosdi.org

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.