Hi all,
 
  
As far as I know you can use whatever version of java you want on packages under “org.eclipse.kapua.console.server.*” which is the code running on the server side of the webapp. 
  
You are only limited to java 6 on  packages  under “org.eclipse.kapua.console.client.*” and “org.eclipse.kapua.console.shared.*” because is the actual part that is translated
 to _javascript_.  
  
I think that we can leave things like they are now, so having Java 7 or 8 in “maven-compiler-plugin” configuration. 
If you do something that is not allowed in Java 6 you’ll get an error on GWT compilation. 
  
Regards, 
  
Alberto Codutti | R&D | EUROTECH | Timezone: CET (UTC +01:00) 
  
From: 
<kapua-dev-bounces@xxxxxxxxxxx> on behalf of Jens Reimann <jreimann@xxxxxxxxxx> 
Reply-To: kapua developer discussions <kapua-dev@xxxxxxxxxxx> 
Date: Thursday, April 20, 2017 at 1:56 PM 
To: kapua developer discussions <kapua-dev@xxxxxxxxxxx> 
Subject: Re: [kapua-dev] GWT 2.4 seems to require Java 6 
 
Actually downgrading Java wasn't such a big effort after all. 
 
I agree that upgrading sounds like a great idea at first. But this could turn out into some kind of effort. Especially with this version of GXT not being compatible with newer GWT versions. 
 
And AFAIK the web console based on GXT will be replace anyway, so I am not sure if we should put that much effort in an upgrade. 
 
We can still do that if there is interest in that. 
 
  
On Thu, Apr 20, 2017 at 1:51 PM, Abdelatif Bensari <abdelatif.bensari@xxxxxxxxx> wrote: 
Hello every one,  
  
Knowing that, I'm new in this, and do not have the all picture in my mind. 
 
I will suggest to move forward by upgrading. 
 
Of course I have no idea of the complexity or the downsides. 
 
 
 
  
I just figured out that GWT 2.4, which is used by the console, seems to actually required Java 6 instead of Java 7 which we currently have set. 
 
Downgrading to Java 6 would be possible, but would require to actually re-write a few of the try-with-resources blocks. 
 
I see the following options: 
 
1) Switch to Java 6 - re-write try-with-resources in Java 6 style 
 
2) Split up projects to have a GWT UI and GWT backend project (not sure this works out) 
 
3) Upgrade GWT 
 
Any ideas? 
 
Cheers 
 
Jens 
 
 
--  
Jens Reimann 
Senior Software Engineer / EMEA ENG Middleware 
Werner-von-Siemens-Ring 14 
85630 Grasbrunn 
Germany 
phone: +49 89 2050 71286 
_____________________________________________________________________________ 
 
Red Hat GmbH, www.de.redhat.com, 
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, 
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 
 
_______________________________________________ 
kapua-dev mailing list 
kapua-dev@xxxxxxxxxxx 
To change your delivery options, retrieve your password, or unsubscribe from this list, visit 
https://dev.eclipse.org/mailman/listinfo/kapua-dev 
 
 
 
 
 
--  
Ils bâtissent avec des pierres et ils ne voient pas que chacun de leurs gestes pour poser la pierre dans le mortier est accompagné d'une ombre de geste qui
 pose une ombre de pierre dans une ombre de mortier. Et c'est la bâtisse d'ombre qui compte.
 
 
 
 
 
_______________________________________________ 
kapua-dev mailing list 
kapua-dev@xxxxxxxxxxx 
To change your delivery options, retrieve your password, or unsubscribe from this list, visit 
https://dev.eclipse.org/mailman/listinfo/kapua-dev 
 
 
 
 
 
--  
Jens Reimann 
Senior Software Engineer / EMEA ENG Middleware 
Werner-von-Siemens-Ring 14 
85630 Grasbrunn 
Germany 
phone: +49 89 2050 71286 
_____________________________________________________________________________ 
 
Red Hat GmbH, www.de.redhat.com, 
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, 
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill 
 
 
 
 
 |