Sorry for the flood, I have never seen a such thing on this ML

Le 17/04/2023 à 16:21, Jacques Le Roux a écrit :
Le 15/04/2023 à 08:56, Jacques Le Roux a écrit :
Le 14/04/2023 à 21:53, Michael Brohl a écrit :
Additionally, I realized that the settings file is (re)generated by the Gradle eclipse task and the property vanished during the process. It would be necessary to add the setting during the build.
Yes, as I could not get it working, I did not dig into that yet. As I said it's not stopping me to debug, but Groovy, so unrelated to JDK 17. I use the last Eclipse ( 2023-03) and all last Eclipse plugins.

(3rd try after removing image, trying again, then using same Apache link 
<https://s.apache.org/i4v8n> below instead of GH, the ML is not very friendly)
The message below in italic did not pass I guess because I put an image I now 
removed

------------------------------------------------------------------------------------------------------------------------------------------------------

/Good news at //"/ignoreUnnamedModuleForSplitPackage=enabled does not work"/aka https://github.com/eclipse-jdt/eclipse.jdt/issues/57 <https://s.apache.org/i4v8n>//now closed :)/

//

/Maybe it's could also be due to a trick Leila gave me and I just applied. //
/

//

/Here is the copy of her message translated (Leila who knows stuff is a bit shy 
;)/

//

/<<On the other hand, in relation to your breakpoint concern, I know that it can come from the config of your project if in the classpath the groovy libraries are not added (or the source is badly configured).//
/ /
//If you see options with add instead of remove://
/ /
//- add groovy dsl support//
/ /
//- add groovy libraries to classpath>>/

//

/Hopefully the image will pass (I doubt). //If not, it's only  a matter of using the "Add" options from the project "Groovy" option (like you have "team" there for instance )//
/ /
//Here is my answer to Leila so far:/

//

/<<Thank you Leila,
/

//

/Indeed I remember now, I had already written about this problem but the 
solution was much more tedious than what you propose.
It had to be done one by one by hand. What I had done before and worked for a 
moment, then failed when I updated Eclipse.
I just tried your trick and I can see the .classpath file has been updated with //added 
(kind="src") in the groovy files, which I didn't have before.
I'll test and get back to you
Thanks again!
>>

HTH/

//

/Jacques
/

//

Reply via email to