Re: Project moved now compile errors

2023-09-13 Thread eliasbala...@gmail.com 
I think you have stumbled upon a known issue.

Class "com.smartgwt.client.data.Record" conflicts with "Record" in more 
recent versions of Java

see 
https://forums.smartclient.com/forum/smart-gwt-technical-q-a/270433-smartgwt-6-1-is-incompatible-with-java17

I hope this has been fixed in later versions of SmartGWT.
We will find out as soon as we try to switch to Java17.

I hope this helps you.

On Wednesday, 13 September 2023 at 15:03:26 UTC+1 Frank Hossfeld wrote:

Might be a problem with the jdk version ... 
IIRC, record was added in Java 14 (not sure). It looks like a jdk version > 
13 is used to build. 
Not sure if SmartGWT is supporting newer jdk version than version 8.

Next problem might be Eclipse itself. Newer Eclipse version need something 
greater than Java 8.

Hope that helps. 
 

blackh...@gmail.com schrieb am Mittwoch, 13. September 2023 um 08:58:57 
UTC+2:

Hi,

We have a so called build server, where we build all our projects. This is 
just a server where eclipse is running and where we build our projects with 
ant.

As the server was/is getting old (windows 2008R2), we have set up a new one 
(windows 2022). We installed eclipse with the same configuration as on the 
old server. Same Java versions installed too.
We checked out the projects and now 1 of the projects does not compile the 
web stuff.
The other projects do build normal.

I have attached the compile log. Can anyone explain what is happening and 
what i am missing to fix this?

Regards,

Jasper

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/c81bd859-305a-4afc-9af6-56cbad17127en%40googlegroups.com.

Re: GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2023-01-06 Thread eliasbala...@gmail.com 
Many thanks, this is great.

I was planning to wait for the official release, but since you are that 
much satisfied I will give it a try.

On Friday, 6 January 2023 at 12:17:28 UTC abhiy...@gmail.com wrote:

> Hi All
>
> You can use the GWT eclipse plugin which is made compatible with latest 
> version of eclipse 4.26(2022-12) by someone from the GWT community. I am 
> providing the link below.
>
> *http://keeitsi.com/software/eclipse-plugins/ 
> *
> I am using this plugin and it works perfectly fine on the latest version 
> of eclipse.
>
> On Friday, January 6, 2023 at 5:30:49 PM UTC+5:30 eliasb...@gmail.com 
> wrote:
>
>> I believe I was using the GWT Eclipse Plugin content from Eclipse 
>> Marketplace which does not exist anymore.
>>
>> The alterrnatives 
>> http://storage.googleapis.com/gwt-eclipse-plugin/v3/release and 
>> http://storage.googleapis.com/gwt-eclipse-plugin/v3/snapshot work only 
>> up to Eclipse 2021-09
>>
>> On Friday, 24 June 2022 at 16:13:44 UTC+1 mtil...@gmail.com wrote:
>>
>>> Any clue about how you got it to work? It still don't work for me on 
>>> 2022-03. It installs but does not really add anything. On 2022-06 it 
>>> refuses to install.
>>>
>>>
>>> On Tuesday, 24 May 2022 at 09:08:45 UTC+2 eliasb...@gmail.com wrote:
>>>
 This seems to be working finally.

 To my surprise, I repeated the experiment and [GWT Eclipse Plugin] is 
 fully accessible and operational.

 I am now confused.

 On Monday, 23 May 2022 at 23:37:41 UTC+1 hprc wrote:

>
> I also use the GWT Eclipse Plugin.
> Currently, the Eclipse side is up to 202103, and seems to be up to 
> JDK1.8.
>
> The official documentation still only describes this plugin, so I'd 
> like you to add a method with the Moven plugin as soon as possible.
> (Preferably with illustrations)
> 2022年5月24日火曜日 6:57:01 UTC+9 eliasb...@gmail.com:
>
>> [GWT Eclipse Plugin] has served us very well.
>>
>> It is quite unfortunate but I fear the time for putting it to rest is 
>> approaching, if it hasn't already come.
>>
>> I just don't want to give up yet :-)
>>
>> On Monday, 23 May 2022 at 03:46:42 UTC+1 hprc wrote:
>>
>>>
>>> It's certainly interesting.
>>> However, do you recognize that the development of [GWT Eclipse 
>>> Plugin] will not be continued anymore?
>>> 2022年5月22日日曜日 18:16:34 UTC+9 eliasb...@gmail.com:
>>>
 Interesting...

 But you are using STS distribution not the standard, perhaps 
 something is different in the STS distribution compared to the primary 
 Eclipse Foundation's distribution.

 On Saturday, 14 May 2022 at 19:09:32 UTC+1 foal wrote:

> I am on Eclipse 4.22 (STS 4.13.1) and plugin still works (
> https://github.com/gwt-plugins/gwt-eclipse-plugin) 
>
> On Wednesday, May 4, 2022 at 12:56:47 AM UTC+2 Craig Mitchell 
> wrote:
>
>> I'm on Eclipse 2021-09 (4.21.0) and it works fine.
>>
>> However, after this version, the Google plugin stops working  
>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659
>>   
>> so I haven't tried later versions.
>>
>> On Monday, 2 May 2022 at 11:17:23 pm UTC+10 eliasb...@gmail.com 
>> wrote:
>>
>>> Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still 
>>> working.
>>>
>>> Under Eclipse 2022-03, the preferences page, the GWT Development 
>>> view and the run configurations are not accessible.
>>>
>>> This is crucial for certain teams relying on GWT Eclipse Plugin 
>>> for running applications from within the Eclipse IDE and locks 
>>> users to 
>>> Eclipse 2021-03 permanently, unless this can be fixed.
>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/288451ca-2ad2-4090-be99-21265bdd8facn%40googlegroups.com.

Re: GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2023-01-06 Thread eliasbala...@gmail.com 
I believe I was using the GWT Eclipse Plugin content from Eclipse 
Marketplace which does not exist anymore.

The 
alterrnatives http://storage.googleapis.com/gwt-eclipse-plugin/v3/release 
and http://storage.googleapis.com/gwt-eclipse-plugin/v3/snapshot work only 
up to Eclipse 2021-09

On Friday, 24 June 2022 at 16:13:44 UTC+1 mtils...@gmail.com wrote:

> Any clue about how you got it to work? It still don't work for me on 
> 2022-03. It installs but does not really add anything. On 2022-06 it 
> refuses to install.
>
>
> On Tuesday, 24 May 2022 at 09:08:45 UTC+2 eliasb...@gmail.com wrote:
>
>> This seems to be working finally.
>>
>> To my surprise, I repeated the experiment and [GWT Eclipse Plugin] is 
>> fully accessible and operational.
>>
>> I am now confused.
>>
>> On Monday, 23 May 2022 at 23:37:41 UTC+1 hprc wrote:
>>
>>>
>>> I also use the GWT Eclipse Plugin.
>>> Currently, the Eclipse side is up to 202103, and seems to be up to 
>>> JDK1.8.
>>>
>>> The official documentation still only describes this plugin, so I'd like 
>>> you to add a method with the Moven plugin as soon as possible.
>>> (Preferably with illustrations)
>>> 2022年5月24日火曜日 6:57:01 UTC+9 eliasb...@gmail.com:
>>>
 [GWT Eclipse Plugin] has served us very well.

 It is quite unfortunate but I fear the time for putting it to rest is 
 approaching, if it hasn't already come.

 I just don't want to give up yet :-)

 On Monday, 23 May 2022 at 03:46:42 UTC+1 hprc wrote:

>
> It's certainly interesting.
> However, do you recognize that the development of [GWT Eclipse Plugin] 
> will not be continued anymore?
> 2022年5月22日日曜日 18:16:34 UTC+9 eliasb...@gmail.com:
>
>> Interesting...
>>
>> But you are using STS distribution not the standard, perhaps 
>> something is different in the STS distribution compared to the primary 
>> Eclipse Foundation's distribution.
>>
>> On Saturday, 14 May 2022 at 19:09:32 UTC+1 foal wrote:
>>
>>> I am on Eclipse 4.22 (STS 4.13.1) and plugin still works (
>>> https://github.com/gwt-plugins/gwt-eclipse-plugin) 
>>>
>>> On Wednesday, May 4, 2022 at 12:56:47 AM UTC+2 Craig Mitchell wrote:
>>>
 I'm on Eclipse 2021-09 (4.21.0) and it works fine.

 However, after this version, the Google plugin stops working  
 https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659
   
 so I haven't tried later versions.

 On Monday, 2 May 2022 at 11:17:23 pm UTC+10 eliasb...@gmail.com 
 wrote:

> Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still 
> working.
>
> Under Eclipse 2022-03, the preferences page, the GWT Development 
> view and the run configurations are not accessible.
>
> This is crucial for certain teams relying on GWT Eclipse Plugin 
> for running applications from within the Eclipse IDE and locks users 
> to 
> Eclipse 2021-03 permanently, unless this can be fixed.
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/9a569dd7-c357-4914-9ee2-d9c7723381a9n%40googlegroups.com.

Re: java.lang.ClassNotFoundException: javax.sql.DataSource when using GWT 2.9.0 + Java 11 combination

2022-12-20 Thread eliasbala...@gmail.com 
I take back what I said.

It seems there are classpath resolution issues when using a custom 
"JettyLauncher" while running under "GWT Eclipse Plugin", probably due to 
different classloaders assignment.

I am afraid the time has finally come to abandon use of DevMode and the 
"GWt Eclipse Plugin", until this is fixed in later versions of GWT.

I hope a future version of GWT will make use of a Jetty version supporting 
a more elegant way to override the "allowedFromSystemClassLoader" variable.

On Monday, 19 December 2022 at 15:46:31 UTC eliasbala...@gmail.com wrote:

> Overriding JettyLauncher with  "javax.sql." on the 
> "allowedFromSystemClassLoader" variable has worked for me on a variety of 
> projects, using SuperDevMode + GWT 2.9.0 + JDK 11
>
> I hope a future version of GWT will make use of a Jetty version supporting 
> a more elegant way to override the "allowedFromSystemClassLoader" variable.
>
> On Friday, 1 July 2022 at 20:32:18 UTC+1 nam...@gmail.com wrote:
>
>> Hello all
>>
>> I use legacy dev mode with a old FF17 with succes on GWT 2.10 / jdk 11. I 
>> had to overide JettyLauncher class to add "javax.sql." on the 
>> "allowedFromSystemClassLoader" variable
>> Until now, I have no issue with this mode except this.
>>
>> Le jeu. 30 juin 2022 à 09:30, Thomas Broyer  a écrit :
>>
>>> Didn't legacy devmode also only work with JDK 8?
>>>
>>> On Wednesday, June 29, 2022 at 10:46:30 PM UTC+2 Jens wrote:
>>>
>>>> Without being able to see the project setup this is tough to answer.
>>>>
>>>> However regardless of the exception you are seeing: Classic/Legacy 
>>>> DevMode will not work with GWT 2.9.0 correctly, because GWT 2.9.0 already 
>>>> uses JsInterop internally in its Java SDK emulation (e.g. java.util.Date 
>>>> uses it). JsInterop is not supported by classic/legacy DevMode. With GWT 
>>>> 2.9.0 you have to use SuperDevMode to have a functional Java SDK emulation 
>>>> during development.
>>>>
>>>> -- J.
>>>>
>>>> abhiy...@gmail.com schrieb am Mittwoch, 29. Juni 2022 um 21:58:40 
>>>> UTC+2:
>>>>
>>>>> Hi Team,
>>>>>
>>>>> I am trying to start classic DEV mode in eclipse through GWT eclipse 
>>>>> plugin .
>>>>> I am using GWT 2.9.0 + Java 11 combination.
>>>>> I am getting below error. Can you help me in resolving the below error:
>>>>>
>>>>> [b]Caused by: java.lang.ClassNotFoundException: javax.sql.DataSource
>>>>> at 
>>>>> com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.findClass(JettyLauncher.java:478)
>>>>>  
>>>>> ~[gwt-dev-2.9.0.jar:?]
>>>>> at 
>>>>> org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:441)
>>>>>  
>>>>>
>>>> -- 
>>>
>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit/6d3569b5-b7f0-4c2e-918c-c342b6803441n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/google-web-toolkit/6d3569b5-b7f0-4c2e-918c-c342b6803441n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/8f0d65cc-b082-4803-8072-459644d06126n%40googlegroups.com.

Re: java.lang.ClassNotFoundException: javax.sql.DataSource when using GWT 2.9.0 + Java 11 combination

2022-12-19 Thread eliasbala...@gmail.com 
Overriding JettyLauncher with  "javax.sql." on the 
"allowedFromSystemClassLoader" variable has worked for me on a variety of 
projects, using SuperDevMode + GWT 2.9.0 + JDK 11

I hope a future version of GWT will make use of a Jetty version supporting 
a more elegant way to override the "allowedFromSystemClassLoader" variable.

On Friday, 1 July 2022 at 20:32:18 UTC+1 nam...@gmail.com wrote:

> Hello all
>
> I use legacy dev mode with a old FF17 with succes on GWT 2.10 / jdk 11. I 
> had to overide JettyLauncher class to add "javax.sql." on the 
> "allowedFromSystemClassLoader" variable
> Until now, I have no issue with this mode except this.
>
> Le jeu. 30 juin 2022 à 09:30, Thomas Broyer  a écrit :
>
>> Didn't legacy devmode also only work with JDK 8?
>>
>> On Wednesday, June 29, 2022 at 10:46:30 PM UTC+2 Jens wrote:
>>
>>> Without being able to see the project setup this is tough to answer.
>>>
>>> However regardless of the exception you are seeing: Classic/Legacy 
>>> DevMode will not work with GWT 2.9.0 correctly, because GWT 2.9.0 already 
>>> uses JsInterop internally in its Java SDK emulation (e.g. java.util.Date 
>>> uses it). JsInterop is not supported by classic/legacy DevMode. With GWT 
>>> 2.9.0 you have to use SuperDevMode to have a functional Java SDK emulation 
>>> during development.
>>>
>>> -- J.
>>>
>>> abhiy...@gmail.com schrieb am Mittwoch, 29. Juni 2022 um 21:58:40 UTC+2:
>>>
 Hi Team,

 I am trying to start classic DEV mode in eclipse through GWT eclipse 
 plugin .
 I am using GWT 2.9.0 + Java 11 combination.
 I am getting below error. Can you help me in resolving the below error:

 [b]Caused by: java.lang.ClassNotFoundException: javax.sql.DataSource
 at 
 com.google.gwt.dev.shell.jetty.JettyLauncher$WebAppContextWithReload$WebAppClassLoaderExtension.findClass(JettyLauncher.java:478)
  
 ~[gwt-dev-2.9.0.jar:?]
 at 
 org.eclipse.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:441)
  

>>> -- 
>>
> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/6d3569b5-b7f0-4c2e-918c-c342b6803441n%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/ca2662bc-f0ba-48f2-bd14-e673dd882ccdn%40googlegroups.com.

Re: unable to instal and use gwt-plugin in Eclipse 2022-06 or Eclipse 2022-09

2022-11-15 Thread eliasbala...@gmail.com 
I am facing the same problems here, having teams of developers only 
familiar with the GWT plugin.

Unfortunately, the alternative is ratehr tricky.
To my understanding it involves use of Maven run configurations within 
Eclipse respective to the GWT plugin run configurations plus forcing 
"maven-install-plugin" to run within Eclipse.
see 
https://www.eclipse.org/m2e/documentation/release-notes-17.html#new-syntax-for-specifying-lifecycle-mapping-metadata

I am afraid GWT plugin is sadly leaving us.

I hope this helps you.

On Tuesday, 15 November 2022 at 16:34:09 UTC ngf.ch...@gmail.com wrote:

> I am using Eclipse IDE for Enterprise Java and Web Developers - 2022-09 
> and am unable to install and use gwt plugin.
> 1. I have before then used Eclipse IDE for Enterprise Java and Web 
> Developers - 2022-06 with the same result. The plugin doesn't install in 
> eclipse.
>
>
> How to use gwt now as i can't use it through my IDE.? 
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/13e4ac1b-efb1-4fa5-a89d-eb80bd6dbf5en%40googlegroups.com.

Re: JavaFX for GWT

2022-11-09 Thread eliasbala...@gmail.com 
This is quite an interesting approach, I am intrigued.

Some remoting capabilities could be useful though.
I know a few standalone apps (Swing, SWT, JavaFX etc.) that rely on server 
communications.

Perhaps custom communication layers for various protocols and transports 
could be added by contributors.

On Wednesday, 9 November 2022 at 14:58:42 UTC Bruno Salmon wrote:

> hi Jonathan,
>
> Unfortunately for your project, I have no plan to support Swing as 
> covering JavaFX is already a big job.
>
> If you are looking for a solution to run your app without a server like 
> WebFX does, I don't think that exists for Swing.
>
> But if you don't mind having a server, there are solutions like WebSwing 
> that can run your app on a server, and then you can have a kind of remote 
> desktop of it in the browser. 
>
> On Wednesday, 9 November 2022 at 12:39:48 UTC Jonathan Franchesco Torres 
> Bca wrote:
>
>> Hi,
>>
>> And what about JFC Swing which is interoperable with JavaFX.
>> I have a desktop application that mixes both and we use substance to 
>> improve the display of the controls
>> I leave an example
>> [image: image.png]
>>
>>  
>>
>>  *   
>>    
>>  *
>>
>> Jonathan Franchesco Torres Baca(@jofrantoba)
>>
>> CIO - Kiongo Technology
>>
>> *Jr Juan Voto Bernales 344 - La Victoria, Lima - Perú*
>>
>> Teléfono   *+5116357857 <+51%201%206357857>*
>>
>> Cel.+51929913524 <+51%20929%20913%20524>
>>
>>
>> El mar, 8 nov 2022 a las 9:38, Bruno Salmon () 
>> escribió:
>>
>>> Hi,
>>>
>>> I'm working on a JavaFX transpiler powered by GWT.
>>> It lets you use JavaFX as a UI toolkit in your GWT apps.
>>> The JavaFX API is far from completely covered, but you can already see 
>>> some interesting results.
>>>
>>> The project is on GitHub for those who are interested.
>>> https://github.com/webfx-project/webfx
>>>
>>> If you have any questions, please let me know.
>>>
>>> -- 
>>>
>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit/8210a6a2-ad1a-4b2d-ba68-19dcc5fbeef3n%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/72879326-af08-48da-8eaf-6cfee7bc85d3n%40googlegroups.com.

Re: Migrating to ltgt gwt-maven-plugin causes compile problem with HibernateValidation

2022-08-24 Thread eliasbala...@gmail.com 
This looks like a classpath issue, from which I have suffered in the past 
but eventually managed to control.

I suggest using Maven dependency control to force the correct 
implementation of the offending classes, particularly if you are running 
with "GWT Eclipse Plugin" which doesn't respect inherited Maven dependency 
exclusions/overrides etc.

If you are using "GWT Eclipse Plugin", even though it is becoming outdated, 
there is still a way to control the classpath.
study https://github.com/eliasbalasis/eclipse-gwt-recipe for 
single-classpath for "Single CLASSPATH stream" traces.

I hope this helps you.

On Wednesday, 24 August 2022 at 03:42:59 UTC+1 Thomas wrote:

> Hi all,
>
> I'm in the progress of modularising a GWT app and migrating it to use the 
> newer ltgt gwt-maven-plugin. I have a GWT module which compiles correctly 
> using the old gwt-maven-plugin, but fails with the following errors using 
> the new gwt-maven-plugin:
>
> [INFO] --- gwt-maven-plugin:1.0.1:compile (default-compile) @ gwt-portal 
> ---
> [INFO] Compiling module com.inspectivity.portal.Portal
> [INFO]Tracing compile failure path for type 
> 'com.inspectivity.portal.client.validation.CustomValidatorFactory'
> [INFO]   [ERROR] Errors in 
> 'file:/Users/thomas/dev-private/inspectivity-modules/gwt-portal/src/main/java/com/inspectivity/portal/client/validation/CustomValidatorFactory.java'
> [INFO]  [ERROR] Line 31: The method getParameterNameProvider() of 
> type CustomValidatorFactory must override or implement a supertype method
> [INFO]  [ERROR] Line 36: The method close() of type 
> CustomValidatorFactory must override or implement a supertype method
> [INFO]Tracing compile failure path for type 
> 'org.hibernate.validator.engine.PathImpl'
> [INFO]   [ERROR] Errors in 
> 'jar:file:/Users/thomas/.m2/repository/com/google/gwt/gwt-user/2.8.2/gwt-user-2.8.2.jar!/org/hibernate/validator/super/org/hibernate/validator/engine/PathImpl.java'
> [INFO]  [ERROR] Line 72: NodeImpl cannot be resolved to a type
> [INFO]  [ERROR] Line 84: NodeImpl cannot be resolved to a type
> [INFO]  [ERROR] Line 131: NodeImpl cannot be resolved to a type
> [INFO]  [ERROR] Line 202: NodeImpl cannot be resolved to a type
> [INFO]  [ERROR] Line 95: NodeImpl cannot be resolved to a type
> [INFO]  [ERROR] Line 127: NodeImpl cannot be resolved to a type
> [INFO]Tracing compile failure path for type 
> 'org.hibernate.validator.engine.ConstraintViolationImpl_CustomFieldSerializer'
> [INFO]   [ERROR] Errors in 
> 'jar:file:/Users/thomas/.m2/repository/com/google/gwt/gwt-user/2.8.2/gwt-user-2.8.2.jar!/org/hibernate/validator/engine/ConstraintViolationImpl_CustomFieldSerializer.java'
> [INFO]  [ERROR] Line 100: The method 
> instantiate(SerializationStreamReader) from the type 
> ConstraintViolationImpl_CustomFieldSerializer refers to the missing type 
> ConstraintViolationImpl
> [INFO]  [ERROR] Line 37: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]  [ERROR] Line 73: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]  [ERROR] Line 32: The type 
> ConstraintViolationImpl_CustomFieldSerializer must implement the inherited 
> abstract method 
> CustomFieldSerializer.deserializeInstance(SerializationStreamReader,
>  
> ConstraintViolationImpl)
> [INFO]  [ERROR] Line 33: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]  [ERROR] Line 32: The type 
> ConstraintViolationImpl_CustomFieldSerializer must implement the inherited 
> abstract method 
> CustomFieldSerializer.serializeInstance(SerializationStreamWriter,
>  
> ConstraintViolationImpl)
> [INFO]  [ERROR] Line 41: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]  [ERROR] Line 105: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]  [ERROR] Line 88: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]  [ERROR] Line 53: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]  [ERROR] Line 98: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]Tracing compile failure path for type 
> 'org.hibernate.validator.engine.ValidationSupport'
> [INFO]   [ERROR] Errors in 
> 'jar:file:/Users/thomas/.m2/repository/com/google/gwt/gwt-user/2.8.2/gwt-user-2.8.2.jar!/org/hibernate/validator/engine/ValidationSupport.java'
> [INFO]  [ERROR] Line 43: ConstraintViolationImpl cannot be 
> resolved to a type
> [INFO]   [ERROR] Errors in 
> 'jar:file:/Users/thomas/.m2/repository/com/google/gwt/gwt-user/2.8.2/gwt-user-2.8.2.jar!/org/hibernate/validator/super/org/hibernate/validator/engine/PathImpl.java'
> [INFO]  [ERROR] Line 72: NodeImpl cannot be resolved to a type
> [INFO]  [ERROR] Line 84: NodeImpl cannot be resolved to a type
> [INFO]  [ERROR] Line 131: NodeImpl cannot be resolved to a type
> [INFO]  [ERR

Re: GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2022-05-24 Thread eliasbala...@gmail.com 
This seems to be working finally.

To my surprise, I repeated the experiment and [GWT Eclipse Plugin] is fully 
accessible and operational.

I am now confused.

On Monday, 23 May 2022 at 23:37:41 UTC+1 hprc wrote:

>
> I also use the GWT Eclipse Plugin.
> Currently, the Eclipse side is up to 202103, and seems to be up to JDK1.8.
>
> The official documentation still only describes this plugin, so I'd like 
> you to add a method with the Moven plugin as soon as possible.
> (Preferably with illustrations)
> 2022年5月24日火曜日 6:57:01 UTC+9 eliasb...@gmail.com:
>
>> [GWT Eclipse Plugin] has served us very well.
>>
>> It is quite unfortunate but I fear the time for putting it to rest is 
>> approaching, if it hasn't already come.
>>
>> I just don't want to give up yet :-)
>>
>> On Monday, 23 May 2022 at 03:46:42 UTC+1 hprc wrote:
>>
>>>
>>> It's certainly interesting.
>>> However, do you recognize that the development of [GWT Eclipse Plugin] 
>>> will not be continued anymore?
>>> 2022年5月22日日曜日 18:16:34 UTC+9 eliasb...@gmail.com:
>>>
 Interesting...

 But you are using STS distribution not the standard, perhaps something 
 is different in the STS distribution compared to the primary Eclipse 
 Foundation's distribution.

 On Saturday, 14 May 2022 at 19:09:32 UTC+1 foal wrote:

> I am on Eclipse 4.22 (STS 4.13.1) and plugin still works (
> https://github.com/gwt-plugins/gwt-eclipse-plugin) 
>
> On Wednesday, May 4, 2022 at 12:56:47 AM UTC+2 Craig Mitchell wrote:
>
>> I'm on Eclipse 2021-09 (4.21.0) and it works fine.
>>
>> However, after this version, the Google plugin stops working  
>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659  
>> so I haven't tried later versions.
>>
>> On Monday, 2 May 2022 at 11:17:23 pm UTC+10 eliasb...@gmail.com 
>> wrote:
>>
>>> Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still working.
>>>
>>> Under Eclipse 2022-03, the preferences page, the GWT Development 
>>> view and the run configurations are not accessible.
>>>
>>> This is crucial for certain teams relying on GWT Eclipse Plugin for 
>>> running applications from within the Eclipse IDE and locks users to 
>>> Eclipse 
>>> 2021-03 permanently, unless this can be fixed.
>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/3d2d5269-8d35-45d6-a7b7-0d549759bdf0n%40googlegroups.com.

Re: GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2022-05-23 Thread eliasbala...@gmail.com 
[GWT Eclipse Plugin] has served us very well.

It is quite unfortunate but I fear the time for putting it to rest is 
approaching, if it hasn't already come.

I just don't want to give up yet :-)

On Monday, 23 May 2022 at 03:46:42 UTC+1 hprc wrote:

>
> It's certainly interesting.
> However, do you recognize that the development of [GWT Eclipse Plugin] 
> will not be continued anymore?
> 2022年5月22日日曜日 18:16:34 UTC+9 eliasb...@gmail.com:
>
>> Interesting...
>>
>> But you are using STS distribution not the standard, perhaps something is 
>> different in the STS distribution compared to the primary Eclipse 
>> Foundation's distribution.
>>
>> On Saturday, 14 May 2022 at 19:09:32 UTC+1 foal wrote:
>>
>>> I am on Eclipse 4.22 (STS 4.13.1) and plugin still works (
>>> https://github.com/gwt-plugins/gwt-eclipse-plugin) 
>>>
>>> On Wednesday, May 4, 2022 at 12:56:47 AM UTC+2 Craig Mitchell wrote:
>>>
 I'm on Eclipse 2021-09 (4.21.0) and it works fine.

 However, after this version, the Google plugin stops working  
 https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659  
 so I haven't tried later versions.

 On Monday, 2 May 2022 at 11:17:23 pm UTC+10 eliasb...@gmail.com wrote:

> Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still working.
>
> Under Eclipse 2022-03, the preferences page, the GWT Development view 
> and the run configurations are not accessible.
>
> This is crucial for certain teams relying on GWT Eclipse Plugin for 
> running applications from within the Eclipse IDE and locks users to 
> Eclipse 
> 2021-03 permanently, unless this can be fixed.
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/5cf6e36d-dabe-46fb-b5e1-2913e0f33e02n%40googlegroups.com.

Re: GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2022-05-22 Thread eliasbala...@gmail.com 
Interesting...

But you are using STS distribution not the standard, perhaps something is 
different in the STS distribution compared to the primary Eclipse 
Foundation's distribution.

On Saturday, 14 May 2022 at 19:09:32 UTC+1 foal wrote:

> I am on Eclipse 4.22 (STS 4.13.1) and plugin still works (
> https://github.com/gwt-plugins/gwt-eclipse-plugin) 
>
> On Wednesday, May 4, 2022 at 12:56:47 AM UTC+2 Craig Mitchell wrote:
>
>> I'm on Eclipse 2021-09 (4.21.0) and it works fine.
>>
>> However, after this version, the Google plugin stops working  
>> https://github.com/GoogleCloudPlatform/google-cloud-eclipse/issues/3659  
>> so I haven't tried later versions.
>>
>> On Monday, 2 May 2022 at 11:17:23 pm UTC+10 eliasb...@gmail.com wrote:
>>
>>> Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still working.
>>>
>>> Under Eclipse 2022-03, the preferences page, the GWT Development view 
>>> and the run configurations are not accessible.
>>>
>>> This is crucial for certain teams relying on GWT Eclipse Plugin for 
>>> running applications from within the Eclipse IDE and locks users to Eclipse 
>>> 2021-03 permanently, unless this can be fixed.
>>>
>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/1e5baf0b-9bc2-437d-bfbf-71644abd0299n%40googlegroups.com.

GWT Eclipse Plugin is not compatible with Eclipse 2022-03

2022-05-02 Thread eliasbala...@gmail.com 
Until Eclipse 2021-03 (4.19) the GWT Eclipse Plugin is still working.

Under Eclipse 2022-03, the preferences page, the GWT Development view and 
the run configurations are not accessible.

This is crucial for certain teams relying on GWT Eclipse Plugin for running 
applications from within the Eclipse IDE and locks users to Eclipse 2021-03 
permanently, unless this can be fixed.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/e165100e-7e7b-4439-927c-29448fc9f6b0n%40googlegroups.com.

Eclipse Plugin WebContent Refresh

2009-07-31 Thread eliasbala...@gmail.com 

I am quite successfully using "Google Eclipse Plugin for GWT" with
Eclipse J2EE 3.5 (Galileo) release

Only issue I have is with automatic refresh of WebContent folder.
Under an Eclipse WTP project the default folder for generating web
files is "WebContent". default for google plugin in "war".
I changed google plugin's default but when compiling Eclipse does not
seem to refresh the contents of the output folder and thus WTP cannot
republish the output to running web server. (I had to do it manually
or semi-automatically using an "eclipse external tool configuration"
with ant)

Is it possible to consider implementing the refresh in future versions
of google plugin? Plugin works perfectly under eclipse. It is just a
matter of convenience and easier project maintenance.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---