I have a test environment with the BuiltInDs project that uses the following components:
JDK 1.8
SmartGWT Eval v13.0-p20221103
GWT 2.8.2
Maven 3.8.6
And to run it I use the following targets:
![imagen1.png Click image for larger version
Name: imagen1.png
Views: 170
Size: 227.2 KB
ID: 269413](filedata/fetch?id=269413&d=1674255064)
![Imagen2.png Click image for larger version
Name: Imagen2.png
Views: 183
Size: 153.8 KB
ID: 269412](filedata/fetch?id=269412&d=1674254873)
![imagen3.png Click image for larger version
Name: imagen3.png
Views: 172
Size: 184.8 KB
ID: 269416](filedata/fetch?id=269416&d=1674255201)
![imagen4.png Click image for larger version
Name: imagen4.png
Views: 178
Size: 179.1 KB
ID: 269417](filedata/fetch?id=269417&d=1674255396)
![imagen5.png Click image for larger version
Name: imagen5.png
Views: 177
Size: 134.2 KB
ID: 269418](filedata/fetch?id=269418&d=1674255451)
![imagen6.png Click image for larger version
Name: imagen6.png
Views: 178
Size: 134.9 KB
ID: 269419](filedata/fetch?id=269419&d=1674255495)
With this configuration, I can access Developer Mode for debugging the code and it works correctly.
On the other hand, I have an environment with a real project that uses the following components:
JDK 1.8
SmartGWT Pro v4.0
GWT 2.8.0
Maven 2.0
And I run it using the following goals:
![imagen7.png Click image for larger version
Name: imagen7.png
Views: 161
Size: 214.2 KB
ID: 269420](filedata/fetch?id=269420&d=1674255548)
![imagen8.png Click image for larger version
Name: imagen8.png
Views: 172
Size: 144.8 KB
ID: 269421](filedata/fetch?id=269421&d=1674255597)
With those goals I can access the Developer Mode for debugging the code and it works correctly.
Now, when I migrate the productive project to the SmartGWT v13.0-p20221103 version with GWT 2.8.2, the same Maven 2.0 and JDK 1.8, with the same goals that worked in the project without migration, the goals are executed correctly and I can activate the Developer Mode, but the debugging has no effect; moreover, in the console, only a trace similar to this one appears:
![imagen9.png Click image for larger version
Name: imagen9.png
Views: 171
Size: 131.8 KB
ID: 269422](filedata/fetch?id=269422&d=1674255756)
JDK 1.8
SmartGWT Eval v13.0-p20221103
GWT 2.8.2
Maven 3.8.6
And to run it I use the following targets:
With this configuration, I can access Developer Mode for debugging the code and it works correctly.
On the other hand, I have an environment with a real project that uses the following components:
JDK 1.8
SmartGWT Pro v4.0
GWT 2.8.0
Maven 2.0
And I run it using the following goals:
With those goals I can access the Developer Mode for debugging the code and it works correctly.
Now, when I migrate the productive project to the SmartGWT v13.0-p20221103 version with GWT 2.8.2, the same Maven 2.0 and JDK 1.8, with the same goals that worked in the project without migration, the goals are executed correctly and I can activate the Developer Mode, but the debugging has no effect; moreover, in the console, only a trace similar to this one appears:
Comment